IETF Discussion Archive - Date Index

[Prev Page] [Next Page] [Thread Index]

Mar 14 2012

Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Noel Chiappa
Re: [IETF] Re: shared address space... a reality!, Warren Kumari
Re: Paris IETF Codesprint, Robert Sparks
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, Stewart Bryant
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Barry Leiba
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Barry Leiba
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Joel M. Halpern
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder
Re: shared address space... a reality!, Christopher Morrow
Re: [83attendees] Usual recreational venue diatribe (was Ground transportation from/to CDG), Iljitsch van Beijnum
Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC, Fangyu Li
RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC, 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, Fangyu Li
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, lihan
Re: GenART last call review of draft-ietf-behave-nat64-learn-analysis-03, jouni korhonen
Re: ×××××: 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, t.petch
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, Rolf Winter
Re: shared address space... a reality!, Turchanyi Geza
RE: הנדון: 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, Sprecher, Nurit (NSN - IL/Hod HaSharon)
RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof anAssociated Channel Code Point for Use byITU-T Ethernet based OAM) toInformational RFC, Sprecher, Nurit (NSN - IL/Hod HaSharon)
Re: shared address space... a reality!, Roger Jørgensen
Re: shared address space... a reality!, Måns Nilsson
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, yang . jian90
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Dino Farinacci

Mar 13 2012

Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the"X-" Prefix in Application Protocols) to Best Current Practice, 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, Peter Saint-Andre
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Noel Chiappa
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Eliot Lear
Gen-ART LC review of draft-melnikov-smtp-priority-09, Roni Even
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder
×××××: 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, Sprecher, Nurit (NSN - IL/Hod HaSharon)
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Joel M. Halpern
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder
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, Ross Callon
Re: [savi] Last Call: <draft-ietf-savi-dhcp-12.txt> (SAVI Solution for DHCP) to Proposed Standard, eric levy-abegnoli
GenART last call review of draft-ietf-behave-nat64-learn-analysis-03, Roni Even
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the"X-" Prefix in Application Protocols) to Best Current Practice, t.petch
IETF Mail Archive Tools RFI, Ray Pelletier

Mar 12 2012

RE: Last Call: <draft-ietf-bmwg-protection-meth-09.txt> (Methodology for benchmarking MPLS protection mechanisms) to Informational RFC, Gregory Mirsky
Re: Gen-ART LC/Telechat review of draft-reschke-http-status-308-05, Julian Reschke
Re: Gen-ART LC/Telechat review of draft-reschke-http-status-308-05, Peter Saint-Andre
Re: Gen-ART LC/Telechat review of draft-reschke-http-status-308-05, Julian Reschke
Gen-ART LC/Telechat review of draft-reschke-http-status-308-05, Ben Campbell
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, Loa Andersson

Mar 09 2012

IETF83 Audio Streaming info, Nick Kukich
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Stephane Bortzmeyer
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Stephane Bortzmeyer
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Weekly posting summary for ietf at ietf.org, Thomas Narten
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex

Mar 08 2012

Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: Add a link to the HTML version in i-d-announce mails ?, Martin Rex
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Barry Leiba
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Jari Arkko
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, John C Klensin
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Jari Arkko
Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard, John Bradley
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Tony Finch
RE: provisioning software, was DNS RRTYPEs, the difficulty with, Tony Finch
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard, Eran Hammer
RE: provisioning software, was DNS RRTYPEs, the difficulty with, Murray S. Kucherawy

Mar 07 2012

Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector
Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Andrew Sullivan
Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf
Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Stewart Bryant
Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Thomas Nadeau
RE: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Aissaoui, Mustapha (Mustapha)
Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Andrew G. Malis
RE: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Aissaoui, Mustapha (Mustapha)
Re: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, 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, Stewart Bryant
Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (DeprecatingUse of the "X-" Prefix in Application Protocols) to BestCurrent Practice, t.petch
RE: tsv-dir review of draft-garcia-shim6-applicability-03, Alberto García
Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: provisioning software, was DNS RRTYPEs, the difficulty with, 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, Randall Gellens
RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Paul E. Jones
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham
RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Paul E. Jones
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Randy Bush
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham
Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randy Bush
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham
Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham
Re: [IETF] Add a link to the HTML version in i-d-announce mails ?, Warren Kumari
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Barry Leiba
Re: [IETF] Add a link to the HTML version in i-d-announce mails ?, Barry Leiba
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>, Randall Gellens
Re: provisioning software, was DNS RRTYPEs, the difficulty with, John Levine
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens

Mar 06 2012

Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, 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, Murray S. Kucherawy
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>, 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, Peter Saint-Andre
Re: Add a link to the HTML version in i-d-announce mails ?, Tim Bray
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Scott Kitterman
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, 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, Scott Kitterman
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Peter Saint-Andre
Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine
Re: Add a link to the HTML version in i-d-announce mails ?, Russ Housley
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: Add a link to the HTML version in i-d-announce mails ?, Yoav Nir
Re: Add a link to the HTML version in i-d-announce mails ?, Julian Reschke
RE: Add a link to the HTML version in i-d-announce mails ?, Murray S. Kucherawy
RE: Add a link to the HTML version in i-d-announce mails ?, Murray S. Kucherawy
Re: WG Review: INtermediary-safe SIP session ID (insipid), Barry Leiba
Re: Last Call: <draft-snell-atompub-tombstones-15.txt> (The Atom "deleted-entry" Element) to Proposed Standard, Peter Saint-Andre
Re: Add a link to the HTML version in i-d-announce mails ?, Barry Leiba
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Scott Kitterman
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely
RE: tsv-dir review of draft-garcia-shim6-applicability-03, Dan Wing
RE: tsv-dir review of draft-garcia-shim6-applicability-03, Alberto García
Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Tony Finch
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, 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, t.petch
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely
Re: [IETF] Add a link to the HTML version in i-d-announce mails ?, Warren Kumari
Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf
Re: Add a link to the HTML version in i-d-announce mails ?, Yoav Nir
Re: Add a link to the HTML version in i-d-announce mails ?, Xavier Marjou
Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine
Re: Add a link to the HTML version in i-d-announce mails ?, Tony Hansen
Re: Add a link to the HTML version in i-d-announce mails ?, Riccardo Bernardini
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: Add a link to the HTML version in i-d-announce mails ?, Dave Crocker
Re: Add a link to the HTML version in i-d-announce mails ?, Randy Bush
Re: Add a link to the HTML version in i-d-announce mails ?, Russ Housley
Re: Add a link to the HTML version in i-d-announce mails ?, Hector
Re: Add a link to the HTML version in i-d-announce mails ?, Julian Reschke
Re: Add a link to the HTML version in i-d-announce mails ?, Riccardo Bernardini
Re: Add a link to the HTML version in i-d-announce mails ?, Yoav Nir
Re: Add a link to the HTML version in i-d-announce mails ?, Simon Perreault
Re: Add a link to the HTML version in i-d-announce mails ?, Julian Reschke
Add a link to the HTML version in i-d-announce mails ?, Xavier Marjou
Re: provisioning software, was DNS RRTYPEs, the difficulty with, 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, 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, t.petch
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov
Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Patrik Fältström
Re: provisioning software, was DNS RRTYPEs, the difficulty with, John Levine
Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf

Mar 05 2012

Mar 04 2012

Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely

Mar 03 2012

Mar 02 2012

Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews
Updates to draft-farrresnickel-ipr-sanctions, Adrian Farrel
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Doug Barton
Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf
Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Doug Barton
RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Murray S. Kucherawy
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Paul Hoffman
RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, 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, Murray S. Kucherawy
Re: provisioning software, was DNS RRTYPEs, the difficulty with, Doug Barton
RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Murray S. Kucherawy
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, Julien Meuric
Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman
Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman
Re: provisioning software, was DNS RRTYPEs, the difficulty with, 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, Scott Kitterman
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Hector
Re: DNS RRTYPEs, the difficulty with, Doug Barton
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, 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, ned+ietf
Weekly posting summary for ietf at ietf.org, Thomas Narten
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, 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, 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, Scott Kitterman

Mar 01 2012

Feb 29 2012

Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard, Julian Reschke
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Henrik Nordström
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Adrien de Croy
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Henrik Nordström
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Henrik Nordström
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Henrik Nordström
Re: Conclusion of Last Call for draft-ietf-sieve-convert anddraft-ietf-sieve-notify-sip-message, Pete Resnick
Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard, SM
Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard, Vincent Roca
Re: DNS RRTYPEs, the difficulty with, Alessandro Vesely
Re: Conclusion of Last Call for draft-ietf-sieve-convert anddraft-ietf-sieve-notify-sip-message, t.petch
Re: Gen-ART LC/Telechat review of draft-ietf-mext-mip6-tls-03, Jouni Korhonen
Re: DNS RRTYPEs, the difficulty with, Stephan Wenger
Re: DNS RRTYPEs, the difficulty with, Scott Kitterman
Re: DNS RRTYPEs, the difficulty with, Hector
Re: DNS RRTYPEs, the difficulty with, Scott Kitterman
Re: DNS RRTYPEs, the difficulty with, Stephan Wenger
Re: DNS RRTYPEs, the difficulty with, ned+ietf
Re: DNS RRTYPEs, the difficulty with, Hector Santos
Re: DNS RRTYPEs, the difficulty with, John R. Levine
Re: DNS RRTYPEs, the difficulty with, Mark Andrews
Re: DNS RRTYPEs, the difficulty with, John Levine
Re: DNS RRTYPEs, the difficulty with, Hector
Re: DNS RRTYPEs, the difficulty with, Scott Kitterman
Re: DNS RRTYPEs, the difficulty with, Hector

Feb 28 2012

Re: DNS RRTYPEs, the difficulty with, Scott Kitterman
Re: DNS RRTYPEs, the difficulty with, Scott Kitterman
Gen-ART LC/Telechat review of draft-ietf-mext-mip6-tls-03, Ben Campbell
Re: DNS RRTYPEs, the difficulty with, Mark Andrews
Re: DNS RRTYPEs, the difficulty with, John R. Levine
Re: DNS RRTYPEs, the difficulty with, Mark Andrews
RE: DNS RRTYPEs, the difficulty with, Murray S. Kucherawy
Re: DNS RRTYPEs, the difficulty with, Scott Kitterman
Re: DNS RRTYPEs, the difficulty with, Doug Barton
Re: DNS RRTYPEs, the difficulty with, Hector
Re: Reminder: T-shirt Design Contest for IETF 83, Benson Schliesser
Re: DNS RRTYPEs, the difficulty with, John Leslie
Re: Reminder: T-shirt Design Contest for IETF 83, Phillip Hallam-Baker
Re: DNS RRTYPEs, the difficulty with, Alessandro Vesely
Re: DNS RRTYPEs, the difficulty with, Hector
Re: DNS RRTYPEs, the difficulty with, John Levine
Re: DNS RRTYPEs, the difficulty with, Paul Hoffman
Re: DNS RRTYPEs, the difficulty with, John Levine
Re: DNS RRTYPEs, the difficulty with, John Levine
Re: DNS RRTYPEs, the difficulty with, John Levine
Re: DNS RRTYPEs, the difficulty with, Mark Andrews
ISOC Fellowship to the IETF (IETF 84 and 85), Steve Conte

Feb 27 2012

Re: DNS RRTYPEs, the difficulty with, Hector
RE: DNS RRTYPEs, the difficulty with, Murray S. Kucherawy
Re: DNS RRTYPEs, the difficulty with, Mark Andrews
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Mark Andrews
Re: DNS RRTYPEs, the difficulty with, Hector
Re: DNS RRTYPEs, the difficulty with, Doug Barton
Re: DNS RRTYPEs, the difficulty with, Scott Kitterman
RE: DNS RRTYPEs, the difficulty with, Murray S. Kucherawy
Re: DNS RRTYPEs, the difficulty with, Mark Andrews
Re: DNS RRTYPEs, the difficulty with, Mark Andrews
Re: DNS RRTYPEs, the difficulty with, Hector
Re: DNS RRTYPEs, the difficulty with, Scott Kitterman
Re: DNS RRTYPEs, the difficulty with, Paul Hoffman
Re: DNS RRTYPEs, the difficulty with, Patrik Fältström
Re: DNS RRTYPEs, the difficulty with, Hector
RE: DNS RRTYPEs, the difficulty with, Murray S. Kucherawy
Re: DNS RRTYPEs, the difficulty with, Patrik Fältström
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), John C Klensin
Re: DNS Rule Transmission is a new tool in anti-spam controls, Hector
Re: DNS RRTYPEs, the difficulty with, Hector
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, 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, 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, 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, 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, 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, Stewart Bryant
Re: DNS RRTYPEs, the difficulty with, 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, HUANG Feng F

Feb 26 2012

Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Stephen Farrell
RE: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), TEVFÄK ÅAHÄN
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Julian Reschke
Re: [pcp] Last Call: <draft-ietf-pcp-base-23.txt> (Port Control Protocol (PCP)) to Proposed Standard, Masataka Ohta
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Yoav Nir
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Willy Tarreau
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Willy Tarreau
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Mark Nottingham
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Adrien de Croy
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Stephen Farrell
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Mark Nottingham
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Stephen Farrell

Feb 25 2012

Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Mark Nottingham
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Stephen Farrell
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Julian Reschke
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Stephen Farrell
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Julian Reschke
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Stephen Farrell
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Julian Reschke
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Stephen Farrell
Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery, Joe Touch
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Doug Barton
Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery, Ted Lemon
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Mark Nottingham
Re: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC, david.black
Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery, Joe Touch
Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery, Joe Touch
Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery, Joe Touch
Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery, Joe Touch

Feb 24 2012

Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)), Mark Andrews
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Yoav Nir
Re: DNS RRTYPEs, the difficulty with, Hector
Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)), Edward Lewis
Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)), Scott Kitterman
Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)), Andrew Sullivan
Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)), Scott Kitterman
DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)), Andrew Sullivan
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Patrik FÃltstrÃm
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), John C Klensin
draft-weil-shared-transition-space-request, The IESG
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Patrik Fältström
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Andrew Sullivan
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Paul Hoffman
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Stephen Farrell
DNS Rule Transmission is a new tool in anti-spam controls, Todd Glassey
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Willy Tarreau
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Patrik Fältström
Weekly posting summary for ietf at ietf.org, Thomas Narten
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Mark Andrews
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Mark Nottingham
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Roy T. Fielding
Re: Variable length internet addresses in TCP/IP: history, Mark Andrews
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Tim Bray
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Roy T. Fielding
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Paul Hoffman
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Tim Bray
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Roy T. Fielding
Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history], Masataka Ohta
Re: Issues with "prefer IPv6" [Re: Variable length internet addresses, Mark Andrews
Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history], Brian E Carpenter
Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history], Masataka Ohta

Feb 23 2012

Re: Issues with "prefer IPv6" [Re: Variable length internet addresses, Martin Rex
Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history], ned+ietf
Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history], Mark Andrews
Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history], ned+ietf
Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history], Doug Barton
Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history], ned+ietf
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Julian Reschke
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Doug Barton
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Tim Bray
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Doug Barton
Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history], Doug Barton
Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery, Jeffrey Hutzelman
Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history], ned+ietf
Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery, Kim Kinnear
Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history], Brian E Carpenter
RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC, George, Wes
Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery, Kim Kinnear
RE: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Leif Sawyer
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), RJ Atkinson
Re: Variable length internet addresses in TCP/IP: history, Martin Rex
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Julian Reschke
Re: A nuance of interoperability reports, Hector
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Eliot Lear
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, Daniel Cohn
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Damien Saucez
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Salvatore Loreto
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Eliot Lear
Fwd: Re: [tz] Astrolabe dismisses suit., Eliot Lear

Feb 22 2012

Gen-ART LC review of draft-ietf-pcn-3-in-1-encoding-08, Roni Even
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Peter Saint-Andre
Re: A nuance of interoperability reports, Martin Rex
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Paul Hoffman
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Stephen Farrell
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Paul Hoffman
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Peter Saint-Andre
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), David Harrington
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Paul Hoffman
Re: A nuance of interoperability reports, Suzanne Woolf
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), RJ Atkinson
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Albert Lunde
Re: A nuance of interoperability reports, Randy Bush
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), David Morris
Re: A nuance of interoperability reports, Scott Kitterman
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Wes Hardaker
Re: A nuance of interoperability reports, Randy Bush
RE: A nuance of interoperability reports, Murray S. Kucherawy
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), David Harrington
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Hector Santos
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Hector Santos
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Hector Santos
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Julian Reschke
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), David Morris

Mail converted by MHonArc