IETF Discussion

• Thread Index

• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: ned+ietf
• RE: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
  • From: Aissaoui, Mustapha (Mustapha)
• Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
  • From: Andrew G. Malis
• RE: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
  • From: Aissaoui, Mustapha (Mustapha)
• RE: tsv-dir review of draft-garcia-shim6-applicability-03
  • From: Alberto García
• Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
  • From: Stewart Bryant
• Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
  • From: Thomas Nadeau
• Re: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
  • From: Stewart Bryant
• Fwd: Last Call: <draft-ietf-pwe3-pw-typed-wc-fec-03.txt> (LDP Typed Wildcard FEC for PWid and Generalized PWid FEC Elements) to Proposed Standard
  • From: Stewart Bryant
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John R. Levine
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Alessandro Vesely
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (DeprecatingUse of the "X-" Prefix in Application Protocols) to BestCurrent Practice
  • From: t.petch
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: ned+ietf
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Patrik Fältström
• RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Randall Gellens
• RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Paul E. Jones
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Mark Nottingham
• RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Paul E. Jones
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Martin Rex
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Randy Bush
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Mark Nottingham
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John R. Levine
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Randy Bush
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Mark Nottingham
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John R. Levine
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Randall Gellens
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Mark Nottingham
• Re: [IETF] Add a link to the HTML version in i-d-announce mails ?
  • From: Warren Kumari
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Randall Gellens
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Barry Leiba
• Re: [IETF] Add a link to the HTML version in i-d-announce mails ?
  • From: Barry Leiba
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>
  • From: Randall Gellens
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John Levine
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Randall Gellens
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Peter Saint-Andre
• RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Murray S. Kucherawy
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>
  • From: Peter Saint-Andre
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Peter Saint-Andre
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Tim Bray
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Randall Gellens
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Scott Kitterman
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Peter Saint-Andre
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Scott Kitterman
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Peter Saint-Andre
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John R. Levine
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Russ Housley
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Yoav Nir
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Julian Reschke
• RE: tsv-dir review of draft-garcia-shim6-applicability-03
  • From: Alberto García
• RE: Add a link to the HTML version in i-d-announce mails ?
  • From: Murray S. Kucherawy
• RE: Add a link to the HTML version in i-d-announce mails ?
  • From: Murray S. Kucherawy
• Re: WG Review: INtermediary-safe SIP session ID (insipid)
  • From: Barry Leiba
• Re: Last Call: <draft-snell-atompub-tombstones-15.txt> (The Atom "deleted-entry" Element) to Proposed Standard
  • From: Peter Saint-Andre
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Barry Leiba
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Scott Kitterman
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Alessandro Vesely
• RE: tsv-dir review of draft-garcia-shim6-applicability-03
  • From: Dan Wing
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John R. Levine
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Tony Finch
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Rolf E. Sonneveld
• Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of anAssociated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
  • From: t.petch
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Alessandro Vesely
• Re: [IETF] Add a link to the HTML version in i-d-announce mails ?
  • From: Warren Kumari
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: ned+ietf
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Yoav Nir
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Xavier Marjou
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John R. Levine
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Tony Hansen
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Riccardo Bernardini
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Barry Leiba
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Dave Crocker
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Randy Bush
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Russ Housley
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Hector
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Julian Reschke
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Riccardo Bernardini
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Yoav Nir
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Simon Perreault
• Re: Add a link to the HTML version in i-d-announce mails ?
  • From: Julian Reschke
• Add a link to the HTML version in i-d-announce mails ?
  • From: Xavier Marjou
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Tony Finch
• Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of anAssociated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
  • From: Eliot Lear
• Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of anAssociated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
  • From: t.petch
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Alexey Melnikov
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Alexey Melnikov
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Alexey Melnikov
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: ned+ietf
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Patrik Fältström
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John Levine
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: ned+ietf
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: ned+ietf
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: ned+ietf
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: ned+ietf
• Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
  • From: Andrew G. Malis
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Barry Leiba
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Hector Santos
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Alessandro Vesely
• RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Murray S. Kucherawy
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John Levine
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Patrik Fältström
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: SM
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: ned+ietf
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: ned+ietf
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: John R. Levine
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Alexey Melnikov
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Alexey Melnikov
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Alexey Melnikov
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Alexey Melnikov
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Donald Eastlake
• Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Alessandro Vesely
• RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocationof an Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: ned+ietf
• Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
  • From: Russ Housley
• RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
  • From: John E Drake
• Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John Levine
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: ned+ietf
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Scott Kitterman
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Patrik Fältström
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: ned+ietf
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Alessandro Vesely
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Hector
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: John Levine
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Hector
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Scott Kitterman
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Scott Kitterman
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>
  • From: Randall Gellens
• Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM)
  • From: Bernard Aboba
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John R. Levine
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Updates to draft-farrresnickel-ipr-sanctions
  • From: Adrian Farrel
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Doug Barton
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: ned+ietf
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John R. Levine
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Doug Barton
• RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Murray S. Kucherawy
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Paul Hoffman
• RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Murray S. Kucherawy
• RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Murray S. Kucherawy
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: Doug Barton
• RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Murray S. Kucherawy
• Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: Scott O. Bradner
• Re: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: Julien Meuric
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Scott Kitterman
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Scott Kitterman
• Re: provisioning software, was DNS RRTYPEs, the difficulty with
  • From: John R. Levine
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Scott Kitterman
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Hector
• Re: DNS RRTYPEs, the difficulty with
  • From: Doug Barton
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Patrik Fältström
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: ned+ietf
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Randy Bush
• RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of anAssociated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
  • From: John C Klensin
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Scott Kitterman
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: John Leslie
• Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of anAssociated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
  • From: Russ Housley
• RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Murray S. Kucherawy
• Re: [marf] Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: SM
• Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: John C Klensin
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Peter Saint-Andre
• RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Murray S. Kucherawy
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: SM
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Mark Nottingham
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: SM
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Scott Kitterman
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Barry Leiba
• RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of anAssociated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Murray S. Kucherawy
• Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: Russ Housley
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Paul Hoffman
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Paul Hoffman
• Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
  • From: Scott Kitterman
• RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: Kyung-Yeop Hong (hongk)
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Peter Saint-Andre
• RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Murray S. Kucherawy
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Peter Saint-Andre
• Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: Stewart Bryant
• RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of anAssociated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Murray S. Kucherawy
• RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: John C Klensin
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Dave Crocker
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: SM
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: SM
• RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: Russ Housley
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Nick Hilliard
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Tim Bray
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Peter Saint-Andre
• RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Scott Kitterman
• Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: Loa Andersson
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Henrik Nordström
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Henrik Nordström
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Henrik Nordström
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Henrik Nordström
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Adrien de Croy
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: SM
• Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: Russ Housley
• RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: Kyung-Yeop Hong (hongk)
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Scott Kitterman
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple MailTransfer Protocol extension for Message Transfer Priorities)to Proposed Standard
  • From: t.petch
• Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
  • From: SM
• RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
  • From: Murray S. Kucherawy
• tsv-dir review of draft-garcia-shim6-applicability-03
  • From: Dan Wing
• Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard
  • From: Julian Reschke
• Re: Conclusion of Last Call for draft-ietf-sieve-convert anddraft-ietf-sieve-notify-sip-message
  • From: Pete Resnick
• Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard
  • From: SM
• Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard
  • From: Vincent Roca
• Re: Gen-ART LC/Telechat review of draft-ietf-mext-mip6-tls-03
  • From: Jouni Korhonen
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector Santos
• Re: DNS RRTYPEs, the difficulty with
  • From: Alessandro Vesely
• Re: Conclusion of Last Call for draft-ietf-sieve-convert anddraft-ietf-sieve-notify-sip-message
  • From: t.petch
• Re: DNS RRTYPEs, the difficulty with
  • From: Stephan Wenger
• Re: DNS RRTYPEs, the difficulty with
  • From: Scott Kitterman
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: DNS RRTYPEs, the difficulty with
  • From: Scott Kitterman
• Re: DNS RRTYPEs, the difficulty with
  • From: Stephan Wenger
• Re: DNS RRTYPEs, the difficulty with
  • From: ned+ietf
• Re: DNS RRTYPEs, the difficulty with
  • From: John R. Levine
• Re: DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: DNS RRTYPEs, the difficulty with
  • From: John Levine
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: DNS RRTYPEs, the difficulty with
  • From: Scott Kitterman
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: DNS RRTYPEs, the difficulty with
  • From: Scott Kitterman
• Re: DNS RRTYPEs, the difficulty with
  • From: Scott Kitterman
• Gen-ART LC/Telechat review of draft-ietf-mext-mip6-tls-03
  • From: Ben Campbell
• Re: DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: DNS RRTYPEs, the difficulty with
  • From: John R. Levine
• Re: DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• RE: DNS RRTYPEs, the difficulty with
  • From: Murray S. Kucherawy
• Re: DNS RRTYPEs, the difficulty with
  • From: Scott Kitterman
• Re: DNS RRTYPEs, the difficulty with
  • From: Doug Barton
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: Reminder: T-shirt Design Contest for IETF 83
  • From: Benson Schliesser
• Re: DNS RRTYPEs, the difficulty with
  • From: John Leslie
• Re: Reminder: T-shirt Design Contest for IETF 83
  • From: Phillip Hallam-Baker
• Re: DNS RRTYPEs, the difficulty with
  • From: Alessandro Vesely
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: DNS RRTYPEs, the difficulty with
  • From: John Levine
• Re: DNS RRTYPEs, the difficulty with
  • From: Paul Hoffman
• Re: DNS RRTYPEs, the difficulty with
  • From: John Levine
• Re: DNS RRTYPEs, the difficulty with
  • From: John Levine
• Re: DNS RRTYPEs, the difficulty with
  • From: John Levine
• Re: DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• ISOC Fellowship to the IETF (IETF 84 and 85)
  • From: Steve Conte
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector
• RE: DNS RRTYPEs, the difficulty with
  • From: Murray S. Kucherawy
• Re: DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Mark Andrews
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: DNS RRTYPEs, the difficulty with
  • From: Doug Barton
• Re: DNS RRTYPEs, the difficulty with
  • From: Scott Kitterman
• RE: DNS RRTYPEs, the difficulty with
  • From: Murray S. Kucherawy
• Re: DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: DNS RRTYPEs, the difficulty with
  • From: Mark Andrews
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: DNS RRTYPEs, the difficulty with
  • From: Scott Kitterman
• Re: DNS RRTYPEs, the difficulty with
  • From: Paul Hoffman
• Re: DNS RRTYPEs, the difficulty with
  • From: Patrik Fältström
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector
• RE: DNS RRTYPEs, the difficulty with
  • From: Murray S. Kucherawy
• Re: DNS RRTYPEs, the difficulty with
  • From: Patrik Fältström
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: John C Klensin
• Re: DNS Rule Transmission is a new tool in anti-spam controls
  • From: Hector
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Willy Tarreau
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Willy Tarreau
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Adrien de Croy
• Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Ted Lemon
• Re: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC
  • From: david.black
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Patrik Fältström
• DNS Rule Transmission is a new tool in anti-spam controls
  • From: Todd Glassey
• Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
  • From: Stewart Bryant
• Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
  • From: Thomas D Nadeau
• Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
  • From: Loa Andersson
• Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
  • From: Stewart Bryant
• Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
  • From: Loa Andersson
• Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
  • From: Stewart Bryant
• Re: DNS RRTYPEs, the difficulty with
  • From: Alessandro Vesely
• RE: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
  • From: HUANG Feng F
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• RE: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: TEVFİK ŞAHİN
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Julian Reschke
• Re: [pcp] Last Call: <draft-ietf-pcp-base-23.txt> (Port Control Protocol (PCP)) to Proposed Standard
  • From: Masataka Ohta
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Yoav Nir
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Mark Nottingham
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Mark Nottingham
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Mark Nottingham
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Julian Reschke
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Julian Reschke
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Julian Reschke
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Joe Touch
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Doug Barton
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Mark Nottingham
• Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Joe Touch
• Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Joe Touch
• Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Joe Touch
• Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Joe Touch
• Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis))
  • From: Mark Andrews
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Yoav Nir
• Re: DNS RRTYPEs, the difficulty with
  • From: Hector
• Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis))
  • From: Edward Lewis
• Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis))
  • From: Scott Kitterman
• Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis))
  • From: Andrew Sullivan
• Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis))
  • From: Scott Kitterman
• DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis))
  • From: Andrew Sullivan
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: John C Klensin
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Willy Tarreau
• Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Kim Kinnear
• Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Kim Kinnear
• draft-weil-shared-transition-space-request
  • From: The IESG
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Patrik Fältström
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Andrew Sullivan
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Paul Hoffman
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Patrik Fältström
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Mark Andrews
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Mark Nottingham
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Roy T. Fielding
• Re: Variable length internet addresses in TCP/IP: history
  • From: Mark Andrews
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Tim Bray
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Roy T. Fielding
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Paul Hoffman
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Tim Bray
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Roy T. Fielding
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
  • From: Masataka Ohta
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses
  • From: Mark Andrews
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
  • From: Brian E Carpenter
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
  • From: Masataka Ohta
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses
  • From: Martin Rex
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
  • From: ned+ietf
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
  • From: Mark Andrews
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
  • From: ned+ietf
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
  • From: Doug Barton
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
  • From: ned+ietf
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Julian Reschke
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Doug Barton
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Tim Bray
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Doug Barton
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
  • From: Doug Barton
• Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Jeffrey Hutzelman
• Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
  • From: ned+ietf
• Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
  • From: Brian E Carpenter
• RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC
  • From: George, Wes
• RE: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Leif Sawyer
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: RJ Atkinson
• Re: Variable length internet addresses in TCP/IP: history
  • From: Martin Rex
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: David Harrington
• RE: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
  • From: Daniel Cohn
• Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
  • From: Damien Saucez
• Fwd: Re: [tz] Astrolabe dismisses suit.
  • From: Eliot Lear
• Re: A nuance of interoperability reports
  • From: Suzanne Woolf
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Julian Reschke
• Re: A nuance of interoperability reports
  • From: Hector
• Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
  • From: Eliot Lear
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Salvatore Loreto
• Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
  • From: Eliot Lear
• Gen-ART LC review of draft-ietf-pcn-3-in-1-encoding-08
  • From: Roni Even
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Peter Saint-Andre
• Re: A nuance of interoperability reports
  • From: Martin Rex
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Paul Hoffman
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Paul Hoffman
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Peter Saint-Andre
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Paul Hoffman
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: RJ Atkinson
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Albert Lunde
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: David Harrington
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Hector Santos
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Adrien de Croy
• Re: A nuance of interoperability reports
  • From: Randy Bush
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: David Morris
• Re: A nuance of interoperability reports
  • From: Scott Kitterman
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Wes Hardaker
• Re: A nuance of interoperability reports
  • From: Randy Bush
• RE: A nuance of interoperability reports
  • From: Murray S. Kucherawy
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Hector Santos
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Hector Santos
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Julian Reschke
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: David Morris
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Michael Richardson
• Re: A nuance of interoperability reports
  • From: Richard Barnes
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• A nuance of interoperability reports
  • From: Murray S. Kucherawy
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Mark Nottingham
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Tim Bray
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Mark Nottingham
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Barry Leiba
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Conclusion of Last Call for draft-ietf-sieve-convert and draft-ietf-sieve-notify-sip-message
  • From: Pete Resnick
• Re: Explanation of the OCSP sign request
  • From: Martin Rex
• Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
  • From: Livingood, Jason
• Explanation of the OCSP sign request
  • From: Robert Hernady
• Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
  • From: Lorenzo Colitti
• Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
  • From: John Scudder
• Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Ted Lemon
• Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Kim Kinnear
• Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Kim Kinnear
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Julian Reschke
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Julian Reschke
• Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
  • From: Stephen Farrell
• Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard
  • From: Julian Reschke
• Re: Variable length internet addresses in TCP/IP: history
  • From: Masataka Ohta
• Re: IETF Last Calls and Godwin-like rules
  • From: SM
• Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Ralph Droms
• Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Joe Touch
• Re: IETF Last Calls and Godwin-like rules
  • From: Henning Schulzrinne
• Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
  • From: Joe Touch
• Re: IETF Last Calls and Godwin-like rules
  • From: Pete Resnick
• Re: IETF Last Calls and Godwin-like rules
  • From: John C Klensin
• Re: IETF Last Calls and Godwin-like rules
  • From: Paul Hoffman
• Re: IETF Last Calls and Godwin-like rules
  • From: Chris Grundemann
• Re: IETF Last Calls and Godwin-like rules
  • From: Peter Saint-Andre
• Re: IETF Last Calls and Godwin-like rules
  • From: Chris Grundemann
• Re: IETF Last Calls and Godwin-like rules
  • From: SM
• Re: IETF Last Calls and Godwin-like rules
  • From: Pete Resnick
• Re: IETF Last Calls and Godwin-like rules
  • From: Melinda Shore
• Re: IETF Last Calls and Godwin-like rules
  • From: Andrew Sullivan
• Re: Variable length internet addresses in TCP/IP: history
  • From: Brian E Carpenter
• Re: IETF Last Calls and Godwin-like rules
  • From: Pete Resnick
• Re: Variable length internet addresses in TCP/IP: history
  • From: Bob Hinden
• RE: IETF Last Calls and Godwin-like rules
  • From: Leif Sawyer
• Re: IETF Last Calls and Godwin-like rules
  • From: Randy Bush
• Re: Variable length internet addresses in TCP/IP: history
  • From: Noel Chiappa
• Re: IETF Last Calls and Godwin-like rules
  • From: Dave CROCKER
• Re: Variable length internet addresses in TCP/IP: history
  • From: Bob Hinden
• Re: IETF Last Calls and Godwin-like rules
  • From: Noel Chiappa
• RE: IETF Last Calls and Godwin-like rules
  • From: Leif Sawyer
• Re: IETF Last Calls and Godwin-like rules
  • From: Pete Resnick
• Re: IETF Last Calls and Godwin-like rules
  • From: George Willingmyre
• Re: SEARS - Search Engine Address Resolution Service (and Protocol)
  • From: Todd Glassey
• Re: [core] Last Call: <draft-ietf-core-link-format-11.txt> (CoRE Link Format) to Proposed Standard
  • From: Don Sturek
• Re: [DNSOP] SEARS - Search Engine Address Resolution Service (and Protocol)
  • From: Dmitry Belyavsky
• Re: Last Call: <draft-reschke-http-status-308-05.txt> (The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)) to Experimental RFC
  • From: Julian Reschke
• Re: IETF Last Calls and Godwin-like rules
  • From: Dave CROCKER
• Re: Variable length internet addresses in TCP/IP: history
  • From: Dave CROCKER
• Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
  • From: Jari Arkko
• Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
  • From: Jari Arkko
• Re: IETF Last Calls and Godwin-like rules
  • From: Randy Bush
• Re: Variable length internet addresses in TCP/IP: history
  • From: Steven Bellovin
• Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
  • From: Joel M. Halpern
• Re: Variable length internet addresses in TCP/IP: history
  • From: Masataka Ohta
• Re: SEARS - Search Engine Address Resolution Service (and Protocol)
  • From: Masataka Ohta
• IRTF IPR Disclosure Rules
  • From: Eggert, Lars
• Re: IETF Last Calls and Godwin-like rules
  • From: Nick Hilliard
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Nick Hilliard
• Re: IETF Last Calls and Godwin-like rules
  • From: Mark Andrews
• Re: [core] Last Call: <draft-ietf-core-link-format-11.txt> (CoRE Link Format) to Proposed Standard
  • From: Carsten Bormann
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: David Conrad
• Re: IETF Last Calls and Godwin-like rules
  • From: Noel Chiappa
• RE: SEARS - Search Engine Address Resolution Service (and Protocol)
  • From: Worley, Dale R (Dale)
• Re: IETF Last Calls and Godwin-like rules
  • From: John C Klensin
• Re: [core] Last Call: <draft-ietf-core-link-format-11.txt> (CoRE Link Format) to Proposed Standard
  • From: Carsten Bormann
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: james woodyatt
• SEARS - Search Engine Address Resolution Service (and Protocol)
  • From: Todd Glassey
• Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
  • From: John G. Scudder
• Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
  • From: John Scudder
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Martin Millnert
• Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
  • From: Thomas Narten
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Martin Millnert
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Chris Grundemann
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Nick Hilliard
• Re: IETF Last Calls and Godwin-like rules
  • From: Melinda Shore
• RE: Auth48 comments on draft-ietf-pwe3-static-pw-status-10
  • From: Gregory Mirsky
• re: [core] Last Call: <draft-ietf-core-link-format-11.txt> (CoRE Link Format) to Proposed Standard
  • From: Don Sturek
• draft-weil last call: IANA Reserved IPv4 Prefix for Shared Address Space
  • From: Scott A Griffith
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Martin Millnert
• Re: IETF Last Calls and Godwin-like rules
  • From: SM
• Re: IETF Last Calls and Godwin-like rules
  • From: Alia Atlas
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP'
  • From: Chris Grundemann
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Chris Grundemann
• Re: IETF Last Calls and Godwin-like rules
  • From: Noel Chiappa
• Re: IETF Last Calls and Godwin-like rules
  • From: Yoav Nir
• Re: IETF Last Calls and Godwin-like rules
  • From: Roger Jørgensen
• Re: IETF Last Calls and Godwin-like rules
  • From: Yoav Nir
• Re: IETF Last Calls and Godwin-like rules
  • From: Dave CROCKER
• Re: IETF Last Calls and Godwin-like rules
  • From: Yoav Nir
• Re: IETF Last Calls and Godwin-like rules
  • From: Måns Nilsson
• IETF Last Calls and Godwin-like rules
  • From: John C Klensin
• Re: Auth48 comments on draft-ietf-pwe3-static-pw-status-10
  • From: Stewart Bryant
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Martin Millnert
• Re: Auth48 comments on draft-ietf-pwe3-static-pw-status-10
  • From: Bocci, Matthew (Matthew)
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP'
  • From: Roger Jørgensen
• Re: Variable length internet addresses in TCP/IP: history
  • From: Steven Bellovin
• Re: Variable length internet addresses in TCP/IP: history
  • From: Masataka Ohta
• Re: Variable length internet addresses in TCP/IP: history
  • From: Masataka Ohta
• Re: Variable length internet addresses in TCP/IP: history
  • From: Steven Bellovin
• RE: Variable length internet addresses in TCP/IP: history
  • From: Ross Callon
• Re: Variable length internet addresses in TCP/IP: history
  • From: Steven Bellovin
• Re: Variable length internet addresses in TCP/IP: history
  • From: Noel Chiappa
• Re: Variable length internet addresses in TCP/IP: history
  • From: Dave CROCKER
• Re: Variable length internet addresses in TCP/IP: history
  • From: Wes Beebee
• Re: Variable length internet addresses in TCP/IP: history
  • From: Richard Barnes
• Re: Variable length internet addresses in TCP/IP: history
  • From: Steve Crocker
• Re: Variable length internet addresses in TCP/IP: history
  • From: Dave CROCKER
• Re: WG Review: Recharter of Locator/ID Separation Protocol (lisp)
  • From: Thomas Narten
• Re: Variable length internet addresses in TCP/IP: history
  • From: Stephen Sprunk
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
  • From: Lea Roberts
• Last Call: draft-weil-shared-transition-space-request-14.txt (IANA Reserved IPv4 Prefix for Shared Address Space)
  • From: William Hale
• Re: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
  • From: Noel Chiappa
• Re: Last Call: <draft-garcia-shim6-applicability-03.txt> (Applicability Statement for the Level 3 Multihoming Shim Protocol (Shim6)) to Informational RFC
  • From: Brian E Carpenter
• Re: Variable length internet addresses in TCP/IP: history
  • From: Martin Millnert
• Re: Variable length internet addresses in TCP/IP: history
  • From: Noel Chiappa
• Re: Another last call for draft-weil
  • From: Joel M. Halpern
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Owen DeLong
• Followup Gen-ART Review on draft-ietf-dhc-forcerenew-nonce
  • From: Ben Campbell
• Re: Another last call for draft-weil
  • From: Scott O Bradner
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP'
  • From: Erichsen, Kirk
• Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
  • From: Livingood, Jason
• Auth48 comments on draft-ietf-pwe3-static-pw-status-10
  • From: Bocci, Matthew (Matthew)
• Re: Variable length internet addresses in TCP/IP: history
  • From: Dave CROCKER
• Re: Variable length internet addresses in TCP/IP: history
  • From: Yoav Nir
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
  • From: Martin Rex
• Re: Variable length internet addresses in TCP/IP: history
  • From: Masataka Ohta
• Re: Variable length internet addresses in TCP/IP: history
  • From: Cameron Byrne
• Re: Variable length internet addresses in TCP/IP: history
  • From: Randy Bush
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Doug Barton
• Re: Variable length internet addresses in TCP/IP: history
  • From: Brian E Carpenter
• Re: Last call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Victor Kuarsingh
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Victor Kuarsingh
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Masataka Ohta
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Pete Resnick
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
  • From: Martin Rex
• Re: Variable length internet addresses in TCP/IP: history
  • From: Randy Bush
• Let ARIN decide (was Re: Another last call for draft-weil)
  • From: Masataka Ohta
• Re: Variable length internet addresses in TCP/IP: history
  • From: Masataka Ohta
• Re: Variable length internet addresses in TCP/IP: history
  • From: Masataka Ohta
• Re: Variable length internet addresses in TCP/IP: history
  • From: Bob Hinden
• Re: Variable length internet addresses in TCP/IP: history
  • From: Mark Andrews
• Re: Variable length internet addresses in TCP/IP: history
  • From: Martin Rex
• Re: Variable length internet addresses in TCP/IP: history
  • From: Brian E Carpenter
• Re: Variable length internet addresses in TCP/IP: history
  • From: Martin Rex
• Re: Furthering discussions about BCP79 sanctions
  • From: Thomas Nadeau
• RE: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Leif Sawyer
• RE: Furthering discussions about BCP79 sanctions
  • From: Adrian Farrel
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Randy Bush
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Brian E Carpenter
• RE: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Leif Sawyer
• Reminder: T-shirt Design Contest for IETF 83
  • From: Alexa Morris
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Randy Bush
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: ned+ietf
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Pete Resnick
• RE: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Leif Sawyer
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: ned+ietf
• Re: Another last call for draft-weil
  • From: Christopher Morrow
• Re: Another last call for draft-weil
  • From: Bradner, Scott
• Re: Another last call for draft-weil
  • From: David Conrad
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Pete Resnick
• Re: Variable length internet addresses in TCP/IP: history
  • From: Bradner, Scott
• Re: Variable length internet addresses in TCP/IP: history
  • From: Steve Crocker
• Re: Another last call for draft-weil
  • From: Bradner, Scott
• RE: Another last call for draft-weil
  • From: Ross Callon
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Chris Grundemann
• Re: Furthering discussions about BCP79 sanctions
  • From: todd glassey
• Re: Last call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: William Check
• Re: Yet Another Reason?
  • From: todd glassey
• Variable length internet addresses in TCP/IP: history
  • From: Bob Braden
• Last call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Thienpondt Hans
• Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
  • From: Ted Lemon
• RE: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
  • From: Greg Daley
• Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
  • From: Ben Campbell
• Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
  • From: Ted Lemon
• Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
  • From: Ben Campbell
• Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
  • From: Ben Campbell
• Re: Another last call for draft-weil
  • From: Owen DeLong
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
  • From: Hector
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Jeff.Finkelstein
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: ned+ietf
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
  • From: Donald Eastlake