IETF Discussion (thread)
Technical Plenary Captioned,
Ray Pelletier,
2012/03/26
- Re: Technical Plenary Captioned, SM, 2012/03/26
- Re: Technical Plenary Captioned, Ray Pelletier, 2012/03/26
- Re: Technical Plenary Captioned, SM, 2012/03/26
- Re: Technical Plenary Captioned, Joel jaeggli, 2012/03/26
- Re: Technical Plenary Captioned, Alexa Morris, 2012/03/26
- Re: Technical Plenary Captioned, SM, 2012/03/26
- Re: Technical Plenary Captioned, John C Klensin, 2012/03/26
- Re: Technical Plenary Captioned, Vinayak Hegde, 2012/03/27
IPv6 Zone Identifiers Considered Hateful,
Sabahattin Gucukoglu,
2012/03/19
- Re: IPv6 Zone Identifiers Considered Hateful, Francis Dupont, 2012/03/19
- Re: IPv6 Zone Identifiers Considered Hateful, Kevin P. Fleming, 2012/03/19
- Re: IPv6 Zone Identifiers Considered Hateful, t.petch, 2012/03/20
- RE: IPv6 Zone Identifiers Considered Hateful, Worley, Dale R (Dale), 2012/03/21
- Re: IPv6 Zone Identifiers Considered Hateful, Craig Finseth, 2012/03/21
- RE: IPv6 Zone Identifiers Considered Hateful, Worley, Dale R (Dale), 2012/03/21
- Re: IPv6 Zone Identifiers Considered Hateful, Craig Finseth, 2012/03/21
- Re: IPv6 Zone Identifiers Considered Hateful, Tony Finch, 2012/03/22
- RE: IPv6 Zone Identifiers Considered Hateful, Worley, Dale R (Dale), 2012/03/22
- Re: IPv6 Zone Identifiers Considered Hateful, Brian E Carpenter, 2012/03/22
- Re: IPv6 Zone Identifiers Considered Hateful, Francis Dupont, 2012/03/28
- Re: IPv6 Zone Identifiers Considered Hateful, Fred Baker, 2012/03/21
Query to the community -- An additional IETF Meeting event?,
IAOC Chair,
2012/03/16
- Re: Query to the community -- An additional IETF Meeting event?, Riccardo Bernardini, 2012/03/16
- Trade show at IETF, Sam Hartman, 2012/03/16
- Re: Trade show at IETF, Andy Bierman, 2012/03/16
- Re: Trade show at IETF, John C Klensin, 2012/03/16
- Re: Trade show at IETF, David Morris, 2012/03/16
- Re: Trade show at IETF, Melinda Shore, 2012/03/16
- Re: Trade show at IETF, John C Klensin, 2012/03/16
- Re: Trade show at IETF, Dave Crocker, 2012/03/16
- Re: Trade show at IETF, Joel jaeggli, 2012/03/16
- Re: Trade show at IETF, Joel jaeggli, 2012/03/17
- Re: Trade show at IETF, Dave Crocker, 2012/03/18
- Re: Trade show at IETF, John C Klensin, 2012/03/17
- Re: Trade show at IETF, Hector, 2012/03/19
- Re: Query to the community -- An additional IETF Meeting event?, Fred Baker, 2012/03/16
- Re: Query to the community -- An additional IETF Meeting event?, David Meyer, 2012/03/16
- Re: Query to the community -- An additional IETF Meeting event?, Dave Crocker, 2012/03/16
- Re: Query to the community -- An additional IETF Meeting event?, Fred Baker, 2012/03/16
- Re: Query to the community -- An additional IETF Meeting event?, Henk Uijterwaal, 2012/03/18
- RE: Query to the community -- An additional IETF Meeting event?, George, Wes, 2012/03/19
- Re: Query to the community -- An additional IETF Meeting event?, Michael Richardson, 2012/03/19
- Re: Query to the community -- An additional IETF Meeting event?, Ole Jacobsen, 2012/03/19
- Re: Query to the community -- An additional IETF Meeting event?, Ed Juskevicius, 2012/03/19
- Re: Query to the community -- An additional IETF Meeting event?, jonne.soininen, 2012/03/17
- RE: Query to the community -- An additional IETF Meeting event?, Richard Shockey, 2012/03/17
- FW: Query to the community -- An additional IETF Meeting event?, Knight, Frederick, 2012/03/19
Issues relating to managing a mailing list...,
Russ Housley,
2012/03/14
- Re: Issues relating to managing a mailing list..., Robert Raszuk, 2012/03/14
- Re: Issues relating to managing a mailing list..., ned+ietf, 2012/03/14
- Re: Issues relating to managing a mailing list..., Brian E Carpenter, 2012/03/14
- Re: Issues relating to managing a mailing list..., Scott Kitterman, 2012/03/14
- Re: Issues relating to managing a mailing list..., John C Klensin, 2012/03/14
- Re: Issues relating to managing a mailing list..., Cyrus Daboo, 2012/03/15
- Re: Issues relating to managing a mailing list..., John C Klensin, 2012/03/15
- Re: Issues relating to managing a mailing list..., Pete Resnick, 2012/03/15
- Re: Issues relating to managing a mailing list..., Cyrus Daboo, 2012/03/15
- Re: Issues relating to managing a mailing list..., Robert Sparks, 2012/03/15
- Re: Issues relating to managing a mailing list..., John Levine, 2012/03/16
- Re: Issues relating to managing a mailing list..., Kevin P. Fleming, 2012/03/16
- Re: Issues relating to managing a mailing list..., Marshall Eubanks, 2012/03/15
- Re: Issues relating to managing a mailing list..., Pete Resnick, 2012/03/15
- Re: Issues relating to managing a mailing list..., Michael Richardson, 2012/03/16
- Re: Issues relating to managing a mailing list..., Dave Crocker, 2012/03/15
- Re: Issues relating to managing a mailing list..., Pete Resnick, 2012/03/15
- Re: Issues relating to managing a mailing list..., Pete Resnick, 2012/03/15
- Re: Issues relating to managing a mailing list..., Michael Richardson, 2012/03/15
- Re: Issues relating to managing a mailing list..., Hector, 2012/03/16
- Re: Issues relating to managing a mailing list..., Dave Cridland, 2012/03/15
- Re: Issues relating to managing a mailing list..., Randy Bush, 2012/03/15
- Re: Issues relating to managing a mailing list..., Francesco Gennai, 2012/03/15
- Re: Issues relating to managing a mailing list..., Riccardo Bernardini, 2012/03/15
- Re: Issues relating to managing a mailing list..., Hector, 2012/03/15
- Re: Issues relating to managing a mailing list..., ned+ietf, 2012/03/15
- Re: Issues relating to managing a mailing list..., Andrew Sullivan, 2012/03/15
- Re: Issues relating to managing a mailing list..., Francesco Gennai, 2012/03/15
- Re: Issues relating to managing a mailing list..., ned+ietf, 2012/03/15
- Re: Issues relating to managing a mailing list..., Randy Bush, 2012/03/15
- Re: Issues relating to managing a mailing list..., Michael Richardson, 2012/03/15
- RE: Issues relating to managing a mailing list..., Ross Callon, 2012/03/14
- RE: Issues relating to managing a mailing list..., John C Klensin, 2012/03/15
- Re: Issues relating to managing a mailing list..., Lixia Zhang, 2012/03/15
- Re: Issues relating to managing a mailing list..., Riccardo Bernardini, 2012/03/15
- Re: Issues relating to managing a mailing list..., Marc Petit-Huguenin, 2012/03/15
- RE: Issues relating to managing a mailing list..., ned+ietf, 2012/03/15
- Re: Issues relating to managing a mailing list..., Rich Kulawiec, 2012/03/15
- Re: Issues relating to managing a mailing list..., Eliot Lear, 2012/03/15
- Re: Issues relating to managing a mailing list..., Michael Richardson, 2012/03/15
- Re: Issues relating to managing a mailing list..., Dave Crocker, 2012/03/15
- Re: Issues relating to managing a mailing list..., Sam Hartman, 2012/03/15
- Re: Issues relating to managing a mailing list..., Hector, 2012/03/16
- Re: Issues relating to managing a mailing list..., t.petch, 2012/03/16
- Re: Issues relating to managing a mailing list..., Eric Burger, 2012/03/19
- RE: Issues relating to managing a mailing list..., Noel Chiappa, 2012/03/15
- Re: Issues relating to managing a mailing list..., Russ Housley, 2012/03/15
- Re: Issues relating to managing a mailing list..., Noel Chiappa, 2012/03/15
- RE: Issues relating to managing a mailing list..., John C Klensin, 2012/03/15
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,
2012/03/14
- 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), 2012/03/14
- 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, 2012/03/14
- 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, t.petch, 2012/03/16
- 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, Stewart Bryant, 2012/03/16
- 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, t.petch, 2012/03/16
- RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC, Sprecher, Nurit (NSN - IL/Hod HaSharon), 2012/03/18
- Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC, t.petch, 2012/03/20
- RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC, Sprecher, Nurit (NSN - IL/Hod HaSharon), 2012/03/20
- 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, Andrew G. Malis, 2012/03/18
- 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, Andrew G. Malis, 2012/03/18
Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp),
Jari Arkko,
2012/03/08
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder, 2012/03/09
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Jari Arkko, 2012/03/08
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Barry Leiba, 2012/03/08
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder, 2012/03/14
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Joel M. Halpern, 2012/03/13
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder, 2012/03/14
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Eliot Lear, 2012/03/13
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Dino Farinacci, 2012/03/14
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder, 2012/03/14
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Joel M. Halpern, 2012/03/14
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Barry Leiba, 2012/03/14
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder, 2012/03/15
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Barry Leiba, 2012/03/14
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Noel Chiappa, 2012/03/13
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Noel Chiappa, 2012/03/14
Add a link to the HTML version in i-d-announce mails ?,
Xavier Marjou,
2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Julian Reschke, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Yoav Nir, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Hector, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Russ Housley, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Randy Bush, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Dave Crocker, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Tony Hansen, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Xavier Marjou, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Yoav Nir, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Julian Reschke, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Yoav Nir, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Russ Housley, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Tim Bray, 2012/03/06
- RE: Add a link to the HTML version in i-d-announce mails ?, Murray S. Kucherawy, 2012/03/06
- Re: [IETF] Add a link to the HTML version in i-d-announce mails ?, Warren Kumari, 2012/03/06
- RE: Add a link to the HTML version in i-d-announce mails ?, Murray S. Kucherawy, 2012/03/06
- Re: Add a link to the HTML version in i-d-announce mails ?, Martin Rex, 2012/03/08
Re: DNS RRTYPEs, the difficulty with,
Doug Barton,
2012/03/02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 2012/03/02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Doug Barton, 2012/03/02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Paul Hoffman, 2012/03/02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Doug Barton, 2012/03/02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 2012/03/02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Doug Barton, 2012/03/02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 2012/03/02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 2012/03/02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely, 2012/03/03
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 2012/03/03
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Patrik Fältström, 2012/03/03
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Scott Kitterman, 2012/03/03
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Patrik Fältström, 2012/03/05
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John Levine, 2012/03/05
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely, 2012/03/05
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector Santos, 2012/03/05
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 2012/03/05
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John Levine, 2012/03/05
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Patrik Fältström, 2012/03/05
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/05
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Tony Finch, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Tony Finch, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Randy Bush, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Patrik Fältström, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Stephane Bortzmeyer, 2012/03/09
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Andrew Sullivan, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Scott Kitterman, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John Levine, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 2012/03/06
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/07
- RE: provisioning software, was DNS RRTYPEs, the difficulty with, Murray S. Kucherawy, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 2012/03/07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Tony Finch, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Stephane Bortzmeyer, 2012/03/09
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/09
- RE: provisioning software, was DNS RRTYPEs, the difficulty with, Tony Finch, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 2012/03/08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 2012/03/09
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector, 2012/03/03
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Donald Eastlake, 2012/03/04
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 2012/03/03
- Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with, John Levine, 2012/03/03
- Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with, Hector, 2012/03/03
- Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely, 2012/03/04
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector, 2012/03/03
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard,
SM,
2012/03/01
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 2012/03/01
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, John Levine, 2012/03/02
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 2012/03/03
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov, 2012/03/05
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, John R. Levine, 2012/03/05
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 2012/03/05
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Rolf E. Sonneveld, 2012/03/06
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, SM, 2012/03/05
- RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Murray S. Kucherawy, 2012/03/01
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 2012/03/01
- RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Murray S. Kucherawy, 2012/03/01
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, John Leslie, 2012/03/01
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Randy Bush, 2012/03/01
- 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, 2012/03/02
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Hector, 2012/03/02
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 2012/03/02
- RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Murray S. Kucherawy, 2012/03/02
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Hector, 2012/03/02
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard,
Barry Leiba,
2012/03/01
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 2012/03/01
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 2012/03/02
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov, 2012/03/05
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 2012/03/05
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 2012/03/05
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 2012/03/05
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 2012/03/05
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 2012/03/05
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 2012/03/05
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov, 2012/03/06
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 2012/03/06
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov, 2012/03/05
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice,
Scott Kitterman,
2012/03/01
- 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, 2012/03/01
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Scott Kitterman, 2012/03/01
- 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, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Scott Kitterman, 2012/03/06
- 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, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Scott Kitterman, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens, 2012/03/06
- 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, 2012/03/06
- 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, 2012/03/06
- 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, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Barry Leiba, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randy Bush, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham, 2012/03/06
- 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, 2012/03/06
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham, 2012/03/06
- 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, 2012/03/07
- RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens, 2012/03/07
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (DeprecatingUse of the "X-" Prefix in Application Protocols) to BestCurrent Practice, t.petch, 2012/03/07
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis),
Henrik Nordström,
2012/03/01
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Adrien de Croy, 2012/03/01
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Henrik Nordström, 2012/03/01
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Henrik Nordström, 2012/03/01
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Henrik Nordström, 2012/03/01
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Peter Saint-Andre, 2012/03/01
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,
Kyung-Yeop Hong (hongk),
2012/03/01
- 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, Sprecher, Nurit (NSN - IL/Hod HaSharon), 2012/03/01
- 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, Russ Housley, 2012/03/01
- 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, Loa Andersson, 2012/03/01
- 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, Russ Housley, 2012/03/01
- 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, Sprecher, Nurit (NSN - IL/Hod HaSharon), 2012/03/01
- 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), 2012/03/01
- 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, John C Klensin, 2012/03/01
- 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, Sprecher, Nurit (NSN - IL/Hod HaSharon), 2012/03/01
- 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, 2012/03/01
- 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, 2012/03/01
- 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, Russ Housley, 2012/03/01
- 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, Sprecher, Nurit (NSN - IL/Hod HaSharon), 2012/03/01
- 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, Russ Housley, 2012/03/01
- 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, John E Drake, 2012/03/03
- 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, Russ Housley, 2012/03/03
- 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, Sprecher, Nurit (NSN - IL/Hod HaSharon), 2012/03/03
- 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, 2012/03/14
- Re: 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, ma . yuxia, 2012/03/14
- RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocationof anAssociated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC, Zhenlong Cui, 2012/03/21
- 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, John C Klensin, 2012/03/01
- 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, Scott O. Bradner, 2012/03/02
- 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, 2012/03/06
- 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, 2012/03/06
- 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, 2012/03/06
- 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, 2012/03/21
- 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, Thomas Walsh, 2012/03/21
- 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, 2012/03/23
- R: 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, D'Alessandro Alessandro Gerardo, 2012/03/21
- 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, Sprecher, Nurit (NSN - IL/Hod HaSharon), 2012/03/01
- 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, Kyung-Yeop Hong (hongk), 2012/03/01
Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard,
SM,
2012/03/01
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Barry Leiba, 2012/03/01
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 2012/03/01
- 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, 2012/03/01
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Barry Leiba, 2012/03/01
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 2012/03/01
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Barry Leiba, 2012/03/01
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 2012/03/02
- 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, 2012/03/02
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 2012/03/02
- Message not available
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 2012/03/02
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 2012/03/02