IETF Discussion Archive - Thread Index

• Re: Clarification for Copyright to referred material in IETF draft, (continued)
  • Re: Clarification for Copyright to referred material in IETF draft, Noel Chiappa
    • Re: Clarification for Copyright to referred material in IETF draft, George Willingmyre
    • Re: Clarification for Copyright to referred material in IETF draft, Marshall Eubanks
      • Re: Clarification for Copyright to referred material in IETF draft, Eric Burger
• Re: Second Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)) to BCP, SM
• Re: Last Call: <draft-arkko-ipv6-transition-guidelines-08.txt> (Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment) to Informational RFC, Jari Arkko
• Re: I-D Action:draft-yevstifeyev-abnf-separated-lists-01.txt, Bill McQuillan
  • RE: I-D Action:draft-yevstifeyev-abnf-separated-lists-01.txt, Thomson, Martin
  • RE: I-D Action:draft-yevstifeyev-abnf-separated-lists-01.txt, Thomson, Martin
  • <Possible follow-ups>
  • RE: I-D Action:draft-yevstifeyev-abnf-separated-lists-01.txt, Mykyta Yevstifeyev
• Re: [http-state] Last Call: <draft-ietf-httpstate-cookie-18.txt> (HTTP State Management Mechanism) to Proposed Standard, Mark Nottingham
  • Re: [http-state] Last Call: <draft-ietf-httpstate-cookie-18.txt> (HTTP State Management Mechanism) to Proposed Standard, Adam Barth
• Gen-ART IETF LC review of draft-ietf-ecrit-lost-servicelistboundary, Roni Even
  • AW: Gen-ART IETF LC review of draft-ietf-ecrit-lost-servicelistboundary, Karl Heinz Wolf
    • RE: Gen-ART IETF LC review of draft-ietf-ecrit-lost-servicelistboundary, Roni Even
      • AW: Gen-ART IETF LC review of draft-ietf-ecrit-lost-servicelistboundary, Karl Heinz Wolf
• Gen-ART LC Review of draft-saintandre-tls-server-id-check-11, Ben Campbell
• Re: [http-state] Gen-ART LC review of draft-ietf-httpstate-cookie-18, =JeffH
• Re: Last Call: <draft-kucherawy-authres-vbr-01.txt> (Authentication-Results Registration For Vouch By Reference Results) to Proposed Standard, Jay Gopalakrishnan
  • <Possible follow-ups>
  • Re: Last Call: <draft-kucherawy-authres-vbr-01.txt> (Authentication-Results Registration For Vouch By Reference Results) to Proposed Standard, Jay Gopalakrishnan
• RE: Last Call: <draft-ietf-tls-ssl2-must-not-03.txt> (Prohibiting SSL Version 2.0) to Proposed Standard, Glen Zorn
  • Re: [TLS] Last Call: <draft-ietf-tls-ssl2-must-not-03.txt> (Prohibiting SSL Version 2.0) to Proposed Standard, Michael D'Errico
    • RE: [TLS] Last Call: <draft-ietf-tls-ssl2-must-not-03.txt> (Prohibiting SSL Version 2.0) to Proposed Standard, Glen Zorn
      • Re: [TLS] Last Call: <draft-ietf-tls-ssl2-must-not-03.txt> (Prohibiting SSL Version 2.0) to Proposed Standard, Marsh Ray
      • Re: [TLS] Last Call: <draft-ietf-tls-ssl2-must-not-03.txt>, Martin Rex
      • RE: [TLS] Last Call: <draft-ietf-tls-ssl2-must-not-03.txt>, Glen Zorn
      • Re: [TLS] Last Call: <draft-ietf-tls-ssl2-must-not-03.txt>, Martin Rex
      • Re: [TLS] Last Call: <draft-ietf-tls-ssl2-must-not-03.txt>, Sean Turner
      • Re: [TLS] Last Call: <draft-ietf-tls-ssl2-must-not-03.txt>, Sean Turner
      • Re: [TLS] Last Call: <draft-ietf-tls-ssl2-must-not-03.txt>, Marsh Ray
      • Re: [TLS] Last Call: <draft-ietf-tls-ssl2-must-not-03.txt>, Sean Turner
      • RE: [TLS] Last Call: <draft-ietf-tls-ssl2-must-not-03.txt>, Glen Zorn
  • Re: Last Call: <draft-ietf-tls-ssl2-must-not-03.txt> (Prohibiting SSL Version 2.0) to Proposed Standard, Joe Salowey
    • RE: Last Call: <draft-ietf-tls-ssl2-must-not-03.txt> (Prohibiting SSL Version 2.0) to Proposed Standard, Glen Zorn
• Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, L.Wood
  • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Sean Turner
    • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, L.Wood
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Sam Hartman
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated, Martin Rex
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated, L.Wood
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated, Martin Rex
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated, L.Wood
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Francis Dupont
      • RE: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
      • RE: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Christian Huitema
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Francis Dupont
      • RE: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Francis Dupont
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Francis Dupont
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Sean Turner
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Sam Hartman
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Francis Dupont
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Sam Hartman
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated, Martin Rex
      • Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated, Sam Hartman
      • RE: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
• Re: Last Call: <draft-kucherawy-authres-vbr-01.txt> (Authentication-Results Registration For Vouch By Reference Results) to Proposed Standard, Dave CROCKER
  • Re: Last Call: <draft-kucherawy-authres-vbr-01.txt> (Authentication-Results Registration For Vouch By Reference Results) to Proposed Standard, John Levine
    • Re: Last Call: <draft-kucherawy-authres-vbr-01.txt> (Authentication-Results Registration For Vouch By Reference Results) to Proposed Standard, Alessandro Vesely
  • Re: Last Call: <draft-kucherawy-authres-vbr-01.txt> (Authentication-Results Registration For Vouch By Reference Results) to Proposed Standard, J.D. Falk
• secdir review of draft-stone-mgcp-vbd-08.txt, Carl Wallace
• draft-cheshire-dnsext-multicastdns-12.txt, Donald Eastlake
  • Re: draft-cheshire-dnsext-multicastdns-12.txt, Stuart Cheshire
• Gen-ART LC review of draft-ietf-httpstate-cookie-18, Richard L. Barnes
  • Re: Gen-ART LC review of draft-ietf-httpstate-cookie-18, Adam Barth
    • Re: Gen-ART LC review of draft-ietf-httpstate-cookie-18, Richard L. Barnes
      • Re: Gen-ART LC review of draft-ietf-httpstate-cookie-18, Adam Barth
      • Re: Gen-ART LC review of draft-ietf-httpstate-cookie-18, Richard L. Barnes
• Gen-ART LC review of draft-ietf-opsec-protect-control-plane-04, Roni Even
  • Re: Gen-ART LC review of draft-ietf-opsec-protect-control-plane-04, Joel Jaeggli
    • Re: Gen-ART LC review of draft-ietf-opsec-protect-control-plane-04, Rodney Dunn
      • RE: Gen-ART LC review of draft-ietf-opsec-protect-control-plane-04, Roni Even
      • Re: Gen-ART LC review of draft-ietf-opsec-protect-control-plane-04, Rodney Dunn
• Re: Call for Comments: "Design Considerations for Protocol Extensions", Adam Roach
  • Re: Call for Comments: "Design Considerations for Protocol Extensions", Fred Baker
    • Re: Call for Comments: "Design Considerations for Protocol Extensions", Adam Roach
• secdir review of draft-ietf-dime-rfc3588bis-25, Carl Wallace
• Gen-ART LC Review of draft-cheshire-dnsext-multicastdns-12, Ben Campbell
  • Re: Gen-ART LC Review of draft-cheshire-dnsext-multicastdns-12, Ben Campbell
  • Re: Gen-ART LC Review of draft-cheshire-dnsext-multicastdns-12, Stuart Cheshire
    • Re: Gen-ART LC Review of draft-cheshire-dnsext-multicastdns-12, Ben Campbell
      • Re: Gen-ART LC Review of draft-cheshire-dnsext-multicastdns-12, Douglas Otis
      • Re: Gen-ART LC Review of draft-cheshire-dnsext-multicastdns-12, Stuart Cheshire
• AP article: US Embassy: Beijing Air Quality Is 'Crazy Bad', Dave CROCKER
• Feedback on Day Passes, Bob Hinden
  • Re: Feedback on Day Passes, James M. Polk
    • Re: Feedback on Day Passes, Tobias Gondrom
      • Re: Feedback on Day Passes, James M. Polk
      • Re: Feedback on Day Passes, Bob Hinden
      • Re: Feedback on Day Passes, James M. Polk
      • Re: Feedback on Day Passes, Cullen Jennings
  • <Possible follow-ups>
  • Re: Feedback on Day Passes, SM
• secdir review of draft-melnikov-mailserver-uri-to-historic-00, Richard L. Barnes
• Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, RJ Atkinson
  • Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Douglas Otis
  • Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Michael StJohns
    • Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, ned+ietf
  • Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Doug Barton
    • Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Tony Finch
      • Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Doug Barton
      • Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Paul Hoffman
      • Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Doug Barton
      • Stop the process trolls ! Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Phillip Hallam-Baker
      • Re: Stop the process trolls ! Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Keith Moore
      • Re: Stop the process trolls ! Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Phillip Hallam-Baker
      • Re: Stop the process trolls ! Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Keith Moore
      • Re: Stop the process trolls ! Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Andrew Sullivan
      • On DNS Expert failure (was: Stop the process trolls !), Andrew Sullivan
      • Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Stuart Cheshire
    • Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt, Stuart Cheshire
• Re: Last Call: <draft-cheshire-dnsext-dns-sd-07.txt> (DNS-Based Service Discovery) to Proposed Standard, Pekka Savola
  • Re: Last Call: <draft-cheshire-dnsext-dns-sd-07.txt> (DNS-Based Service Discovery) to Proposed Standard, Stuart Cheshire
    • Re: Last Call: <draft-cheshire-dnsext-dns-sd-07.txt> (DNS-Based Service Discovery) to Proposed Standard, Pekka Savola
      • Re: Last Call: <draft-cheshire-dnsext-dns-sd-07.txt> (DNS-Based Service Discovery) to Proposed Standard, Stuart Cheshire
      • Re: Last Call: <draft-cheshire-dnsext-dns-sd-07.txt> (DNS-Based Service Discovery) to Proposed Standard, Pekka Savola
      • Re: Last Call: <draft-cheshire-dnsext-dns-sd-07.txt> (DNS-Based Service Discovery) to Proposed Standard, Stuart Cheshire
• ISOC Board of Trustees Meeting Output, Russ Housley
  • Re: ISOC Board of Trustees Meeting Output, jean-michel bernier de portzamparc
    • Re: ISOC Board of Trustees Meeting Output, Hannes Tschofenig
    • Re: ISOC Board of Trustees Meeting Output, Marshall Eubanks
• Re: Last Call: <draft-salowey-secsh-uri-00.txt> (Uniform Resource Identifier (URI) Scheme for Secure Shell (SSH)) to Proposed Standard, Cullen Jennings
  • Re: Last Call: <draft-salowey-secsh-uri-00.txt> (Uniform Resource Identifier (URI) Scheme for Secure Shell (SSH)) to Proposed Standard, Joe Salowey
  • Re: Last Call: <draft-salowey-secsh-uri-00.txt> (Uniform ResourceIdentifier (URI) Scheme for Secure Shell (SSH)) to Proposed Standard, t.petch
    • Re: Last Call: <draft-salowey-secsh-uri-00.txt> (Uniform ResourceIdentifier (URI) Scheme for Secure Shell (SSH)) to Proposed Standard, Chris Lonvick
• IETF Fellowship Applications, Steve Conte
• DNSSEC & legal effect, Josh Howlett
  • Re: DNSSEC & legal effect, Stephen Farrell
• Problem with draft-sheffer-emu-eap-eke, Bernard Aboba
  • <Possible follow-ups>
  • Re: Problem with draft-sheffer-emu-eap-eke, Yaron Sheffer
    • Re: Problem with draft-sheffer-emu-eap-eke, Yaron Sheffer
      • RE: Problem with draft-sheffer-emu-eap-eke, Glen Zorn
• Re: Last Call: <draft-igoe-secsh-x509v3-06.txt> (X.509v3 Certificates for Secure Shell Authentication) to Proposed Standard, Rene Struik
  • Re: Last Call: <draft-igoe-secsh-x509v3-06.txt> (X.509v3 Certificates for Secure Shell Authentication) to Proposed Standard, Paul Hoffman
    • Re: Last Call: <draft-igoe-secsh-x509v3-06.txt> (X.509v3 Certificates for Secure Shell Authentication) to Proposed Standard, Rene Struik
  • <Possible follow-ups>
  • Re: Last Call: <draft-igoe-secsh-x509v3-06.txt> (X.509v3 Certificates for Secure Shell Authentication) to Proposed Standard, RJ Atkinson
• RE: [mpls-tp] about open discussion about MIP MEP in MPLS-TP networks, Alexander Vainshtein
  • R: [mpls-tp] about open discussion about MIP MEP in MPLS-TP networks, BUSI, ITALO (ITALO)
• IESG position on NAT traversal and IPv4/IPv6, Hadriel Kaplan
  • Re: IESG position on NAT traversal and IPv4/IPv6, Phillip Hallam-Baker
    • Re: IESG position on NAT traversal and IPv4/IPv6, Masataka Ohta
    • RE: IESG position on NAT traversal and IPv4/IPv6, David Harrington
      • Re: IESG position on NAT traversal and IPv4/IPv6, Hadriel Kaplan
      • Re: IESG position on NAT traversal and IPv4/IPv6, Phillip Hallam-Baker
      • RE: IESG position on NAT traversal and IPv4/IPv6, Worley, Dale R (Dale)
  • Re: IESG position on NAT traversal and IPv4/IPv6, Gonzalo Camarillo
    • Re: IESG position on NAT traversal and IPv4/IPv6, Jari Arkko
      • Re: IESG position on NAT traversal and IPv4/IPv6, Masataka Ohta
      • Re: IESG position on NAT traversal and IPv4/IPv6, Phillip Hallam-Baker
      • Re: IESG position on NAT traversal and IPv4/IPv6, Masataka Ohta
      • Re: IESG position on NAT traversal and IPv4/IPv6, Yoav Nir
      • Re: IESG position on NAT traversal and IPv4/IPv6, Masataka Ohta
      • Re: IESG position on NAT traversal and IPv4/IPv6, Martin Rex
      • Re: IESG position on NAT traversal and IPv4/IPv6, Masataka Ohta
      • Re: IESG position on NAT traversal and IPv4/IPv6, Tadayuki HATTORI
      • Re: IESG position on NAT traversal and IPv4/IPv6, Martin Rex
      • Re: IESG position on NAT traversal and IPv4/IPv6, Masataka Ohta
      • Re: IESG position on NAT traversal and IPv4/IPv6, Tadayuki HATTORI
      • Re: IESG position on NAT traversal and IPv4/IPv6, Martin Rex
      • Re: IESG position on NAT traversal and IPv4/IPv6, Masataka Ohta
  • Re: IESG position on NAT traversal and IPv4/IPv6, Brian E Carpenter
  • <Possible follow-ups>
  • Re: IESG position on NAT traversal and IPv4/IPv6, Noel Chiappa
  • RE: IESG position on NAT traversal and IPv4/IPv6, Noel Chiappa
• Thoughts on IANA registries, Julian Reschke
• Two step, three step, one step, and alternatives, John C Klensin
  • Re: Two step, three step, one step, and alternatives, Dave CROCKER
    • Re: Two step, three step, one step, and alternatives, John C Klensin
      • Re: Two step, three step, one step, and alternatives, Dave CROCKER
  • Re: Two step, three step, one step, and alternatives, Eric Burger
  • Re: Two step, three step, one step, and alternatives, Eliot Lear
    • Re: Two step, three step, one step, and alternatives, John C Klensin
      • Re: Two step, three step, one step, and alternatives, Spencer Dawkins
• Re: [IAOC] Badges and blue sheets, JORDI PALET MARTINEZ
  • Re: [IAOC] Badges and blue sheets, Yoav Nir
    • Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, Shane Kerr
      • Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, Phillip Hallam-Baker
      • Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, SM
      • Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, Yoav Nir
      • Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, Marshall Eubanks
      • Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, John C Klensin
      • RE: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, Worley, Dale R (Dale)
      • Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, SM
      • Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, Yoav Nir
      • Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, Ole Jacobsen
      • Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, Bert
      • Re: Publishing list of non-paying IETF attendees, was Re: [IAOC] Badges and blue sheets, bill manning
    • Re: [IAOC] Badges and blue sheets, JORDI PALET MARTINEZ
      • Re: [IAOC] Badges and blue sheets, Phillip Hallam-Baker
      • Re: [IAOC] Badges and blue sheets, Brian E Carpenter
      • Re: [IAOC] Badges and blue sheets, James M. Polk
    • Re: [IAOC] Badges and blue sheets, Marshall Eubanks
      • Re: [IAOC] Badges and blue sheets, JORDI PALET MARTINEZ
      • Re: [IAOC] Badges and blue sheets, JORDI PALET MARTINEZ
      • Re: [IAOC] Badges and blue sheets, Lucy Lynch
      • Re: [IAOC] Badges and blue sheets, JORDI PALET MARTINEZ
      • Re: [IAOC] Badges and blue sheets, Andrew Sullivan
      • Re: [IAOC] Badges and blue sheets, Ole Jacobsen
      • Re: [IAOC] Badges and blue sheets, Richard L. Barnes
      • Re: [IAOC] Badges and blue sheets, Scott Brim
      • RE: [IAOC] Badges and blue sheets, Yoav Nir
      • Re: [IAOC] Badges and blue sheets, Bob Hinden
      • Re: [IAOC] Badges and blue sheets, JORDI PALET MARTINEZ
      • Re: [IAOC] Badges and blue sheets, Ole Jacobsen
      • Re: [IAOC] Badges and blue sheets, bill manning
• Everybody wants it but nobody does it...., Marc Manthey
  • Re: [vmeet] Everybody wants it but nobody does it...., Marshall Eubanks
• Re: [79all] IETF Badge, Samuel Weiler
  • Re: [79all] IETF Badge, Ole Jacobsen
    • Re: [79all] IETF Badge, Peter Saint-Andre
      • Re: [79all] IETF Badge, Ole Jacobsen
      • Re: [79all] IETF Badge, Peter Saint-Andre
      • RE: [79all] IETF Badge, Worley, Dale R (Dale)
      • Re: [79all] IETF Badge, Eliot Lear
      • Re: [79all] IETF Badge, Peter Saint-Andre
      • Re: [79all] IETF Badge, Andrew Allen
      • Re: [79all] IETF Badge, Marshall Eubanks
      • Re: [IAOC] [79all] IETF Badge, Eric Burger
      • Re: [IAOC] [79all] IETF Badge, Eliot Lear
      • Re: [79all] IETF Badge, Dave CROCKER
    • Re: [79all] IETF Badge, Samuel Weiler
      • Re: [79all] IETF Badge, Henk Uijterwaal
      • Re: [79all] IETF Badge, Jaap Akkerhuis
      • Re: [79all] IETF Badge, Bjoern A. Zeeb
      • Re: [79all] IETF Badge, Ole Jacobsen
      • Re: [79all] IETF Badge, Lawrence Conroy
      • Badges and blue sheets, Brian E Carpenter
      • Re: Badges and blue sheets, JORDI PALET MARTINEZ
      • Re: [IAOC] Badges and blue sheets, Marshall Eubanks
      • Re: [IAOC] Badges and blue sheets, JORDI PALET MARTINEZ
      • Re: Badges and blue sheets, Tobias Gondrom
      • Re: [79all] IETF Badge, Hadriel Kaplan
      • Re: [79all] IETF Badge, Gonzalo Camarillo
  • RE: [79all] IETF Badge, Worley, Dale R (Dale)
    • Re: [79all] IETF Badge, Dave CROCKER
      • Re: [79all] IETF Badge, Joel Jaeggli
      • Re: [79all] IETF Badge, Henk Uijterwaal
      • Re: [79all] IETF Badge, Dave CROCKER
      • Re: [79all] IETF Badge, Peter Saint-Andre
      • Re: [79all] IETF Badge, Hadriel Kaplan
      • Re: [79all] IETF Badge, Andrew Allen
      • Re: [79all] IETF Badge, Doug Ewell
      • Re: [79all] IETF Badge, Martin Rex
      • Re: [79all] IETF Badge, Scott Brim
      • Re: [79all] IETF Badge, Dave CROCKER
      • Re: [79all] IETF Badge, Phillip Hallam-Baker
      • Re: [79all] IETF Badge, Stephane Bortzmeyer
      • Re: [79all] IETF Badge, Ray Pelletier
      • Re: [79all] IETF Badge, mstjohns
      • Re: [79all] IETF Badge, Scott Brim
      • Re: [79all] IETF Badge, Ole Jacobsen
      • Re: [79all] IETF Badge, Michael StJohns
      • Re: [79all] IETF Badge, Ole Jacobsen
      • Message not available
      • Re: [79all] IETF Badge, Ole Jacobsen
      • Re: [79all] IETF Badge, Xiangsong Cui
      • Re: [79all] IETF Badge, Lou Berger
      • Re: [79all] IETF Badge, Stephen Farrell
      • RE: [79all] IETF Badge, Xiangsong Cui
      • Re: [79all] IETF Badge, Lou Berger
      • Re: [79all] IETF Badge, Ole Jacobsen
      • Re: [79all] IETF Badge, Lou Berger
      • Re: [79all] IETF Badge, Ole Jacobsen
      • Re: [79all] IETF Badge, Lou Berger
      • Re: [79all] IETF Badge, Andrew Sullivan
      • Re: [79all] IETF Badge, Bob Hinden
      • Re: [79all] IETF Badge, Patrik Faltstrom (pfaltstr)
      • Re: [79all] IETF Badge, Lawrence Conroy
      • Re: [79all] IETF Badge, Ole Jacobsen
      • Re: [79all] IETF Badge, Peter Saint-Andre
      • Re: [79all] IETF Badge, Phillip Hallam-Baker
  • Re: [79all] IETF Badge, SM
  • <Possible follow-ups>
  • [79all] IETF Badge, Scott O. Bradner
    • Re: [79all] IETF Badge, James M. Polk
  • Re: [79all] IETF Badge, Scott O. Bradner
    • Re: [79all] IETF Badge, Randall Gellens
• text versions of ID and RFCs, Yaakov Stein
  • Re: text versions of ID and RFCs, Tony Hansen
    • RE: text versions of ID and RFCs, Yaakov Stein
      • Re: text versions of ID and RFCs, Ben Niven-Jenkins
• ISOC's Internet ON - San Francisco California, December 8-9, 2010, IPv16.com
• BOF scheduling, Yaakov Stein
• Move of ALTO and DECADE to Transport Area, The IESG
  • [www.ietf.org/rt #32645] Move of ALTO and DECADE to Transport Area, Cindy Morgan via RT
  • <Possible follow-ups>
  • Re: Move of ALTO and DECADE to Transport Area, The IESG
• Alternative Proposal for Two-Stage IETF Standardization, Dave CROCKER
  • Re: Alternative Proposal for Two-Stage IETF Standardization, Mark Andrews
    • Re: Alternative Proposal for Two-Stage IETF Standardization, Dave CROCKER
  • Re: Alternative Proposal for Two-Stage IETF Standardization, Brian E Carpenter
  • Re: Alternative Proposal for Two-Stage IETF Standardization, Russ Housley
    • Re: Alternative Proposal for Two-Stage IETF Standardization, Dave CROCKER
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Dave CROCKER
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Russ Housley
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Spencer Dawkins
      • Re: Alternative Proposal for Two-Stage IETF Standardization, ned+ietf
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Spencer Dawkins
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Dave CROCKER
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Russ Housley
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Dave CROCKER
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Spencer Dawkins
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Eric Burger
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Peter Saint-Andre
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Martin Rex
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Dave CROCKER
      • Re: Alternative Proposal for Two-Stage IETF Standardization, Martin Rex
• Updated - Audio Streaming Info - IETF 79 Beijing, November 7-12, 2010, Joel Jaeggli
• Requested follow-up from last night's plenary, Ted Hardie
• Transcript during the Technical Plenary, IAB Chair
• FW: NomCom 2010-2011: Announcing Beijing Office Hours for IETF-79, Thomas Walsh
• Beijing TSV area "office hours", Lars Eggert
  • CORRECTION: Beijing TSV area "office hours", Lars Eggert
    • Re: CORRECTION: Beijing TSV area "office hours", Scott Brim
• Proposed WG and BOF Scheduling Experiment, The IESG
  • Re: Proposed WG and BOF Scheduling Experiment, Richard L. Barnes
    • RE: Proposed WG and BOF Scheduling Experiment, David Harrington
      • Re: Proposed WG and BOF Scheduling Experiment, Andrew G. Malis
      • Re: Proposed WG and BOF Scheduling Experiment, Henk Uijterwaal
      • RE: Proposed WG and BOF Scheduling Experiment, gregory.cauchie
      • Re: Proposed WG and BOF Scheduling Experiment, Michael Richardson
      • Re: Proposed WG and BOF Scheduling Experiment, Spencer Dawkins
      • Re: Proposed WG and BOF Scheduling Experiment, Scott Brim
  • Re: Proposed WG and BOF Scheduling Experiment, Dave CROCKER
    • Re: Proposed WG and BOF Scheduling Experiment, Geoff Mulligan
    • Re: Proposed WG and BOF Scheduling Experiment, Geoff Mulligan
    • RE: BOF Attendance Minimization, Bernard Aboba
      • Re: BOF Attendance Minimization, Dave CROCKER
  • Re: Proposed WG and BOF Scheduling Experiment, Scott Brim
    • Re: Proposed WG and BOF Scheduling Experiment, Phillip Hallam-Baker
  • Re: Proposed WG and BOF Scheduling Experiment, Brian E Carpenter
    • Re: Proposed WG and BOF Scheduling Experiment, Aaron Falk
      • Re: Proposed WG and BOF Scheduling Experiment, Barry Leiba
    • Re: Proposed WG and BOF Scheduling Experiment, Russ Housley
      • RE: Proposed WG and BOF Scheduling Experiment, Worley, Dale R (Dale)
      • RE: Proposed WG and BOF Scheduling Experiment, Ross Callon
      • RE: Proposed WG and BOF Scheduling Experiment, Worley, Dale R (Dale)
  • Re: Proposed WG and BOF Scheduling Experiment, Pete Resnick
  • Re: Proposed WG and BOF Scheduling Experiment, Andrew Sullivan
  • Re: Proposed WG and BOF Scheduling Experiment, Kurt Zeilenga
    • Provider-Aggregated vs Provider-Independent IPv6 addressing, Templin, Fred L
      • Re: Provider-Aggregated vs Provider-Independent IPv6 addressing, Brian E Carpenter
  • Re: Proposed WG and BOF Scheduling Experiment, Eric Burger
• Tonight's Plenary: RFCs Will No Longer Be Published, Dave CROCKER
  • Re: Tonight's Plenary: RFCs Will No Longer Be Published, Olaf Kolkman
• irtf-discuss list, Aaron Falk
• ** OAuth Tutorial & OAuth Security Session **, Hannes Tschofenig
  • Re: [OAUTH-WG] ** OAuth Tutorial & OAuth Security Session **, Torsten Lodderstedt
    • RE: [OAUTH-WG] ** OAuth Tutorial & OAuth Security Session **, Anthony Nadalin
      • AW: RE: [OAUTH-WG] ** OAuth Tutorial & OAuth Security Session **, torsten
      • Re: [secdir] [OAUTH-WG] ** OAuth Tutorial & OAuth Security Session **, Richard L. Barnes
      • Re: [OAUTH-WG] [secdir] ** OAuth Tutorial & OAuth Security Session **, Mark Mcgloin
      • RE: [secdir] [OAUTH-WG] ** OAuth Tutorial & OAuth Security Session **, Anthony Nadalin
      • Re: [secdir] [OAUTH-WG] ** OAuth Tutorial & OAuth Security Session **, Richard L. Barnes
      • Re: [OAUTH-WG] [secdir] ** OAuth Tutorial & OAuth Security Session **, Igor Faynberg
      • Re: [kitten] [OAUTH-WG] ** OAuth Tutorial & OAuth Security Session **, Nicolas Williams
• FW: Nomcom 2010-2011: NomCom Voting Member Stepping Down, Thomas Walsh
• IPv6 Top Topic at U.S. FCC Technological Advisory Council Meeting, IPv16.com
• Call for IAOC Nominations and Volunteers 2010, IAB Chair
• draft-c1222-transport-over-ip-07 -- more concerns, Alfred Hönes
  • Re: draft-c1222-transport-over-ip-07 -- more concerns, Avygdor Moise
  • Re: draft-c1222-transport-over-ip-07 -- more concerns, Avygdor Moise
    • Re: draft-c1222-transport-over-ip-07 -- more concerns, Alfred Hönes
      • Re: draft-c1222-transport-over-ip-07 -- more concerns, Avygdor Moise
• Transitional RFC Series Editor recommendations Overview document to be distributed by Wednesday - background document for monday plenary, Glenn Kowack
  • <Possible follow-ups>
  • Transitional RFC Series Editor recommendations Overview document to be distributed by Wednesday - background document for Monday Plenary, Glenn Kowack
• No single problem... (was Re: what is the problem bis), Ted Hardie
  • Re: No single problem..., John Leslie
  • Re: No single problem... (was Re: what is the problem bis), Randy Presuhn
    • Re: No single problem... (was Re: what is the problem bis), Phillip Hallam-Baker
      • Re: No single problem... (was Re: what is the problem bis), Melinda Shore
      • Re: No single problem... (was Re: what is the problem bis), Phillip Hallam-Baker
      • Re: No single problem... (was Re: what is the problem bis), Hadriel Kaplan
  • Re: No single problem... (was Re: what is the problem bis), John C Klensin
    • Re: No single problem... (was Re: what is the problem bis), Ted Hardie
      • Re: No single problem... (was Re: what is the problem bis), John Leslie
      • Re: No single problem... (was Re: what is the problem bis), Bill McQuillan
    • RE: No single problem... (was Re: what is the problem bis), Ross Callon
      • RE: No single problem... (was Re: what is the problem bis), John C Klensin
      • RE: No single problem... (was Re: what is the problem bis), Ross Callon
  • Re: No single problem... (was Re: what is the problem bis), Hadriel Kaplan
    • Re: No single problem... (was Re: what is the problem bis), Ted Hardie
• mgcp conference modification, Andres Miedzowicz
• An elephant in the room (was IETF processes (was Re: draft-housley-two-maturity-levels)), Ted Hardie
  • Re: An elephant in the room (was IETF processes (was Re: draft-housley-two-maturity-levels)), Dave CROCKER
    • Re: An elephant in the room (was IETF processes (was Re: draft-housley-two-maturity-levels)), Julian Reschke
    • Re: An elephant in the room (was IETF processes (was Re: draft-housley-two-maturity-levels)), Dave CROCKER
• An archive for nerdy t-shirts, Paul Hoffman
  • Re: An archive for nerdy t-shirts, Ole Jacobsen
  • Re: An archive for nerdy t-shirts, Lucy Lynch
    • Re: An archive for nerdy t-shirts, Donald Eastlake
      • Re: An archive for nerdy t-shirts, Ole Jacobsen
• IETF processes (was Re: draft-housley-two-maturity-levels), RJ Atkinson
  • Re: IETF processes (was Re: draft-housley-two-maturity-levels), Dave CROCKER
    • Re: IETF processes (was Re: draft-housley-two-maturity-levels), Bob Braden
      • Re: IETF processes (was Re: draft-housley-two-maturity-levels), Dave CROCKER
      • Re: IETF processes (was Re: draft-housley-two-maturity-levels), Eliot Lear
    • Re: IETF processes (was Re: draft-housley-two-maturity-levels), RJ Atkinson
      • Alternate entry document model (was: Re: IETF processes (was Re: draft-housley-two-maturity-levels)), John C Klensin
      • Re: Alternate entry document model (was: Re: IETF processes (was Re: draft-housley-two-maturity-levels)), SM
      • Re: Alternate entry document model (was: Re: IETF processes (was Re: draft-housley-two-maturity-levels)), Andrew Sullivan
      • Re: Alternate entry document model (was: Re: IETF processes (was Re: draft-housley-two-maturity-levels)), Michael Richardson
      • Re: Alternate entry document model (was: Re: IETF processes (was Re: draft-housley-two-maturity-levels)), Yoav Nir
      • Re: Alternate entry document model, Joel M. Halpern
      • Re: Alternate entry document model, Dave CROCKER
      • Re: Alternate entry document model, Gonzalo Camarillo
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe: draft-housley-two-maturity-levels)), t.petch
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe:draft-housley-two-maturity-levels)), Randy Presuhn
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe:draft-housley-two-maturity-levels)), Ted Hardie
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe:, Martin Rex
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe:, Andrew Sullivan
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe:, Martin Rex
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe:, Spencer Dawkins
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe:, Yoav Nir
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe:, Martin Rex
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe:, t.petch
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe:, Yoav Nir
      • Re: Alternate entry document model (was: Re: IETF processes (wasRe:, Spencer Dawkins
      • Re: Alternate entry document model (was: Re: IETF processes (was Re: draft-housley-two-maturity-levels)), SM
      • Re: Alternate entry document model (was: Re: IETF processes, Martin Rex
      • Re: Alternate entry document model (was: Re: IETF processes (was Re: draft-housley-two-maturity-levels)), John C Klensin
      • Re: Alternate entry document model, Arnt Gulbrandsen
  • Re: IETF processes (was Re: draft-housley-two-maturity-levels), Scott Brim
• Travel Tips for leaving or entering the US., Richard Shockey
  • Re: Travel Tips for leaving or entering the US., Marshall Eubanks
• Re: Last Call: <draft-cheshire-dnsext-multicastdns-12.txt> (Multicast DNS) to Proposed Standard, Stephane Bortzmeyer
  • Re: Last Call: <draft-cheshire-dnsext-multicastdns-12.txt> (Multicast DNS) to Proposed Standard, Eliot Lear
• Gen-ART review of draft-ietf-l3vpn-mvpn-spmsi-joins-01, James M. Polk
  • Re: Gen-ART review of draft-ietf-l3vpn-mvpn-spmsi-joins-01, Eric Rosen
    • Re: Gen-ART review of draft-ietf-l3vpn-mvpn-spmsi-joins-01, James M. Polk
      • Re: Gen-ART review of draft-ietf-l3vpn-mvpn-spmsi-joins-01, Eric Rosen
      • RE: Gen-ART review of draft-ietf-l3vpn-mvpn-spmsi-joins-01, Adrian Farrel
      • RE: Gen-ART review of draft-ietf-l3vpn-mvpn-spmsi-joins-01, Mr. James W. Laferriere
      • Re: Gen-ART review of draft-ietf-l3vpn-mvpn-spmsi-joins-01, James M. Polk
      • Re: Gen-ART review of draft-ietf-l3vpn-mvpn-spmsi-joins-01, James M. Polk
• cell sim card recommendations, Dave CROCKER
  • Re: cell sim card recommendations, Hui Deng
    • Re: [79attendees] cell sim card recommendations, YAO Jiankang
• Fwd: [rfc-i] Transitional RFC Editor recommendations published in draft-kowack-rfc-editor-model-v2, Russ Housley
• Re: [keyassure] WG Review: Keys In DNS (kidns), Jeffrey A. Williams
  • Re: WG Review: Keys In DNS (kidns), Simon Josefsson
  • <Possible follow-ups>
  • Re: [keyassure] WG Review: Keys In DNS (kidns), Jeffrey A. Williams
• Transitional RFC Series Editor recommendations published, Glenn Kowack
• Re: WG Review: Keys In DNS (kidns), Ted Hardie
  • <Possible follow-ups>
  • Re: WG Review: Keys In DNS (kidns), Simon Josefsson
• RE: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Avygdor Moise
  • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Donald Eastlake
    • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Avygdor Moise
  • RE: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Michael StJohns
  • Message not available
    • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Avygdor Moise
      • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Ralph Droms
      • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Michael StJohns
      • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Michael Richardson
      • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Avygdor Moise
      • Message not available
      • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Avygdor Moise
      • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Ralph Droms
      • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Bora Akyol
      • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Michael StJohns
      • Message not available
      • Re: Document Action: 'ANSI C12.22, IEEE 1703 and MC12.22 TransportOver IP' to Informational RFC, Avygdor Moise
• what is the problem bis, Scott O. Bradner
  • Re: what is the problem bis, Marshall Eubanks
    • Re: what is the problem bis, Dave CROCKER
  • RE: what is the problem bis, Ross Callon
    • Re: what is the problem bis, Eliot Lear
      • Re: what is the problem bis, Michael Richardson
    • Re: what is the problem bis, Dave CROCKER
      • RE: what is the problem bis, Ross Callon
      • Re: what is the problem bis, Dave CROCKER
      • Re: what is the problem bis, Hadriel Kaplan
      • Re: what is the problem bis, Ofer Inbar
      • Re: what is the problem bis, Eric Burger
      • RE: what is the problem bis, John C Klensin
      • Re: what is the problem bis, Phillip Hallam-Baker
      • Re: what is the problem bis, Keith Moore
      • Re: what is the problem bis, John C Klensin
      • Re: what is the problem bis, Keith Moore
    • Re: what is the problem bis, Keith Moore
  • Re: what is the problem bis, todd glassey
  • Re: what is the problem bis, Phillip Hallam-Baker
    • Re: what is the problem bis, Randy Presuhn
    • Re: what is the problem bis, Andrew Sullivan
      • RE: what is the problem bis, Yoav Nir
      • RE: what is the problem bis, Paul Hoffman
      • RE: what is the problem bis, ned+ietf
      • Re: what is the problem bis, Keith Moore
      • Re: what is the problem bis, Yoav Nir
      • Re: what is the problem bis, Keith Moore
      • Re: what is the problem bis, t.petch
      • what is the problem ter, Keith Moore
      • RE: what is the problem ter, John E Drake
      • Re: what is the problem ter, Martin Rex
      • Re: what is the problem bis, Michael Richardson
      • Re: what is the problem bis, Keith Moore
      • Re: what is the problem bis, Hadriel Kaplan
      • Re: what is the problem bis, Richard L. Barnes
      • Re: what is the problem bis, Dave CROCKER
      • Re: what is the problem bis, Keith Moore
      • RE: what is the problem bis, Glen Zorn
      • Re: what is the problem bis, Keith Moore
      • Re: what is the problem bis, Joel Jaeggli
      • Re: what is the problem bis, Keith Moore
      • Re: what is the problem bis, Yoav Nir
      • Re: what is the problem bis, Joel Jaeggli
      • Re: what is the problem bis, Keith Moore
      • Re: what is the problem bis, Phillip Hallam-Baker