IETF Discussion
[Prev Page][Next Page]
- Re: [IETF] Re: shared address space... a reality!, (continued)
- RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC,
yang . jian90
- Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp),
Noel Chiappa
- Gen-ART LC review of draft-melnikov-smtp-priority-09,
Roni Even
- הנדון: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC,
Sprecher, Nurit (NSN - IL/Hod HaSharon)
- RE: Last Call: <draft-ietf-bmwg-protection-meth-09.txt> (Methodology for benchmarking MPLS protection mechanisms) to Informational RFC,
Gregory Mirsky
- Re: [savi] Last Call: <draft-ietf-savi-dhcp-12.txt> (SAVI Solution for DHCP) to Proposed Standard,
eric levy-abegnoli
- GenART last call review of draft-ietf-behave-nat64-learn-analysis-03,
Roni Even
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the"X-" Prefix in Application Protocols) to Best Current Practice,
t.petch
- IETF Mail Archive Tools RFI,
Ray Pelletier
- Gen-ART LC/Telechat review of draft-reschke-http-status-308-05,
Ben Campbell
- IETF83 Audio Streaming info,
Nick Kukich
- Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice,
John C Klensin
- Re: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard,
Stewart Bryant
Fwd: Last Call: <draft-ietf-pwe3-pw-typed-wc-fec-03.txt> (LDP Typed Wildcard FEC for PWid and Generalized PWid FEC Elements) to Proposed Standard,
Stewart Bryant
Re: WG Review: INtermediary-safe SIP session ID (insipid),
Barry Leiba
Re: Last Call: <draft-snell-atompub-tombstones-15.txt> (The Atom "deleted-entry" Element) to Proposed Standard,
Peter Saint-Andre
Add a link to the HTML version in i-d-announce mails ?,
Xavier Marjou
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>,
Randall Gellens
Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM),
Bernard Aboba
Updates to draft-farrresnickel-ipr-sanctions,
Adrian Farrel
Re: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC,
Julien Meuric
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard,
SM
RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard,
Murray S. Kucherawy
Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard,
Barry Leiba
Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice,
Scott Kitterman
Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC,
Kyung-Yeop Hong (hongk)
Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard,
SM
Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard,
Scott Kitterman
RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard,
Murray S. Kucherawy
Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard,
Scott Kitterman
Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard,
Scott Kitterman
RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard,
Murray S. Kucherawy
tsv-dir review of draft-garcia-shim6-applicability-03,
Dan Wing
Gen-ART LC/Telechat review of draft-ietf-mext-mip6-tls-03,
Ben Campbell
ISOC Fellowship to the IETF (IETF 84 and 85),
Steve Conte
DNS Rule Transmission is a new tool in anti-spam controls,
Todd Glassey
Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC,
Stewart Bryant
Re: [pcp] Last Call: <draft-ietf-pcp-base-23.txt> (Port Control Protocol (PCP)) to Proposed Standard,
Masataka Ohta
draft-weil-shared-transition-space-request,
The IESG
RE: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC,
Daniel Cohn
Fwd: Re: [tz] Astrolabe dismisses suit.,
Eliot Lear
Gen-ART LC review of draft-ietf-pcn-3-in-1-encoding-08,
Roni Even
A nuance of interoperability reports,
Murray S. Kucherawy
Conclusion of Last Call for draft-ietf-sieve-convert and draft-ietf-sieve-notify-sip-message,
Pete Resnick
Explanation of the OCSP sign request,
Robert Hernady
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis),
Stephen Farrell
<Possible follow-ups>
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis),
RJ Atkinson
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis),
Doug Barton
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis),
Mark Andrews
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis),
Patrik Fältström
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis),
Andrew Sullivan
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis),
Patrik Fältström
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis),
John C Klensin
- DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)),
Andrew Sullivan
- Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)),
Scott Kitterman
- Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)),
Andrew Sullivan
- Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)),
Scott Kitterman
- Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)),
Edward Lewis
- Re: DNS RRTYPEs, the difficulty with,
Alessandro Vesely
- Re: DNS RRTYPEs, the difficulty with,
Hector
- Re: DNS RRTYPEs, the difficulty with,
Patrik Fältström
- RE: DNS RRTYPEs, the difficulty with,
Murray S. Kucherawy
- Re: DNS RRTYPEs, the difficulty with,
Paul Hoffman
- Re: DNS RRTYPEs, the difficulty with,
Doug Barton
- Re: DNS RRTYPEs, the difficulty with,
John Levine
- Re: DNS RRTYPEs, the difficulty with,
Paul Hoffman
- Re: DNS RRTYPEs, the difficulty with,
Doug Barton
- Re: DNS RRTYPEs, the difficulty with,
Scott Kitterman
- RE: DNS RRTYPEs, the difficulty with,
Murray S. Kucherawy
- Re: DNS RRTYPEs, the difficulty with,
John R. Levine
- Re: DNS RRTYPEs, the difficulty with,
Doug Barton
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John R. Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Doug Barton
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
ned+ietf
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John R. Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Alessandro Vesely
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
ned+ietf
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Patrik Fältström
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Scott Kitterman
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Patrik Fältström
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Alessandro Vesely
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Hector Santos
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
ned+ietf
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Alessandro Vesely
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
ned+ietf
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Alessandro Vesely
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
ned+ietf
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Patrik Fältström
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Tony Finch
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
ned+ietf
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John R. Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
ned+ietf
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Tony Finch
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John R. Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John R. Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John R. Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Randy Bush
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Patrik Fältström
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John R. Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John R. Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John R. Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Stephane Bortzmeyer
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Andrew Sullivan
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Hector
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Alessandro Vesely
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Scott Kitterman
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
John R. Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Martin Rex
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Martin Rex
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- RE: provisioning software, was DNS RRTYPEs, the difficulty with,
Murray S. Kucherawy
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Martin Rex
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Tony Finch
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Stephane Bortzmeyer
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- RE: provisioning software, was DNS RRTYPEs, the difficulty with,
Tony Finch
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Martin Rex
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Martin Rex
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Martin Rex
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Martin Rex
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Martin Rex
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Martin Rex
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Hector
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Martin Rex
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Mark Andrews
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Hector
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
ned+ietf
- Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with,
John Levine
- Re: provisioning software, was DNS RRTYPEs, the difficulty with,
Hector
- Re: DNS RRTYPEs, the difficulty with,
Scott Kitterman
- Re: DNS RRTYPEs, the difficulty with,
John Levine
- Re: DNS RRTYPEs, the difficulty with,
Hector
- Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)),
Mark Andrews
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis),
Doug Barton
Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis),
Peter Saint-Andre
Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard,
Julian Reschke
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
IRTF IPR Disclosure Rules,
Eggert, Lars
SEARS - Search Engine Address Resolution Service (and Protocol),
Todd Glassey
re: [core] Last Call: <draft-ietf-core-link-format-11.txt> (CoRE Link Format) to Proposed Standard,
Don Sturek
draft-weil last call: IANA Reserved IPv4 Prefix for Shared Address Space,
Scott A Griffith
Re: IETF Last Calls and Godwin-like rules,
Noel Chiappa
Re: WG Review: Recharter of Locator/ID Separation Protocol (lisp),
Thomas Narten
Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>,
Lea Roberts
Last Call: draft-weil-shared-transition-space-request-14.txt (IANA Reserved IPv4 Prefix for Shared Address Space),
William Hale
Re: Last Call: <draft-garcia-shim6-applicability-03.txt> (Applicability Statement for the Level 3 Multihoming Shim Protocol (Shim6)) to Informational RFC,
Brian E Carpenter
Re: Variable length internet addresses in TCP/IP: history,
Noel Chiappa
Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP',
Erichsen, Kirk
Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC,
Livingood, Jason
Auth48 comments on draft-ietf-pwe3-static-pw-status-10,
Bocci, Matthew (Matthew)
Reminder: T-shirt Design Contest for IETF 83,
Alexa Morris
Re: Another last call for draft-weil,
Owen DeLong
Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP,
Daryl Tanner
[Index of Archives]
[IETF Annoucements]
[IP Storage]
[Linux SCTP]
[IETF]
