IETF Discussion (date)
March 30, 2012
- Re: [conex] Last Call: <draft-ietf-conex-concepts-uses-04.txt> (ConEx Concepts and Use Cases) to Informational RFC, marcelo bagnulo braun, 04:56
- Re: IETF attendees reengineer their hotel's Wi-Fi network, Michael Richardson, 03:13
- Re: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?, JORDI PALET MARTINEZ, 02:10
- RE: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?, George, Wes, 00:44
- RE: IETF attendees reengineer their hotel's Wi-Fi network, George, Wes, 00:34
March 29, 2012
- Weekly posting summary for ietf(_at_)ietf(_dot_)org, Thomas Narten, 23:54
- Re: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?, Yoav Nir, 17:01
- Re: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?, Eric Burger, 16:49
- Fwd: IETF attendees reengineer their hotel's Wi-Fi network, Robert Raszuk, 16:43
- IETF attendees reengineer their hotel's Wi-Fi network, Russ Housley, 16:28
- Re: [conex] Last Call: <draft-ietf-conex-concepts-uses-04.txt> (ConEx Concepts and Use Cases) to Informational RFC, Christopher Morrow, 11:13
- Re: [conex] Last Call: <draft-ietf-conex-concepts-uses-04.txt> (ConEx Concepts and Use Cases) to Informational RFC, Christopher Morrow, 11:11
- Re: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?, JORDI PALET MARTINEZ, 07:27
- IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?, Jim Fleming, 07:11
- Re: ZOOM://IETF.Fact.Check "Improving HTTP starts with speed.", Hannes Tschofenig, 02:35
- Re: ZOOM://IETF.Fact.Check "Improving HTTP starts with speed.", Fred Baker, 02:29
- Re: ZOOM://IETF.Fact.Check "Improving HTTP starts with speed.", Hannes Tschofenig, 02:11
March 28, 2012
- ZOOM://IETF.Fact.Check "Improving HTTP starts with speed.", Jim Fleming, 20:38
- ZOOM://IETF.Fact.Check ? 2012 State of the Art according to the ISOC ?, Jim Fleming, 18:54
- Re: Meetecho support fot Plenary session, Meetecho IETF support, 18:41
- IETF.FACT.CHECK ....839 new Top Level Domains or more...plus the DIRTY.BIT, Jim Fleming, 18:11
- IETF.Fact.Check on the ZOOM://BOX Protocol(s), Jim Fleming, 16:18
- IETF.Fact.Check on the ZOOM:// Scheme and ZOOM://BOX Architecture and the Inter.NOT, Jim Fleming, 15:51
- Re: IETF.Fact.Check - .COM .NET .ORG Legacy DNS vs Peer-2-Peer DNS, Nick Hilliard, 14:57
- IETF.Fact.Check - .COM .NET .ORG Legacy DNS vs Peer-2-Peer DNS, Jim Fleming, 14:22
- response set assertions and extensions, Dave Crocker, 13:27
- Re: IAB responds to ICANN questions concerning "The interpretation of rules in the ICANN gTLD applicant guidelines", David Morris, 13:17
- Meetecho support fot Plenary session, Meetecho IETF support, 09:38
- Re: IPv6 Zone Identifiers Considered Hateful, Thierry Moreau, 09:22
- Re: IPv6 Zone Identifiers Considered Hateful, Francis Dupont, 03:14
March 26, 2012
- Re: Technical Plenary Captioned, John C Klensin, 14:15
- OMA IETF MIF API Workshop - Room info, Hui Deng, 12:29
- Re: Anti-Trust Policy BOF tomorrow, Marshall Eubanks, 11:05
- Re: Fact.Check IETF Meeting - Paris, France - 100/8 IANA, David Conrad, 10:57
- Re: Technical Plenary Captioned, SM, 10:21
- Re: Technical Plenary Captioned, Alexa Morris, 10:12
- Anti-Trust Policy BOF tomorrow, Marshall Eubanks, 10:11
- Re: Technical Plenary Captioned, Joel jaeggli, 09:46
- Re: Technical Plenary Captioned, SM, 09:39
- Re: Technical Plenary Captioned, Ray Pelletier, 09:32
- Re: Technical Plenary Captioned, SM, 09:17
- Re: Fact.Check IETF Meeting - Paris, France - 100/8 IANA, Dave Cridland, 09:12
- Re: Fact.Check IETF Meeting - Paris, France - 100/8 IANA, Christopher Morrow, 09:09
- Technical Plenary Captioned, Ray Pelletier, 09:05
- Fact.Check IETF Meeting - Paris, France - 100/8 IANA, Jim Fleming, 08:21
March 25, 2012
- Re: Fact.Check IETF Meeting - 1460 registrations:, Francis Dupont, 17:13
- Re: Fact.Check IETF Meeting - Paris, France - Internet Engineering, Christopher Morrow, 10:26
- Fact.Check IETF Meeting - Paris, France - Internet Engineering, Jim Fleming, 10:21
- Re: Fact.Check IETF Meeting - 1460 registrations:, JORDI PALET MARTINEZ, 09:28
- Fact.Check IETF Meeting - 1460 registrations:, Jim Fleming, 08:37
- RE: FW: LastCall:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use byITU-T Ethernetbased OAM) toInformational RFC, Rui Costa, 06:12
- RE: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (AnOverviewoftheOAM Tool Set for MPLS based Transport Networks) toInformational RFC, Sprecher, Nurit (NSN - IL/Hod HaSharon), 01:51
March 23, 2012
- Re: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overviewofthe OAM Tool Set for MPLS based Transport Networks) toInformational RFC, Huub van Helvoort, 16:12
- RE: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Aissaoui, Mustapha (Mustapha), 12:02
- RE: [PWE3] FW: LastCall: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernet basedOAM) to Informational RFC, Ross Callon, 10:47
- Re: [PWE3] FW: LastCall: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernet basedOAM) to Informational RFC, Malcolm . BETTS, 10:40
- Re: FW: LastCall:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use byITU-T Ethernetbased OAM) toInformational RFC, Alia Atlas, 09:12
- 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, 06:31
- Re: FW: LastCall:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use byITU-T Ethernetbased OAM) toInformational RFC, t.petch, 05:59
- Re: [PWE3] FW: LastCall: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernet basedOAM) to Informational RFC, t.petch, 05:52
- Re: IPR requirements in document write-up, t.petch, 05:37
- 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, 04:45
- RE: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overviewofthe OAM Tool Set for MPLS based Transport Networks) toInformational RFC, Sprecher, Nurit (NSN - IL/Hod HaSharon), 02:11
March 22, 2012
- Weekly posting summary for ietf(_at_)ietf(_dot_)org, Thomas Narten, 23:53
- Re: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overviewof the OAM Tool Set for MPLS based Transport Networks) toInformational RFC, Huub van Helvoort, 18:27
- Re: IPv6 Zone Identifiers Considered Hateful, Brian E Carpenter, 17:28
- Re: FW: 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, Alia Atlas, 16:08
- RE: IPv6 Zone Identifiers Considered Hateful, Worley, Dale R (Dale), 11:48
- Re: Last Call: <draft-ietf-krb-wg-des-die-die-die-04.txt> (Deprecate DES, RC4-HMAC-EXP, and other weak cryptographic algorithms in Kerberos) to Best Current Practice, Joel jaeggli, 11:39
- RE: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overview of the OAM Tool Set for MPLS based Transport Networks) to Informational RFC, Rui Costa, 09:45
- FW: 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, Rui Costa, 09:43
- Re: IPv6 Zone Identifiers Considered Hateful, Tony Finch, 06:51
- RE: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overviewof the OAM Tool Set for MPLS based Transport Networks) toInformational RFC, Sprecher, Nurit (NSN - IL/Hod HaSharon), 05:52
March 21, 2012
- Re: IPv6 Zone Identifiers Considered Hateful, Brian E Carpenter, 22:50
- OMA IETF MIF API Workshop, Hui Deng, 20:50
- 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, 19:39
- Re: IPv6 Zone Identifiers Considered Hateful, Fred Baker, 19:31
- Journals at the IETF - calling all contributors!, Ole Jacobsen, 18:34
- Re: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overview of the OAM Tool Set for MPLS based Transport Networks) to Informational RFC, Huub van Helvoort, 17:49
- R: 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, erminio(_dot_)ottone_69(_at_)libero(_dot_)it, 17:43
- Re: IPv6 Zone Identifiers Considered Hateful, Brian E Carpenter, 16:52
- 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, Yoshinori Koike, 16:01
- Re: IPv6 Zone Identifiers Considered Hateful, Fred Baker, 15:44
- 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, Malcolm . BETTS, 15:35
- 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, Malcolm . BETTS, 15:35
- 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, Malcolm . BETTS, 15:33
- Re: IPv6 Zone Identifiers Considered Hateful, Craig Finseth, 15:15
- Re: [AVTCORE] IPR requirements in document write-up, Barry Leiba, 14:51
- RE: [AVTCORE] IPR requirements in document write-up, Roni Even, 14:29
- Re: [AVTCORE] IPR requirements in document write-up, Simon Josefsson, 14:00
- Re: [AVTCORE] IPR requirements in document write-up, Barry Leiba, 13:43
- Re: [AVTCORE] IPR requirements in document write-up, Stephan Wenger, 13:10
- RE: IPv6 Zone Identifiers Considered Hateful, Worley, Dale R (Dale), 13:00
- Re: IPv6 Zone Identifiers Considered Hateful, Craig Finseth, 12:55
- RE: IPv6 Zone Identifiers Considered Hateful, Worley, Dale R (Dale), 12:49
- 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, Alia Atlas, 10:30
- 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, D'Alessandro Alessandro Gerardo, 10:13
- R: הנדון: 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, D'Alessandro Alessandro Gerardo, 10:06
- 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, 09:16
- 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, 06:20
- 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, 06:06
- 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, Stephen Farrell, 04:33
- 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, Satoshi UENO, 04:21
- 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), 02:42
March 20, 2012
- Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>, Ryoo, Jeong-dong, 19:52
- 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, Huub van Helvoort, 18:19
- Re: URIs and zone IDs, Brian E Carpenter, 16:16
- UMPIRE moderation experiments at IETF83, Simon Pietro Romano, 10:15
- URIs and zone IDs (was: Re: IPv6 Zone Identifiers Considered Hateful), John C Klensin, 10:12
- 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), 04:52
- Re: IPv6 Zone Identifiers Considered Hateful, t.petch, 04:26
- 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, 04:16
March 19, 2012
- Re: Gen-ART LC review of draft-melnikov-smtp-priority-09, Alexey Melnikov, 15:23
- 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, 12:53
- Re: Query to the community -- An additional IETF Meeting event?, Ed Juskevicius, 09:58
- Re: Query to the community -- An additional IETF Meeting event?, Ole Jacobsen, 09:52
- Re: IPv6 Zone Identifiers Considered Hateful, Kevin P. Fleming, 09:39
- Re: Query to the community -- An additional IETF Meeting event?, Michael Richardson, 09:34
- 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, 09:12
- VS: Query to the community -- An additional IETF Meeting event?, teemu.savolainen, 09:11
- FW: Query to the community -- An additional IETF Meeting event?, Knight, Frederick, 09:10
- Beer and Gear, O'Reirdan, Michael, 09:10
- Re: Issues relating to managing a mailing list..., Eric Burger, 08:59
- Re: Trade show at IETF, Hector, 08:13
- Re: IPv6 Zone Identifiers Considered Hateful, Francis Dupont, 07:56
- RE: Query to the community -- An additional IETF Meeting event?, George, Wes, 07:46
- 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, Maarten vissers, 05:58
- IPv6 Zone Identifiers Considered Hateful, Sabahattin Gucukoglu, 05:56
March 18, 2012
- Re: Trade show at IETF, Dave Crocker, 12:41
- Re: Query to the community -- An additional IETF Meeting event?, Henk Uijterwaal, 10: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, 07:47
- 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, 07:33
- 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), 06:08
March 17, 2012
- RE: Query to the community -- An additional IETF Meeting event?, Richard Shockey, 10:46
- Re: Query to the community -- An additional IETF Meeting event?, Scott Brim, 09:36
- Re: Last Call: <draft-reschke-http-status-308-05.txt> (The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)) to Experimental RFC, Julian Reschke, 08:41
- Re: Last Call: <draft-reschke-http-status-308-05.txt> (The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)) to Experimental RFC, Julian Reschke, 07:51
- 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, Rui Costa, 07:01
- Re: Trade show at IETF, John C Klensin, 05:17
- Re: [Gen-art] Gen-ART LC/Telechat review of draft-reschke-http-status-308-05, Julian Reschke, 04:21
- Re: Query to the community -- An additional IETF Meeting event?, jonne.soininen, 04:19
- Re: Trade show at IETF, Joel jaeggli, 01:10
March 16, 2012
- Re: Trade show at IETF, Joel jaeggli, 23:28
- Re: Trade show at IETF, Dave Crocker, 23:15
- Re: Trade show at IETF, John C Klensin, 22:05
- Re: Trade show at IETF, Melinda Shore, 20:49
- Re: Trade show at IETF, David Morris, 18:33
- Re: Query to the community -- An additional IETF Meeting event?, Joel jaeggli, 17:34
- Re: Trade show at IETF, John C Klensin, 17:32
- Re: Trade show at IETF, David Morris, 17:00
- Re: Query to the community -- An additional IETF Meeting event?, Fred Baker, 16:33
- Re: Trade show at IETF, Russ Housley, 16:30
- Re: Query to the community -- An additional IETF Meeting event?, Dave Crocker, 16:24
- Re: Query to the community -- An additional IETF Meeting event?, Fred Baker, 16:21
- Re: Query to the community -- An additional IETF Meeting event?, David Meyer, 16:13
- Re: [Gen-art] Gen-ART LC/Telechat review of draft-reschke-http-status-308-05, Ben Campbell, 16:06
- Re: Query to the community -- An additional IETF Meeting event?, Fred Baker, 16:04
- Re: Trade show at IETF, Andy Bierman, 15:53
- Trade show at IETF, Sam Hartman, 15:35
- Re: Query to the community -- An additional IETF Meeting event?, Riccardo Bernardini, 15:30
- Query to the community -- An additional IETF Meeting event?, IAOC Chair, 14:49
- 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, 13:33
- Re: Issues relating to managing a mailing list..., Kevin P. Fleming, 13:00
- Re: Issues relating to managing a mailing list..., John Levine, 12:40
- 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, 11:06
- RE: Bad ABNF, Worley, Dale R (Dale), 10:48
- 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, 10:12
- Bad ABNF, SM, 10:10
- Re: [savi] Last Call: <draft-ietf-savi-dhcp-12.txt> (SAVI Solution for DHCP) to Proposed Standard, Guang Yao, 10:04
- Re: Issues relating to managing a mailing list..., Michael Richardson, 08:28
- Re: SIDR WG Virtual Interim Meeting, March 24, 2012, Stewart Bryant, 06:40
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the"X-" Prefix in Application Protocols) to Best Current Practice, t.petch, 06:02
- 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, 04:48
- Re: Issues relating to managing a mailing list..., t.petch, 04:44
- Re: Issues relating to managing a mailing list..., Hector, 02:06
- Re: Issues relating to managing a mailing list..., Hector, 01:28
March 15, 2012
- Weekly posting summary for ietf(_at_)ietf(_dot_)org, Thomas Narten, 23:53
- Re: SIDR WG Virtual Interim Meeting, March 24, 2012, Ted Hardie, 18:50
- Re: Issues relating to managing a mailing list..., Pete Resnick, 15:41
- Re: Issues relating to managing a mailing list..., Marshall Eubanks, 15:19
- Re: Issues relating to managing a mailing list..., Pete Resnick, 13:46
- Re: Issues relating to managing a mailing list..., Pete Resnick, 13:42
- Re: Issues relating to managing a mailing list..., Dave Crocker, 13:40
- RE: Issues relating to managing a mailing list..., ned+ietf, 13:39
- Re: Issues relating to managing a mailing list..., Robert Sparks, 13:37
- Re: Issues relating to managing a mailing list..., Michael Richardson, 13:24
- Re: Issues relating to managing a mailing list..., ned+ietf, 13:21
- RE: Issues relating to managing a mailing list..., John C Klensin, 13:16
- Re: Issues relating to managing a mailing list..., Cyrus Daboo, 12:57
- Re: Issues relating to managing a mailing list..., Dave Crocker, 12:56
- Re: Issues relating to managing a mailing list..., Sam Hartman, 12:55
- Re: Issues relating to managing a mailing list..., Noel Chiappa, 12:42
- Re: Issues relating to managing a mailing list..., Francesco Gennai, 12:04
- Re: Issues relating to managing a mailing list..., Russ Housley, 12:03
- Re: Issues relating to managing a mailing list..., Pete Resnick, 10:49
- Re: Issues relating to managing a mailing list..., Rich Kulawiec, 10:44
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder, 10:43
- RE: Issues relating to managing a mailing list..., ned+ietf, 10:29
- Re: Issues relating to managing a mailing list..., Andrew Sullivan, 10:24
- Re: Issues relating to managing a mailing list..., Marc Petit-Huguenin, 10:13
- Re: Issues relating to managing a mailing list..., ned+ietf, 10:10
- Re: IETF Mail Archive Tools RFI, Russ Housley, 10:01
- Re: Issues relating to managing a mailing list..., Riccardo Bernardini, 09:56
- Re: IETF Mail Archive Tools RFI, SM, 09:52
- Re: Issues relating to managing a mailing list..., Lixia Zhang, 09:43
- Re: Issues relating to managing a mailing list..., John C Klensin, 08:56
- RE: Issues relating to managing a mailing list..., John C Klensin, 08:48
- Re: Issues relating to managing a mailing list..., Dave Cridland, 08:45
- Re: Issues relating to managing a mailing list..., Cyrus Daboo, 08:41
- Re: Issues relating to managing a mailing list..., Dave Crocker, 08:38
- Re: Issues relating to managing a mailing list..., Michael Richardson, 08:27
- Re: Issues relating to managing a mailing list..., Michael Richardson, 08:19
- Re: Issues relating to managing a mailing list..., Scott Brim, 08:18
- Re: [83attendees] Usual recreational venue diatribe (was Ground transportation from/to CDG), Iljitsch van Beijnum, 07:46
- Re: Issues relating to managing a mailing list..., Hector, 05:53
- Re: Issues relating to managing a mailing list..., Riccardo Bernardini, 04:50
- New ITS email list for discussing IPv6 and vehicular communications, Alexandru Petrescu, 04:04
- Re: Issues relating to managing a mailing list..., Francesco Gennai, 02:19
- Re: Issues relating to managing a mailing list..., Eliot Lear, 02:16
- Re: Issues relating to managing a mailing list..., Randy Bush, 01:48
- Re: Issues relating to managing a mailing list..., Randy Bush, 01:45
- RE: Issues relating to managing a mailing list..., Noel Chiappa, 00:07
March 14, 2012
- RE: Issues relating to managing a mailing list..., Ross Callon, 23:02
- Re: Issues relating to managing a mailing list..., John C Klensin, 22:48
- 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, 22:13
- Re: Issues relating to managing a mailing list..., Scott Kitterman, 20:45
- Re: Issues relating to managing a mailing list..., Brian E Carpenter, 20:28
- Re: Issues relating to managing a mailing list..., David Morris, 20:26
- Re: Issues relating to managing a mailing list..., ned+ietf, 19:45
- Re: Issues relating to managing a mailing list..., Robert Raszuk, 18:57
- Issues relating to managing a mailing list..., Russ Housley, 18:46
- RE: [PWE3] FW: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernet based OAM)to Informational RFC, Sprecher, Nurit (NSN - IL/Hod HaSharon), 17:43
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Noel Chiappa, 16:31
- Re: [IETF] Re: shared address space... a reality!, Warren Kumari, 12:06
- Re: Paris IETF Codesprint, Robert Sparks, 10:55
- 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, 10:54
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Barry Leiba, 10:30
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder, 10:18
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Dino Farinacci, 10:17
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder, 10:16
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder, 10:16
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Barry Leiba, 10:03
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Joel M. Halpern, 09:47
- Re: shared address space... a reality!, Christopher Morrow, 09:36
- Re: [83attendees] Usual recreational venue diatribe (was Ground transportation from/to CDG), Iljitsch van Beijnum, 09:25
- 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, 09:08
- 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), 08:43
- 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, 08:36
- 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, 08:13
- Re: GenART last call review of draft-ietf-behave-nat64-learn-analysis-03, jouni korhonen, 07:50
- 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, 06:57
- 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, 06:39
- Re: shared address space... a reality!, Turchanyi Geza, 05:51
- 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), 05:44
- 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), 05:24
- Re: shared address space... a reality!, Roger Jørgensen, 03:32
- Re: shared address space... a reality!, Måns Nilsson, 02:47
- 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, 02:46
March 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, 17:24
- 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, 17:19
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Noel Chiappa, 14:53
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Eliot Lear, 14:44
- Gen-ART LC review of draft-melnikov-smtp-priority-09, Roni Even, 14:26
- הנדון: 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), 14:10
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Joel M. Halpern, 14:05
- 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, 13:27
- RE: Last Call: <draft-ietf-bmwg-protection-meth-09.txt> (Methodology for benchmarking MPLS protection mechanisms) to Informational RFC, Gregory Mirsky, 10:11
- Re: Gen-ART LC/Telechat review of draft-reschke-http-status-308-05, Julian Reschke, 10:11
- Re: [savi] Last Call: <draft-ietf-savi-dhcp-12.txt> (SAVI Solution for DHCP) to Proposed Standard, eric levy-abegnoli, 10:10
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the"X-" Prefix in Application Protocols) to Best Current Practice, t.petch, 09:17
- GenART last call review of draft-ietf-behave-nat64-learn-analysis-03, Roni Even, 08:52
March 12, 2012
- IETF Mail Archive Tools RFI, Ray Pelletier, 23:43
- Re: Gen-ART LC/Telechat review of draft-reschke-http-status-308-05, Peter Saint-Andre, 12:48
- Re: Gen-ART LC/Telechat review of draft-reschke-http-status-308-05, Julian Reschke, 12:17
- Gen-ART LC/Telechat review of draft-reschke-http-status-308-05, Ben Campbell, 11:15
- 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, 03:32
March 09, 2012
- IETF83 Audio Streaming info, Nick Kukich, 13:32
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), John Scudder, 10:25
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 05:58
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Stephane Bortzmeyer, 04:02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Stephane Bortzmeyer, 03:58
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 00:05
March 08, 2012
- Weekly posting summary for ietf(_at_)ietf(_dot_)org, Thomas Narten, 23:53
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 22:22
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector, 21:39
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 20:57
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 20:23
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 20:04
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 19:16
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 19:08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 19:08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 18:00
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 17:22
- Re: Add a link to the HTML version in i-d-announce mails ?, Martin Rex, 15:49
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Barry Leiba, 15:34
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Jari Arkko, 15:14
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 13:57
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 12:45
- 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, 12:02
- 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, 11:43
- 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, 11:43
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp), Jari Arkko, 11:26
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Tony Finch, 08:06
- RE: provisioning software, was DNS RRTYPEs, the difficulty with, Tony Finch, 08:02
March 07, 2012
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 21:20
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 20:11
- RE: provisioning software, was DNS RRTYPEs, the difficulty with, Murray S. Kucherawy, 18:44
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 17:28
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 17:07
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 17:04
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector, 16:55
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 16:48
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 16:41
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Andrew Sullivan, 16:39
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 16:22
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 15:50
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 15:47
- RE: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Aissaoui, Mustapha (Mustapha), 14:10
- Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Andrew G. Malis, 14:09
- RE: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Aissaoui, Mustapha (Mustapha), 14:08
- RE: tsv-dir review of draft-garcia-shim6-applicability-03, Alberto García, 14:08
- Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Stewart Bryant, 13:46
- Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Thomas Nadeau, 13:32
- Re: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard, Stewart Bryant, 11:48
- 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, 11:03
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 09:14
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely, 06:57
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (DeprecatingUse of the "X-" Prefix in Application Protocols) to BestCurrent Practice, t.petch, 04:08
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 02:58
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 01:55
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Patrik Fältström, 01:13
- RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens, 00:26
- 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, 00:20
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 00:05
March 06, 2012
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham, 23:58
- 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, 23:54
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Martin Rex, 23:40
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 23:04
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Randy Bush, 22:22
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 22:12
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham, 22:11
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 21:47
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 20:59
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randy Bush, 20:53
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham, 20:51
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 20:50
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 20:43
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens, 20:38
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Mark Nottingham, 20:02
- Re: [IETF] Add a link to the HTML version in i-d-announce mails ?, Warren Kumari, 19:03
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens, 19:02
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Barry Leiba, 18:54
- Re: [IETF] Add a link to the HTML version in i-d-announce mails ?, Barry Leiba, 18:43
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>, Randall Gellens, 18:17
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John Levine, 18:09
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens, 18:03
- 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, 17:50
- 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, 17:46
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>, Peter Saint-Andre, 17:42
- 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, 17:32
- Re: Add a link to the HTML version in i-d-announce mails ?, Tim Bray, 17:32
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Randall Gellens, 17:19
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Scott Kitterman, 16:32
- 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, 16:31
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Scott Kitterman, 16:25
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 16:20
- 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, 16:20
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 16:16
- Re: Add a link to the HTML version in i-d-announce mails ?, Russ Housley, 16:16
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 16:09
- Re: Add a link to the HTML version in i-d-announce mails ?, Yoav Nir, 16:03
- Re: Add a link to the HTML version in i-d-announce mails ?, Julian Reschke, 15:44
- RE: tsv-dir review of draft-garcia-shim6-applicability-03, Alberto García, 14:02
- RE: Add a link to the HTML version in i-d-announce mails ?, Murray S. Kucherawy, 12:34
- RE: Add a link to the HTML version in i-d-announce mails ?, Murray S. Kucherawy, 12:33
- Re: WG Review: INtermediary-safe SIP session ID (insipid), Barry Leiba, 12:30
- Re: Last Call: <draft-snell-atompub-tombstones-15.txt> (The Atom "deleted-entry" Element) to Proposed Standard, Peter Saint-Andre, 11:49
- Re: Add a link to the HTML version in i-d-announce mails ?, Barry Leiba, 11:45
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Scott Kitterman, 11:40
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely, 11:35
- RE: tsv-dir review of draft-garcia-shim6-applicability-03, Dan Wing, 11:25
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 11:04
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Tony Finch, 11:00
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Rolf E. Sonneveld, 10:35
- 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, 10:26
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely, 10:03
- Re: [IETF] Add a link to the HTML version in i-d-announce mails ?, Warren Kumari, 10:03
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 09:33
- Re: Add a link to the HTML version in i-d-announce mails ?, Yoav Nir, 09:27
- Re: Add a link to the HTML version in i-d-announce mails ?, Xavier Marjou, 09:11
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 09:01
- Re: Add a link to the HTML version in i-d-announce mails ?, Tony Hansen, 08:44
- Re: Add a link to the HTML version in i-d-announce mails ?, Riccardo Bernardini, 08:36
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 08:36
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 08:35
- Re: Add a link to the HTML version in i-d-announce mails ?, Dave Crocker, 08:31
- Re: Add a link to the HTML version in i-d-announce mails ?, Randy Bush, 08:24
- Re: Add a link to the HTML version in i-d-announce mails ?, Russ Housley, 08:13
- Re: Add a link to the HTML version in i-d-announce mails ?, Hector, 08:06
- Re: Add a link to the HTML version in i-d-announce mails ?, Julian Reschke, 08:04
- Re: Add a link to the HTML version in i-d-announce mails ?, Riccardo Bernardini, 08:02
- Re: Add a link to the HTML version in i-d-announce mails ?, Yoav Nir, 07:56
- Re: Add a link to the HTML version in i-d-announce mails ?, Simon Perreault, 07:54
- Re: Add a link to the HTML version in i-d-announce mails ?, Julian Reschke, 07:52
- Add a link to the HTML version in i-d-announce mails ?, Xavier Marjou, 07:41
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Tony Finch, 07:15
- 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, 05:47
- 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, 05:33
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov, 04:52
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov, 04:51
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov, 04:51
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 00:19
March 05, 2012
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 23:42
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Patrik Fältström, 23:00
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John Levine, 22:47
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 22:13
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 21:23
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 21:12
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 21:00
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 20:30
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 20:25
- 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, Andrew G. Malis, 17:54
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 13:41
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector Santos, 13:20
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely, 13: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, 12:00
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John Levine, 11:11
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Patrik Fältström, 11:00
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, SM, 10:30
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 10:08
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 09:56
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 09:47
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, John R. Levine, 09:42
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 09:15
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov, 08:45
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov, 08:11
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov, 05:59
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Alexey Melnikov, 05:12
March 03, 2012
- 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), 12:50
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 12:23
- Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with, Hector, 12:22
- 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, 12:11
- 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, 12:04
- Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with, John Levine, 11:44
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 10:42
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector, 10:39
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Scott Kitterman, 10:29
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Hector, 10:23
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Patrik Fältström, 10:05
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 10:02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Alessandro Vesely, 05:20
March 02, 2012
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Hector, 23:54
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, John Levine, 22:12
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Hector, 21:17
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 18:55
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 18:54
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>, Randall Gellens, 18:48
- 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), Bernard Aboba, 18:33
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 17:13
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Mark Andrews, 16:49
- Updates to draft-farrresnickel-ipr-sanctions, Adrian Farrel, 15:44
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Doug Barton, 13:09
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, ned+ietf, 12:49
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 12:48
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Doug Barton, 12:47
- 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, 12:44
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Paul Hoffman, 12:34
- 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, 12:28
- 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, 12:17
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, Doug Barton, 12:10
- RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Murray S. Kucherawy, 12:00
- 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, 11:37
- 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, 11:21
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 11:19
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 11:02
- Re: provisioning software, was DNS RRTYPEs, the difficulty with, John R. Levine, 11:00
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 09:23
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Hector, 08:51
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 08:46
- Re: DNS RRTYPEs, the difficulty with, Doug Barton, 03:32
- 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, 01:08
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, ned+ietf, 00:33
March 01, 2012
- Weekly posting summary for ietf(_at_)ietf(_dot_)org, Thomas Narten, 23:54
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Randy Bush, 20:28
- 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, 18:15
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Scott Kitterman, 18:15
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, John Leslie, 17:54
- 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, 17:52
- RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Murray S. Kucherawy, 17:38
- Re: [marf] Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, SM, 17:25
- 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, 17:05
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 17: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, 16:43
- RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Murray S. Kucherawy, 16:16
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, SM, 16:11
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Mark Nottingham, 16:10
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 15:56
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 15:53
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Barry Leiba, 15:48
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, SM, 15:37
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 15:15
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Barry Leiba, 15:01
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard, Barry Leiba, 14:50
- 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), 13:34
- 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, 13: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, Russ Housley, 13:12
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Paul Hoffman, 13:09
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Paul Hoffman, 13:08
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice, Scott Kitterman, 13: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), 12:47
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Peter Saint-Andre, 12:44
- 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, 12:42
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Peter Saint-Andre, 12:41
- 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, 12:40
- 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), 12:39
- 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, 12:35
- 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), 12:34
- 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, 12:29
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Dave Crocker, 12:19
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), SM, 12:09
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, SM, 12:08
- 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), 12:07
- 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, 12:02
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Nick Hilliard, 12:02
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Tim Bray, 11:58
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Peter Saint-Andre, 11:51
- 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), 11:26
- 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), 11:23
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 10:55
- 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, 10:43
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Henrik Nordström, 10:22
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Henrik Nordström, 10:22
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Henrik Nordström, 10:21
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Henrik Nordström, 10:20
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis), Adrien de Croy, 10:19
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, SM, 10:18
- 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, 10:06
- 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), 09: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), 09: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, Kyung-Yeop Hong (hongk), 09:14
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Scott Kitterman, 08:22
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, Barry Leiba, 08:12
- Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple MailTransfer Protocol extension for Message Transfer Priorities)to Proposed Standard, t.petch, 04:46
- Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard, SM, 00:36