IETF Discussion

• Thread Index

• Re: whine, whine, whine
  • From: RJ Atkinson
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: t.petch
• Re: whine, whine, whine
  • From: Klaas Wierenga
• RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: John C Klensin
• Re: location preferences
  • From: Dave CROCKER
• Re: whine, whine, whine
  • From: Eliot Lear
• Re: whine, whine, whine
  • From: Ray Bellis
• Re: whine, whine, whine
  • From: John Levine
• Re: whine, whine, whine
  • From: Tim Chown
• Re: whine, whine, whine
  • From: CAUCHIE Grégory
• Re: whine, whine, whine
  • From: Ray Bellis
• RE: whine, whine, whine
  • From: Christer Holmberg
• Re: whine, whine, whine
  • From: Simon Perreault
• Re: whine, whine, whine
  • From: Simon Perreault
• RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Adrian Farrel
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Lou Berger
• Re: location preferences
  • From: Joel Jaeggli
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Joel Jaeggli
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Glen Zorn
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Glen Zorn
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Joel Jaeggli
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Keith Moore
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Glen Zorn
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Thomas Heide Clausen
• Re: whine, whine, whine
  • From: John R. Levine
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: John Levine
• Re: whine, whine, whine
  • From: Randall Gellens
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Mark Andrews
• getting there
  • From: John Levine
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Henk Uijterwaal
• Thanks! (was: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?)
  • From: Keith Moore
• RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Murray S. Kucherawy
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Joel Jaeggli
• RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Murray S. Kucherawy
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Glen Zorn
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Glen Zorn
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Glen Zorn
• whine, whine, whine
  • From: John Levine
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Stephan Wenger
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Henk Uijterwaal
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Randall Gellens
• Re: location preferences
  • From: James M. Polk
• Re: Getting to Quebec City
  • From: Julien Laganier
• Re: location preferences
  • From: Dave CROCKER
• Re: Getting to Quebec City
  • From: Randall Gellens
• RE: location preferences
  • From: Murray S. Kucherawy
• Re: location preferences
  • From: Dave CROCKER
• location preferences (was: Has anyone found a hotel for Quebec City that isn't exorbitant?)
  • From: Andrew Sullivan
• RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Mary Barnes
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: John C Klensin
• IETF-meta (Was: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?)
  • From: Richard L. Barnes
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Simon Perreault
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Michael Richardson
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Thomas Nadeau
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Ole Jacobsen
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Keith Moore
• Re: [codec] Last Call: <draft-ietf-codec-requirements-04.txt> (Codec Requirements) to Informational RFC
  • From: Carsten Bormann
• RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: John E Drake
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Henk Uijterwaal
• Gen-ART Telechat Review of draft-ietf-dime-ikev2-psk-diameter-08
  • From: Ben Campbell
• Gen-ART LC Review of draft-law-rfc4869bis-01
  • From: Ben Campbell
• Gen-ART LC Review of draft-ietf-v6ops-6to4-to-historic-04
  • From: Ben Campbell
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Boris Zbarsky
• Re: [codec] Last Call: <draft-ietf-codec-requirements-04.txt> (Codec Requirements) to Informational RFC
  • From: Cullen Jennings
• Re: Getting to Quebec City
  • From: Simon Perreault
• Re: Getting to Quebec City
  • From: Bob Hinden
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Glen Zorn
• Re: Getting to Quebec City
  • From: Tim Chown
• Re: Getting to Quebec City
  • From: John R. Levine
• Re: Getting to Quebec City
  • From: Ole Jacobsen
• Re: Getting to Quebec City
  • From: Alastair Johnson
• Re: Getting to Quebec City
  • From: Michael StJohns
• Re: Getting to Quebec City
  • From: Ole Jacobsen
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Scott Brim
• Re: Getting to Quebec City
  • From: John R. Levine
• Re: Getting to Quebec City
  • From: Mary Barnes
• Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: John Levine
• Has anyone found a hotel for Quebec City that isn't exorbitant?
  • From: Keith Moore
• Re: Getting to Quebec City
  • From: Glen Zorn
• Re: Getting to Quebec City
  • From: Glen Zorn
• Re: Getting to Quebec City
  • From: Hamza GHARSALLAH
• Re: Getting to Quebec City
  • From: Andrew Sullivan
• Re: Getting to Quebec City
  • From: Melinda Shore
• Re: Getting to Quebec City
  • From: Eric Rescorla
• Getting to Quebec City
  • From: John Levine
• Re: [codec] Last Call: <draft-ietf-codec-requirements-04.txt> (Codec Requirements) to Informational RFC
  • From: Donald Eastlake
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: John C Klensin
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Julian Reschke
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Boris Zbarsky
• RE: [codec] Last Call: <draft-ietf-codec-requirements-04.txt> (Codec Requirements) to Informational RFC
  • From: Christian Hoene
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Boris Zbarsky
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Michael Richardson
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Lachlan Hunt
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Eliot Lear
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Julian Reschke
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Julian Reschke
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• RE: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Murray S. Kucherawy
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Mykyta Yevstifeyev
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Mykyta Yevstifeyev
• Re: [apps-discuss] Last Call: <draft-ietf-appsawg-rfc3536bis-02.txt> (Terminology Used in Internationalization in the IETF) to BCP
  • From: Barry Leiba
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Mykyta Yevstifeyev
• Re: [apps-discuss] Last Call: <draft-ietf-appsawg-rfc3536bis-02.txt> (Terminology Used in Internationalization in the IETF) to BCP
  • From: Mykyta Yevstifeyev
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Mark Smith
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Gert Doering
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Mark Smith
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• Re: [Gen-art] Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
  • From: Ben Campbell
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Boris Zbarsky
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Joel M. Halpern
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Julian Reschke
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Lachlan Hunt
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Julian Reschke
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Lachlan Hunt
• Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
  • From: John Levine
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Sabahattin Gucukoglu
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Mark Andrews
• Re: one data point regarding native IPv6 support
  • From: Mark Andrews
• IETF Fellowship Announcement (IETF 82 and 83)
  • From: Steve Conte
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Andrew Sullivan
• Re: [Gen-art] Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
  • From: Avi Lior
• Re: Liaison and request for review of ITU-T document
  • From: Ralph Droms
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Mark Smith
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Mark Smith
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Erik Kline
• RE: Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
  • From: Cakulev, Violeta (Violeta)
• RE: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
  • From: Cakulev, Violeta (Violeta)
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Mykyta Yevstifeyev
• RE: one data point regarding native IPv6 support
  • From: Christian Huitema
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Julian Reschke
• Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
  • From: Mykyta Yevstifeyev
• Re: one data point regarding native IPv6 support
  • From: Mark Andrews
• Re: one data point regarding native IPv6 support
  • From: Noel Chiappa
• Re: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
  • From: Yaron Sheffer
• RE: one data point regarding native IPv6 support
  • From: Tony Hain
• Re: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
  • From: Yaron Sheffer
• Re: one data point regarding native IPv6 support
  • From: Keith Moore
• Re: one data point regarding native IPv6 support
  • From: Joel Jaeggli
• Re: one data point regarding native IPv6 support
  • From: Keith Moore
• Re: one data point regarding native IPv6 support
  • From: Joel Jaeggli
• Re: one data point regarding native IPv6 support
  • From: Keith Moore
• RE: one data point regarding native IPv6 support
  • From: Tony Hain
• Re: one data point regarding native IPv6 support
  • From: Keith Moore
• Re: one data point regarding native IPv6 support
  • From: Ole Troan
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: james woodyatt
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• Re: [PCN] Last Call: <draft-ietf-pcn-cl-edge-behaviour-08.txt> (PCN Boundary Node Behaviour for the Controlled Load (CL) Mode of Operation) to Informational RFC
  • From: Tom Taylor
• Re: one data point regarding native IPv6 support
  • From: Tim Chown
• Re: one data point regarding native IPv6 support
  • From: Keith Moore
• RE: one data point regarding native IPv6 support
  • From: Michel Py
• Re: one data point regarding native IPv6 support
  • From: Keith Moore
• Nomcom 2011-12: Call for Volunteers
  • From: Suresh Krishnan
• Re: one data point regarding native IPv6 support
  • From: t.petch
• Re: one data point regarding native IPv6 support
  • From: Steven Bellovin
• Re: one data point regarding native IPv6 support
  • From: Ofer Inbar
• Re: one data point regarding native IPv6 support
  • From: Joel Jaeggli
• Re: one data point regarding native IPv6 support
  • From: Joel Jaeggli
• Re: RE: RE: one data point regarding native IPv6 support
  • From: Noel Chiappa
• Re: one data point regarding native IPv6 support
  • From: Noel Chiappa
• Re: one data point regarding native IPv6 support
  • From: t.petch
• Re: RE: RE: one data point regarding native IPv6 support
  • From: Cameron Byrne
• Re: one data point regarding native IPv6 support
  • From: t.petch
• Re: one data point regarding native IPv6 support
  • From: Jari Arkko
• RE: RE: one data point regarding native IPv6 support
  • From: Michel Py
• Re: RE: one data point regarding native IPv6 support
  • From: Cameron Byrne
• RE: one data point regarding native IPv6 support
  • From: Michel Py
• Re: one data point regarding native IPv6 support
  • From: Keith Moore
• Re: one data point regarding native IPv6 support
  • From: Doug Barton
• RE: one data point regarding native IPv6 support
  • From: Michel Py
• RE: one data point regarding native IPv6 support
  • From: Michel Py
• Re: one data point regarding native IPv6 support
  • From: Nathaniel Borenstein
• TSVDIR review of draft-ietf-dnsext-rfc2672bis-dname
  • From: Joe Touch
• Re: Last Call: <draft-ietf-pppext-trill-protocol-06.txt> (PPP TRILL Protocol Control Protocol) to Proposed Standard
  • From: Jari Arkko
• Bring Your Own Server
  • From: Krishna Birth
• Re: one data point regarding native IPv6 support
  • From: Keith Moore
• Re: one data point regarding native IPv6 support
  • From: John R. Levine
• Re: one data point regarding native IPv6 support
  • From: Michael Richardson
• Re: one data point regarding native IPv6 support
  • From: Hamza GHARSALLAH
• Re: one data point regarding native IPv6 support
  • From: John Levine
• Re: one data point regarding native IPv6 support
  • From: Keith Moore
• Re: one data point regarding native IPv6 support
  • From: ned+ietf
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Mykyta Yevstifeyev
• Re: one data point regarding native IPv6 support
  • From: Masataka Ohta
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Julian Reschke
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Mykyta Yevstifeyev
• RE: one data point regarding native IPv6 support
  • From: Michel Py
• Re: one data point regarding native IPv6 support
  • From: John Levine
• Itojun Service Award Announcement
  • From: Jun Murai
• Re: one data point regarding native IPv6 support
  • From: Mark Andrews
• Re: one data point regarding native IPv6 support
  • From: Masataka Ohta
• Re: one data point regarding native IPv6 support
  • From: Mark Andrews
• Re: one data point regarding native IPv6 support
  • From: Mark Andrews
• Re: one data point regarding native IPv6 support
  • From: John C Klensin
• Re: one data point regarding native IPv6 support
  • From: james woodyatt
• Re: one data point regarding native IPv6 support
  • From: Joel Jaeggli
• Re: Liaison and request for review of ITU-T document
  • From: Brian E Carpenter
• Re: one data point regarding native IPv6 support
  • From: Masataka Ohta
• Re: one data point regarding native IPv6 support
  • From: Brian E Carpenter
• Re: one data point regarding native IPv6 support
  • From: Dave Cridland
• Re: one data point regarding native IPv6 support
  • From: John C Klensin
• RFP for Secretariat Services
  • From: IETF Administrative Director
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: james woodyatt
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: one data point regarding native IPv6 support
  • From: james woodyatt
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Keith Moore
• RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Templin, Fred L
• Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08
  • From: Elwyn Davies
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Joel Jaeggli
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Michael Richardson
• Re: one data point regarding native IPv6 support
  • From: Michael Richardson
• Re: one data point regarding native IPv6 support
  • From: Brian E Carpenter
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: james woodyatt
• RE: one data point regarding native IPv6 support
  • From: John C Klensin
• Re: one data point regarding native IPv6 support
  • From: Brian E Carpenter
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Noel Chiappa
• Re: one data point regarding native IPv6 support
  • From: Nathaniel Borenstein
• RE: one data point regarding native IPv6 support
  • From: Worley, Dale R (Dale)
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Lorenzo Colitti
• RE: one data point regarding native IPv6 support
  • From: Tony Hain
• Re: Last Call: <draft-iesg-rfc1150bis-01.txt> (Conclusion of FYI RFC Sub-series) to Informational RFC
  • From: Mykyta Yevstifeyev
• Re: one data point regarding native IPv6 support
  • From: John C Klensin
• Re: one data point regarding native IPv6 support
  • From: Keith Moore
• Re: one data point regarding native IPv6 support
  • From: Brian E Carpenter
• Re: one data point regarding native IPv6 support
  • From: Bert (IETF) Wijnen
• Re: one data point regarding native IPv6 support
  • From: Thomas Nadeau
• Re: one data point regarding native IPv6 support
  • From: TJ
• Re: one data point regarding native IPv6 support
  • From: otunte otueneh
• Re: one data point regarding native IPv6 support
  • From: Stefan Winter
• Re: one data point regarding native IPv6 support
  • From: otunte otueneh
• Re: one data point regarding native IPv6 support
  • From: Sabahattin Gucukoglu
• Re: one data point regarding native IPv6 support
  • From: Stefan Winter
• Re: one data point regarding native IPv6 support
  • From: Roger Jørgensen
• Re: one data point regarding native IPv6 support
  • From: Hector Santos
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• RE: one data point regarding native IPv6 support
  • From: Michel Py
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Martin Rex
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Mark Andrews
• Re: one data point regarding native IPv6 support
  • From: Masataka Ohta
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Randy Presuhn
• Re: one data point regarding native IPv6 support
  • From: Mark Andrews
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Keith Moore
• Re: one data point regarding native IPv6 support
  • From: ned+ietf
• Re: [v6ops] Last Call:
  • From: Martin Rex
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Tim Chown
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Brian E Carpenter
• Re: one data point regarding native IPv6 support
  • From: james woodyatt
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• one data point regarding native IPv6 support
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: james woodyatt
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Randy Presuhn
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: TJ
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Randy Presuhn
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Brian E Carpenter
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Philip Homburg
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational RFC
  • From: Gert Doering
• RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational RFC
  • From: Gunter Van de Velde (gvandeve)
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Gert Doering
• Re: [Gen-art] Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
  • From: Ben Campbell
• RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Dmitry Anipko
• RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: George, Wesley
• Re: Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
  • From: Scott Rose
• Re: Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
  • From: Scott Rose
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Noel Chiappa
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational RFC
  • From: Joel Jaeggli
• RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Christian Huitema
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational RFC
  • From: Roger Jørgensen
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational RFC
  • From: Joel Jaeggli
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: compromise on the 6to4->Historic debate
  • From: Keith Moore
• Re: compromise on the 6to4->Historic debate
  • From: Mark Andrews
• Re: compromise on the 6to4->Historic debate
  • From: Keith Moore
• Re: compromise on the 6to4->Historic debate
  • From: Mark Andrews
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: james woodyatt
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Tim Chown
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Joel Jaeggli
• compromise on the 6to4->Historic debate
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Martin Rex
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Randy Presuhn
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Brian E Carpenter
• Re: Summary for IESG last call to 5892bis draft
  • From: Pete Resnick
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: james woodyatt
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Noel Chiappa
• Summary for IESG last call to 5892bis draft
  • From: Jiankang YAO
• Re: Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: Vint Cerf
• Gen-ART Review of draft-ietf-ccamp-gmpls-vcat-lcas-13
  • From: kathleen.moriarty
• Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
  • From: Ben Campbell
• RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: George, Wesley
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Martin Rex
• Re: Last Call: <draft-ietf-dhc-subnet-alloc-12.txt> (Subnet Allocation Option) to Informational RFC
  • From: Alexandru Petrescu
• Re: Contents of the IDNA Derived Properties registry (was; Re: Gen-ART LC review of draft-faltstrom-5892bis-04)
  • From: Russ Housley
• Contents of the IDNA Derived Properties registry (was; Re: Gen-ART LC review of draft-faltstrom-5892bis-04)
  • From: John C Klensin
• Re: Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: John C Klensin
• Re: Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: Alexey Melnikov
• Re: Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: Alexey Melnikov
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Dave Cridland
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Andrew Sullivan
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Pete Resnick
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Peter Saint-Andre
• Re: Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: Paul Hoffman
• Re: Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: John C Klensin
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: Paul Hoffman
• Liaison and request for review of ITU-T document
  • From: Ralph Droms
• RE: Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: rontlv
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
  • From: Martin Rex
• Re: Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: Paul Hoffman
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4 to Historic status) to Informational RFC
  • From: Brian E Carpenter
• RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: George, Wesley
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Cameron Byrne
• RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: George, Wesley
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Gert Doering
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Re: New Non-WG Mailing List: fun -- FUture home Networking (FUN)
  • From: John C Klensin
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: TJ
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: TJ
• RE: Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: rontlv
• Re: TSVDIR Review for draft-ohba-pana-relay-03
  • From: Yoshifumi Nishida
• Re: Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Ole Troan
• Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Tim Chown
• Re: New Non-WG Mailing List: fun -- FUture home Networking (FUN)
  • From: Jari Arkko
• Re: New Non-WG Mailing List: fun -- FUture home Networking (FUN)
  • From: Barry Leiba
• Re: New Non-WG Mailing List: fun -- FUture home Networking (FUN)
  • From: John C Klensin
• Re: Proposed text for IESG Handling of Historic Status
  • From: Fred Baker
• Re: Proposed text for IESG Handling of Historic Status
  • From: Barry Leiba
• Re: Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: TJ
• Re: Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: Paul Hoffman
• Subversion troubles?
  • From: Stuart Cheshire
• Re: New Non-WG Mailing List: fun -- FUture home Networking (FUN)
  • From: Stephane Bortzmeyer
• Re: Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Sabahattin Gucukoglu
• Re: Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
  • From: Keith Moore
• Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
  • From: Ben Campbell
• Re: TSVDIR Review for draft-ohba-pana-relay-03
  • From: Yoshihiro Ohba
• Re: tsv-dir review of draft-ietf-behave-ftp64-10
  • From: Iljitsch van Beijnum
• Individual submission rationale - draft-brasher-ltasp-05
  • From: Damian L Brasher
• TSVDIR Review for draft-ohba-pana-relay-03
  • From: Yoshifumi Nishida
• Re: Could you build a linux distro?
  • From: Krishna Birth
• Could you build a linux distro?
  • From: Krishna Birth
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Alexey Melnikov
• RE: Proposed text for IESG Handling of Historic Status
  • From: Murray S. Kucherawy
• Re: Proposed text for IESG Handling of Historic Status
  • From: Mykyta Yevstifeyev
• Re: Proposed text for IESG Handling of Historic Status
  • From: Alexey Melnikov
• Re: Proposed text for IESG Processing of RFC Errata concerning RFC Metadata
  • From: Alexey Melnikov
• Re: Proposed text for IESG Handling of Historic Status
  • From: Alexey Melnikov
• tsv-dir review of draft-ietf-behave-ftp64-10
  • From: Fernando Gont
• RE: Second Last Call: <draft-ietf-dkim-mailinglists-11.txt> (DKIM And Mailing Lists) to BCP
  • From: Murray S. Kucherawy
• Re: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
  • From: Yaron Sheffer
• Re: Second Last Call: <draft-ietf-dkim-mailinglists-11.txt> (DKIM And Mailing Lists) to BCP
  • From: John Levine
• Applied Networking Research Prize awards for IETF-81
  • From: Lars Eggert
• Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Scott Rose
• Re: Proposed text for IESG Handling of Historic Status
  • From: Mykyta Yevstifeyev
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Re: Proposed text for IESG Handling of Historic Status
  • From: John C Klensin
• Re: Proposed text for IESG Handling of Historic Status
  • From: SM
• Re: Proposed text for IESG Handling of Historic Status
  • From: Pete Resnick
• Re: Proposed text for IESG Handling of Historic Status
  • From: Scott Brim
• RE: Proposed text for IESG Handling of Historic Status
  • From: Murray S. Kucherawy
• Re: Proposed text for IESG Handling of Historic Status
  • From: John C Klensin
• Re: Proposed text for IESG Handling of Historic Status
  • From: Sam Hartman
• Proposed text for IESG Handling of Historic Status
  • From: Sean Turner
• Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Edward Lewis
• Proposed text for IESG Processing of RFC Errata concerning RFC Metadata
  • From: Stewart Bryant
• RE: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
  • From: Cakulev, Violeta (Violeta)
• Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Scott Rose
• Concerns about the recent IPR Statement from Alcatel Lucent Related to RFC 6073
  • From: Russ Housley
• Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Edward Lewis
• Re: Problems with online booking for the Hotel Delta Quebec?
  • From: John Levine
• Problems with online booking for the Hotel Delta Quebec?
  • From: Ross Finlayson
• Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Andrew Sullivan
• Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Edward Lewis
• Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Edward Lewis
• secdir review of draft-ietf-dnsext-rfc2672bis-dname-22.txt
  • From: Stephen Hanna
• Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Andrew Sullivan
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Lorenzo Colitti
• Re: Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Edward Lewis
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Alessandro Vesely
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Livingood, Jason
• Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Andrew Sullivan
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Livingood, Jason
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: John C Klensin
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: John C Klensin
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Tony Finch
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Lorenzo Colitti
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Lorenzo Colitti
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Gert Doering
• RE: tsv-dir review of draft-ietf-mpls-p2mp-lsp-ping
  • From: Shaleen Saxena (ssaxena)
• Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Paul Hoffman
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Pete Resnick
• Re: Last Call: <draft-ietf-pppext-trill-protocol-06.txt> (PPP TRILL Protocol Control Protocol) to Proposed Standard
  • From: Stewart Bryant
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Livingood, Jason
• Re: Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Andrew Sullivan
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Joel Jaeggli
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Joel Jaeggli
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: SM
• Re: Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
  • From: Pete Resnick
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Pete Resnick
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Dave CROCKER
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Livingood, Jason
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: Simon Josefsson
• Re: Last Call: <draft-ietf-behave-ftp64-10.txt> (An FTP ALG for IPv6-to-IPv4 translation) to Proposed Standard
  • From: Pekka Savola
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Joel Jaeggli
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Livingood, Jason
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Livingood, Jason
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: Pete Resnick
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Livingood, Jason
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: Simon Josefsson
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Livingood, Jason
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Livingood, Jason
• RE: tsv-dir review of draft-ietf-mpls-p2mp-lsp-ping
  • From: Adrian Farrel
• Fwd: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Dave CROCKER
• Re: [v6ops] Review of draft-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Livingood, Jason
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: John C Klensin
• Re: Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.txt> (IPv6 AAAA DNS Whitelisting Implications) to Informational RFC
  • From: Livingood, Jason
• Re: Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.txt> (IPv6 AAAA DNS Whitelisting Implications) to Informational RFC
  • From: Livingood, Jason
• Gen-ART LC review of draft-faltstrom-5892bis-04
  • From: Roni Even
• tsv-dir review of draft-ietf-mpls-lsp-ping-enhanced-dsmap
  • From: SCHARF, Michael
• tsv-dir review of draft-ietf-mpls-p2mp-lsp-ping
  • From: SCHARF, Michael
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: Simon Josefsson
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: Pete Resnick
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Re: Gen-ART LC review of draft-ietf-mpls-lsp-ping-enhanced-dsmap-09
  • From: Bjoern Hoehrmann
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: Simon Josefsson
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: Paul Hoffman
• Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: RJ Atkinson
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: Donald Eastlake
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: Simon Josefsson
• RE: [CCAMP] Last Call: <draft-ietf-ccamp-asymm-bw-bidir-lsps-bis-01.txt> (GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)) to Proposed Standard
  • From: Attila Takacs
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: Mark Davis ☕
• Gen-ART Telechat Review of draft-ietf-xcon-common-data-model-27
  • From: Ben Campbell
• Re: Gen-ART LC review of draft-ietf-mpls-lsp-ping-enhanced-dsmap-09
  • From: Nitin Bahadur
• Re: Last Call: <draft-faltstrom-5892bis-04.txt> (The Unicode code points and IDNA - Unicode 6.0) to Proposed Standard
  • From: John C Klensin
• Re: Problems using the default ftp settings in NroffEdit for diff display
  • From: Stefan Santesson
• Re: Gen-ART LC review of draft-ietf-grow-geomrt-01
  • From: Terry Manderson
• Re: Problems using the default ftp settings in NroffEdit for diff display
  • From: Martin Rex
• Problems using the default ftp settings in NroffEdit for diff display
  • From: Stefan Santesson
• Re: Gen-ART LC review of draft-ietf-mpls-lsp-ping-enhanced-dsmap-09
  • From: Noel Chiappa
• RE: Gen-ART LC review of draft-ietf-mpls-lsp-ping-enhanced-dsmap-09
  • From: Roni Even
• RE: Gen-ART LC review of draft-ietf-mpls-lsp-ping-enhanced-dsmap-09
  • From: Adrian Farrel
• Re: Gen-ART LC review of draft-ietf-mpls-lsp-ping-enhanced-dsmap-09
  • From: Doug Barton
• Re: The XML page cannot be displayed
  • From: Simon Perreault
• RE: Gen-ART LC review of draft-ietf-mpls-lsp-ping-enhanced-dsmap-09
  • From: Adrian Farrel
• Re: The XML page cannot be displayed
  • From: Julian Reschke
• Re: The XML page cannot be displayed
  • From: t.petch
• Gen-ART LC review of draft-ietf-mpls-lsp-ping-enhanced-dsmap-09
  • From: Roni Even
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Hector Santos
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: SM
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: John Levine
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Dave CROCKER
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: ned+ietf
• Re: Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
  • From: Yaron Sheffer
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: John R. Levine
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Barry Leiba
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: John R. Levine
• Re: Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Barry Leiba
• Re: The XML page cannot be displayed
  • From: Doug Barton
• Re: The XML page cannot be displayed
  • From: t.petch
• Re: The XML page cannot be displayed
  • From: Marc Manthey
• Re: The XML page cannot be displayed
  • From: Simon Perreault
• Re: The XML page cannot be displayed
  • From: Julian Reschke
• The XML page cannot be displayed
  • From: t.petch
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• tsv-dir review of draft-ietf-pwe3-fat-pw-06
  • From: Rolf Winter
• Re: Last Call: <draft-ietf-dhc-dhcpv6-relay-supplied-options-06.txt> (Relay-Supplied DHCP Options) to Proposed Standard
  • From: Mykyta Yevstifeyev
• Re: [v6ops] Review of draft-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Mark Andrews
• MLM Section 3.3 - Extra Line Acknowledgment
  • From: Hector Santos
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Hector Santos
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Hector Santos
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Joe Touch
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: sthaug
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Cameron Byrne
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Tony Finch
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Scott Schmit
• Fwd: Draft Secretariat SOW for Community Comment: Deadline 20 May
  • From: Bob Hinden
• Re: [v6ops] Review of draft-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Tony Finch
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Fred Baker
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Dave CROCKER
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: SM
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Dave CROCKER
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Joel Jaeggli
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Joe Abley
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Dave CROCKER
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Joe Abley
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Dave CROCKER
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Joe Abley
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Joel Jaeggli
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Dave CROCKER
• Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Joel Jaeggli
• RE: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Murray S. Kucherawy
• RE: [ietf-dkim] MLM and C14N
  • From: Murray S. Kucherawy
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: J.D. Falk
• Re: [ietf-dkim] MLM and C14N
  • From: Hector Santos
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Jaap Akkerhuis
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: John R. Levine
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Barry Leiba
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: John R. Levine
• RE: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Murray S. Kucherawy
• RE: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Murray S. Kucherawy
• Re: [ietf-dkim] Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: SM
• RE: Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Murray S. Kucherawy
• RE: Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Murray S. Kucherawy
• Re: Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: Alessandro Vesely
• Re: Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: SM
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Re: Last Call: <draft-ietf-dkim-mailinglists-10.txt> (DKIM And Mailing Lists) to BCP
  • From: John Levine
• Re: How to pay $47 for a copy of RFC 793
  • From: Julian Reschke
• Re: How to pay $47 for a copy of RFC 793
  • From: Steve Crocker
• Re: How to pay $47 for a copy of RFC 793
  • From: Bob Hinden
• Re: How to pay $47 for a copy of RFC 793
  • From: Florian Weimer
• Re: How to pay $47 for a copy of RFC 793
  • From: John C Klensin
• Quebec City IETF Codesprint
  • From: IETF Chair
• Re: How to pay $47 for a copy of RFC 793
  • From: Bob Hinden
• Re: How to pay $47 for a copy of RFC 793
  • From: Joe Touch
• Re: How to pay $47 for a copy of RFC 793
  • From: Joe Touch
• Re: How to pay $47 for a copy of RFC 793
  • From: Steven Bellovin
• Re: How to pay $47 for a copy of RFC 793
  • From: John C Klensin
• Re: How to pay $47 for a copy of RFC 793
  • From: SM
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: Joe Touch
• Re: How to pay $47 for a copy of RFC 793
  • From: Joe Touch
• Re: TSVDIR review of draft-ietf-v6ops-v6-aaaa-whitelisting-implications
  • From: Joe Touch
• Re: How to pay $47 for a copy of RFC 793
  • From: Steven Bellovin
• Re: How to pay $47 for a copy of RFC 793
  • From: Florian Weimer
• Gen-ART LC Review of draft-ietf-vrrp-unified-mib-09
  • From: Ben Campbell
• Gen-ART LC Review of draft-ietf-vrrp-unified-mib-09
  • From: Ben Campbell
• Re: Second Last Call: rfc5953 (Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)) to Draft Standard
  • From: Sean Turner
• Re: Second Last Call: rfc5953 (Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)) to Draft Standard
  • From: Wes Hardaker
• RE: How to pay $47 for a copy of RFC 793
  • From: John R. Levine
• Re: How to pay $47 for a copy of RFC 793
  • From: Stephane Bortzmeyer
• RE: How to pay $47 for a copy of RFC 793
  • From: Yaakov Stein
• RE: How to pay $47 for a copy of RFC 793
  • From: Yaakov Stein
• RE: How to pay $47 for a copy of RFC 793
  • From: Yoav Nir
• Re: Second Last Call: rfc5953 (Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)) to Draft Standard
  • From: SM
• Re: How to pay $47 for a copy of RFC 793
  • From: Masataka Ohta
• Re: How to pay $47 for a copy of RFC 793
  • From: John Levine
• Re: How to pay $47 for a copy of RFC 793
  • From: Masataka Ohta
• Re: How to pay $47 for a copy of RFC 793
  • From: Eric Burger
• Re: How to pay $47 for a copy of RFC 793
  • From: Masataka Ohta
• Re: Google Scholar, was How to pay $47 for a copy of RFC 793
  • From: Harald Alvestrand
• Re: How to pay $47 for a copy of RFC 793
  • From: Eric Burger
• Re: Google Scholar, was How to pay $47 for a copy of RFC 793
  • From: John C Klensin
• Re: Google Scholar, was How to pay $47 for a copy of RFC 793
  • From: Harald Alvestrand
• Re: How to pay $47 for a copy of RFC 793
  • From: Thomas Dreibholz
• Re: capturing the intended standards level, Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: SM
• Re: Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
  • From: SM
• Re: Google Scholar, was How to pay $47 for a copy of RFC 793
  • From: Klaas Wierenga
• Re: Google Scholar, was How to pay $47 for a copy of RFC 793
  • From: Paul Hoffman
• Re: Google Scholar, was How to pay $47 for a copy of RFC 793
  • From: Harald Alvestrand
• Re: Google Scholar, was How to pay $47 for a copy of RFC 793
  • From: John Levine
• Re: How to pay $47 for a copy of RFC 793
  • From: Harald Alvestrand
• Re: How to pay $47 for a copy of RFC 793
  • From: J.D. Falk
• Re: How to pay $47 for a copy of RFC 793
  • From: John C Klensin
• Re: How to pay $47 for a copy of RFC 793
  • From: John Levine
• RE: How to pay $47 for a copy of RFC 793
  • From: John C Klensin
• Re: How to pay $47 for a copy of RFC 793
  • From: John C Klensin
• Re: How to pay $47 for a copy of RFC 793
  • From: Julian Reschke
• capturing the intended standards level, Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Julian Reschke
• Re: How to pay $47 for a copy of RFC 793
  • From: Pekka Savola
• RE: How to pay $47 for a copy of RFC 793
  • From: Ross Callon
• Re: How to pay $47 for a copy of RFC 793
  • From: John C Klensin
• Re: How to pay $47 for a copy of RFC 793
  • From: Dave Crocker
• Re: How to pay $47 for a copy of RFC 793
  • From: Steve Crocker
• Re: How to pay $47 for a copy of RFC 793
  • From: John Levine
• IETF-80 Technical Plenary minutes (was: For Monday's technical plenary - Review of draft-tschofenig-post-standardization-00)
  • From: =JeffH
• Re: How to pay $47 for a copy of RFC 793
  • From: Doug Barton
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: SM
• Re: How to pay $47 for a copy of RFC 793
  • From: Marshall Eubanks
• Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
  • From: Dave CROCKER
• Re: How to pay $47 for a copy of RFC 793
  • From: Bob Braden
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Julian Reschke
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Alexey Melnikov
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Julian Reschke
• [no subject]
  • From: myl@nd
• RE: How to pay $47 for a copy of RFC 793
  • From: Worley, Dale R (Dale)
• Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
  • From: Russ Housley
• Re: How to pay $47 for a copy of RFC 793
  • From: Eric Burger
• Re: How to pay $47 for a copy of RFC 793
  • From: Stefan Winter
• RE: How to pay $47 for a copy of RFC 793
  • From: Michel Py
• Re: How to pay $47 for a copy of RFC 793
  • From: Ole Jacobsen
• Re: How to pay $47 for a copy of RFC 793
  • From: Mark Nottingham
• Re: How to pay $47 for a copy of RFC 793
  • From: John C Klensin
• Re: How to pay $47 for a copy of RFC 793
  • From: Steven Bellovin
• Re: How to pay $47 for a copy of RFC 793
  • From: John R. Levine