IETF Discussion Archive - Thread Index

• Re: [DRUMS], (continued)
  • Re: [DRUMS], Tony Hansen
• XMPP Robots in chatrooms, Dave Cridland
• How to get onto the IETF authenticated LAN?, Phillip Hallam-Baker
  • Re: How to get onto the IETF authenticated LAN?, Yoav Nir
  • Re: How to get onto the IETF authenticated LAN?, Dan Harkins
• Call for Volunteers: IAB Scribe, IAB Chair
• NAT64 Experiment at IETF 78, IETF Chair
• Re: [apps-discuss] Fwd: Last Call: draft-hammer-hostmeta (Web Host Metadata) to Proposed Standard, Aaron Stone
  • Re: [apps-discuss] Fwd: Last Call: draft-hammer-hostmeta (Web Host, Martin Rex
• Fwd: I-D ACTION:draft-crocker-nomcom-process-00.txt, Dave CROCKER
• WebEx for Administrative Plenary, IETF Chair
• WebEx for Technical Plenary, IETF Chair
• Re: [Isis-wg] Last Call: draft-ietf-isis-bfd-tlv (IS-IS BFD EnabledTLV) to Proposed Standard, lan7801
• tools location, Iljitsch van Beijnum
  • RE: tools location, Thomson, Martin
    • Re: tools location, Iljitsch van Beijnum
      • Re: tools location, DM Abreu
      • Re: tools location, Henrik Levkowetz
      • RE: tools location, Thomson, Martin
    • Re: tools location, Scott Brim
      • Re: tools location, Iljitsch van Beijnum
      • Re: tools location, Joel Jaeggli
  • Re: tools location, Lars Eggert
• The anonymity question, Brian E Carpenter
  • Re: The anonymity question, Fred Baker
  • Re: The anonymity question, John Levine
    • Re: The anonymity question, Fred Baker
      • Re: The anonymity question, John R. Levine
      • Re: The anonymity question, Fred Baker
      • RE: The anonymity question, Michel Py
      • Re: The anonymity question, Phillip Hallam-Baker
      • Re: The anonymity question, Joel Jaeggli
      • Re: The anonymity question, todd glassey
      • Re: The anonymity question, Martin Rex
      • Re: The anonymity question, Jorge Amodio
  • Re: The anonymity question, Bob Hinden
    • Re: The anonymity question, Joel Jaeggli
  • Re: The anonymity question, Marshall Eubanks
  • <Possible follow-ups>
  • Re: The anonymity question, Jorge Amodio
• Re: Last Call: draft-hammer-hostmeta (Web Host Metadata) to Proposed Standard, Norbert Lindenberg â
• FW: Nomcom 2010-2011: Final List of Nomcom Members, Thomas Walsh
• Gen-ART LC review of draft-baker-v6ops-greynet-04.tx, Ben Campbell
• Wallet theft in Brussels train station, Robert Moskowitz
  • Re: Wallet theft in Brussels train station, Huub van Helvoort
  • Re: Wallet theft in Brussels train station, Michael Dillon
    • Re: Wallet theft in Brussels train station, Dave CROCKER
  • RE: Wallet theft in Brussels train station, Ross Callon
• Fwd: Re: Question - Can DNSSEC be operated in a manner which meets Khaledmandates?, todd glassey
  • Re: Fwd: Re: Question - Can DNSSEC be operated in a manner which meets, Martin Rex
    • Re: Fwd: Re: Question - Can DNSSEC be operated in a manner which meets, todd glassey
      • Re: Fwd: Re: Question - Can DNSSEC be operated in a manner which, Martin Rex
• BoingBoing: TCP, IP, and TCP/IP headers constructed in LEGOs, Barry Leiba
• Question - Can DNSSEC be operated in a manner which meets Khaled mandates?, todd glassey
  • Re: Question - Can DNSSEC be operated in a manner which meets Khaled mandates?, Peter DeVries
    • Re: Question - Can DNSSEC be operated in a manner which meets Khaled mandates?, todd glassey
      • Re: Question - Can DNSSEC be operated in a manner which meets Khaled mandates?, Phillip Hallam-Baker
      • Re: Question - Can DNSSEC be operated in a manner which meets Khaled mandates?, todd glassey
  • Re: Question - Can DNSSEC be operated in a manner which meets Khaled mandates?, Ted Ts'o
    • Re: Question - Can DNSSEC be operated in a manner which meets Khaled mandates?, todd glassey
    • Re: Question - Can DNSSEC be operated in a manner which meets Khaled mandates?, Masataka Ohta
• Huge number of subscriptions disabled on ietf lists, Cullen Jennings
• Follow up: Audio Streaming Info - IETF 78 July 25-30, 2010, Joel Jaeggli
• secdir review of draft-ietf-ippm-spatial-composition-15.txt, Stephen Hanna
• Re: Last Call: draft-saintandre-tls-server-id-check, =JeffH
  • Re: Last Call: draft-saintandre-tls-server-id-check, John C Klensin
    • Re: Last Call: draft-saintandre-tls-server-id-check, Andrew Sullivan
• Nomcom Enhancements: Improving the IETF leadership selection process, Dave CROCKER
  • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Brian E Carpenter
    • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Scott Brim
    • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Dave CROCKER
  • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Adrian Farrel
    • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Yoav Nir
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Dave CROCKER
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Phillip Hallam-Baker
  • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Lixia Zhang
    • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Dave CROCKER
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Fred Baker
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Dave CROCKER
      • Re: Nomcom Enhancements: Improving the IETF leadership selectionprocess, Doug Ewell
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Lixia Zhang
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Joel M. Halpern
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Brian E Carpenter
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Andrew Sullivan
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Barry Leiba
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Andrew Sullivan
    • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Jari Arkko
      • RE: Nomcom Enhancements: Improving the IETF leadership selection process, Ross Callon
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, John Leslie
      • Re: Nomcom Enhancements: Improving the IETF leadership selection process, Dave CROCKER
      • Re: Nomcom Enhancements: Improving the IETF leadership selectionprocess, Spencer Dawkins
• Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, John C Klensin
  • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Paul Hoffman
    • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, John C Klensin
      • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Paul Hoffman
      • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, John C Klensin
  • <Possible follow-ups>
  • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Peter Saint-Andre
    • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Shumon Huque
• http://www.ietf.org/tools/rfcdiff, IETF Chair
• secdir review of draft-ietf-ipsecme-roadmap, Richard L. Barnes
• SECDIR review: draft-hammer-hostmeta, Kurt Zeilenga
  • RE: SECDIR review: draft-hammer-hostmeta, Eran Hammer-Lahav
• Fwd: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Russ Housley
  • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Marshall Eubanks
    • RE: Historic Moment - Root zone of the Internet was just signedminutes ago!!!, Monique Morrow (mmorrow)
      • Re: Historic Moment - Root zone of the Internet was just signedminutes ago!!!, Russ White
  • Re: Fwd: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, todd glassey
  • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Iljitsch van Beijnum
    • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Andrew Sullivan
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Iljitsch van Beijnum
    • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Tony Finch
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Ronald van der Pol
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Tony Finch
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Iljitsch van Beijnum
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Tony Finch
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Andrew Sullivan
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Phillip Hallam-Baker
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Mark Andrews
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Phillip Hallam-Baker
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Mark Andrews
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Iljitsch van Beijnum
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Phillip Hallam-Baker
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Tony Finch
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Masataka Ohta
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Phillip Hallam-Baker
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Mark Andrews
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Masataka Ohta
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Phillip Hallam-Baker
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Masataka Ohta
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Paul Wouters
      • Re: Historic Moment - Root zone of the Internet was just signed minutes ago!!!, Tony Finch
• Privacy policy (draft-cooper-privacy-policy-01) comments, Thomson, Martin
• Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Paul Hoffman
  • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Shumon Huque
    • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Paul Hoffman
      • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Shumon Huque
      • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Paul Hoffman
      • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Shumon Huque
      • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Paul Hoffman
      • Re: Last Call: draft-saintandre-tls-server-id-check (Representation and Verification of Domain-Based Application Service Identity in Certificates Used with Transport Layer Security) to Proposed Standard, Shumon Huque
• FW: Nomcom 2010-2011: Results of Random Selection, Thomas Walsh
  • <Possible follow-ups>
  • Re: Nomcom 2010-2011: Results of Random Selection, Jiankang YAO
    • Re: Nomcom 2010-2011: Results of Random Selection, Marshall Eubanks
      • RE: Nomcom 2010-2011: Results of Random Selection, WORLEY, Dale R (Dale)
• The IETF Data Tracker and non-IETF streams for RFCs, Paul Hoffman
  • Re: The IETF Data Tracker and non-IETF streams for RFCs, todd glassey
    • Re: The IETF Data Tracker and non-IETF streams for RFCs, Paul Hoffman
• FW: Nomcom 2010-2011: List of Volunteers for Random Selection, Thomas Walsh
• secdir review of draft-ietf-msec-ipsec-group-counter-modes, Sam Hartman
  • Re: [secdir] secdir review of draft-ietf-msec-ipsec-group-counter-modes, Brian Weis
    • Re: [secdir] secdir review of draft-ietf-msec-ipsec-group-counter-modes, Sam Hartman
• web security happenings, Peter Saint-Andre
  • Re: web security happenings, Iljitsch van Beijnum
    • Re: web security happenings, Peter Saint-Andre
      • Re: web security happenings, Thomas Roessler
    • Re: web security happenings, Cullen Jennings
      • Re: web security happenings, Phillip Hallam-Baker
  • <Possible follow-ups>
  • Re: web security happenings, =JeffH
• FW: Nomcom 2010-2011: Final List of Volunteers (Updated), Thomas Walsh
• Re: Second Last Call: draft-ietf-keyprov-dskpp (Dynamic Symmetric Key Provisioning Protocol (DSKPP)) to Proposed Standard, "Martin J. Dürst"
  • RE: [KEYPROV] Second Last Call: draft-ietf-keyprov-dskpp (Dynamic Symmetric Key Provisioning Protocol (DSKPP)) to Proposed Standard, andrea.doherty
• DNSSEC Contributors, IETF Chair
  • RE: DNSSEC Contributors, Su, David H.
  • RE: DNSSEC Contributors, Murray S. Kucherawy
    • Re: DNSSEC Contributors, Russ Housley
  • SV: DNSSEC Contributors, Anne-Marie Eklund-LÃwinder
• Back to authentication on the IETF network (was: Re: IETF 78: getting to/from/around Maastricht), Chris Elliott
  • Re: Back to authentication on the IETF network (was: Re: IETF 78: getting to/from/around Maastricht), Ted Hardie
    • Re: Back to authentication on the IETF network (was: Re: IETF 78: getting to/from/around Maastricht), Chris Elliott
      • Re: Back to authentication on the IETF network, todd glassey
    • Re: Back to authentication on the IETF network (was: Re: IETF 78: getting to/from/around Maastricht), Randy Bush
      • Re: Back to authentication on the IETF network (was: Re: IETF 78: getting to/from/around Maastricht), Joel Jaeggli
• Gen-ART LC review of draft-ietf-msec-ipsec-group-counter-modes-05, Roni Even
  • <Possible follow-ups>
  • Gen-ART LC review of draft-ietf-msec-ipsec-group-counter-modes-05, Roni Even
• Last Call: draft-c1222-transport-over-ip (ANSI C12.22, IEEE 1703 and MC12.22 Transport Over IP) to Informational RFC, Avygdor Moise
• Re: Last Call: draft-ietf-kitten-gssapi-naming-exts (GSS-API Naming Extensions) to Proposed Standard, Simon Josefsson
  • <Possible follow-ups>
  • Re: Last Call: draft-ietf-kitten-gssapi-naming-exts (GSS-API Naming Extensions) to Proposed Standard, Sam Hartman
    • Re: Last Call: draft-ietf-kitten-gssapi-naming-exts (GSS-API Naming Extensions) to Proposed Standard, Nicolas Williams
• Re: [TLS] Second Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer Security (TLS) Extensions: Extension Definitions) to Proposed Standard, Paul Hoffman
• FW: Nomcom 2010-2011: Final List of Volunteers, Thomas Walsh
• Privacy Terminology, Hannes Tschofenig
  • Re: Privacy Terminology, Phillip Hallam-Baker
    • was Re: Privacy Terminology - this should not be complex..., todd glassey
• More on privacy: The Role of the IETF in Improving Privacy on the Internet, Hannes Tschofenig
• RE: [ippm] Last Call: draft-ietf-ippm-twamp-reflect-octets (TWAMP Reflect Octets and Symmetrical Size Features) to Proposed Standard, Steve Baillargeon
• What does a privacy policy mean ?, John Levine
  • Re: What does a privacy policy mean ?, Sabahattin Gucukoglu
  • Re: What does a privacy policy mean ?, Alissa Cooper
  • Re: What does a privacy policy mean ?, Marshall Eubanks
    • Re: What does a privacy policy mean ?, Dave CROCKER
      • Re: What does a privacy policy mean ?, todd glassey
    • Re: What does a privacy policy mean ?, todd glassey
• draft-douglass-timezone-xml-00 & Presence, James M. Polk
  • Re: draft-douglass-timezone-xml-00 & Presence, Cyrus Daboo
    • RE: draft-douglass-timezone-xml-00 & Presence, Glen Zorn
      • RE: draft-douglass-timezone-xml-00 & Presence, Cyrus Daboo
  • Re: draft-douglass-timezone-xml-00 & Presence, todd glassey
• Audio Streaming Info - IETF 78 July 25-30, 2010, Joel Jaeggli
• DNS aliasing at IETF 78: call for participation, Andrew Sullivan
• An updated ISD proposal, John C Klensin
• IETF privacy policy - update, Alissa Cooper
  • Re: IETF privacy policy - update, Melinda Shore
  • Re: IETF privacy policy - update, John C Klensin
    • Re: IETF privacy policy - update, Bob Hinden
  • Re: IETF privacy policy - update, Dave CROCKER
    • Re: IETF privacy policy - update, Marshall Eubanks
      • Re: IETF privacy policy - update, Dave CROCKER
      • Re: IETF privacy policy - update, John C Klensin
      • Re: IETF privacy policy - update, Alissa Cooper
      • Re: IETF privacy policy - update, Eliot Lear
      • Re: IETF privacy policy - update, John Morris
      • Re: IETF privacy policy - update, Ted Hardie
      • Re: IETF privacy policy - update, John C Klensin
  • Re: IETF privacy policy - update, SM
  • Re: IETF privacy policy - update, Eliot Lear
  • Re: IETF privacy policy - update, Iljitsch van Beijnum
    • Re: IETF privacy policy - update, joel jaeggli
      • Re: IETF privacy policy - update, todd glassey
      • Re: IETF privacy policy - update, Iljitsch van Beijnum
      • Re: IETF privacy policy - update, Alissa Cooper
      • Re: IETF privacy policy - update, Iljitsch van Beijnum
      • Re: IETF privacy policy - update, John Morris
      • Re: IETF privacy policy - update, Iljitsch van Beijnum
      • Re: IETF privacy policy - update, John Morris
      • Re: IETF privacy policy - update, Iljitsch van Beijnum
      • Re: IETF privacy policy - update, Melinda Shore
      • Re: IETF privacy policy - update, Sam Hartman
      • Re: IETF privacy policy - update, Ole Jacobsen
      • Re: IETF privacy policy - update, Sam Hartman
      • Re: IETF privacy policy - update, joel jaeggli
      • RE: IETF privacy policy - update, Yoav Nir
      • Re: IETF privacy policy - update, Henk Uijterwaal
      • Re: IETF privacy policy - update, Andrew Sullivan
      • Re: IETF privacy policy - update, Marshall Eubanks
      • Re: IETF privacy policy - update, jean-michel bernier de portzamparc
      • Re: IETF privacy policy - update, Melinda Shore
      • Re: IETF privacy policy - update, Martin Rex
      • Re: IETF privacy policy - update, joel jaeggli
      • Re: IETF privacy policy - update, Paul Hoffman
      • Re: IETF privacy policy - update, Melinda Shore
      • Re: IETF privacy policy - update, John Morris
      • Re: IETF privacy policy - update, Paul Hoffman
      • Re: IETF privacy policy - update, Andrew Sullivan
      • Re: IETF privacy policy - update, Sam Hartman
      • Re: IETF privacy policy - update, John Morris
      • Re: IETF privacy policy - update, Alissa Cooper
      • Re: IETF privacy policy - update, Randy Bush
      • Re: IETF privacy policy - update, joel jaeggli
      • Re: IETF privacy policy - update, Fred Baker
      • Re: IETF privacy policy - update, Melinda Shore
      • Re: IETF privacy policy - update, Fred Baker
      • Re: IETF privacy policy - update, Melinda Shore
      • Re: IETF privacy policy - update, Fred Baker
      • Re: IETF privacy policy - update, Larry Smith
      • Re: IETF privacy policy - update, David Morris
      • Re: IETF privacy policy - update, GTW
      • Re: IETF privacy policy - update, Henk Uijterwaal
      • Re: IETF privacy policy - update, Patrik Fältström
      • Re: IETF privacy policy - update, Fred Baker
      • Re: IETF privacy policy - update, Ted Hardie
      • Re: IETF privacy policy - update, Alissa Cooper
      • Re: IETF privacy policy - update, joel jaeggli
      • Re: IETF privacy policy - update, Randy Bush
      • Re: IETF privacy policy - update, Arnt Gulbrandsen
  • Re: IETF privacy policy - update, Nathaniel Borenstein
  • Re: IETF privacy policy - update, Karen O'Donoghue
    • Re: IETF privacy policy - update, todd glassey
  • Re: IETF privacy policy - update, Stephan Wenger
    • Re: IETF privacy policy - update, Alissa Cooper
      • Re: IETF privacy policy - update, Paul Hoffman
      • Re: IETF privacy policy - update, todd glassey
      • Re: IETF privacy policy - update, John Morris
      • Re: IETF privacy policy - update, Andrew Sullivan
      • Re: IETF privacy policy - update, Martin Rex
      • Re: IETF privacy policy - update, John Morris
      • RE: IETF privacy policy - update, Dearlove, Christopher (UK)
      • Re: IETF privacy policy - still a bad idea, John Levine
      • Re: IETF privacy policy - still a bad idea, Phillip Hallam-Baker
      • Re: IETF privacy policy - still a bad idea, John R. Levine
      • Re: IETF privacy policy - still a bad idea, Marshall Eubanks
      • Re: IETF privacy policy - still a bad idea, Dave CROCKER
      • Re: IETF privacy policy - still a bad idea, Marshall Eubanks
      • Re: IETF privacy policy - still a bad idea, Dave CROCKER
      • Re: IETF privacy policy - still a bad idea, Andrew Sullivan
      • Re: IETF privacy policy - still a bad idea, Marshall Eubanks
      • Re: IETF privacy policy - still a bad idea, Andrew Sullivan
      • Re: IETF privacy policy - still a bad idea, Dave CROCKER
      • Re: IETF privacy policy - still a bad idea, Andrew Sullivan
      • Re: IETF privacy policy - still a bad idea, Ole Jacobsen
      • Re: IETF privacy policy - still a bad idea, Dave CROCKER
      • Re: IETF privacy policy - still a bad idea, Phillip Hallam-Baker
      • Re: IETF privacy policy - still a bad idea, Fred Baker
      • Re: IETF privacy policy - still a bad idea, John R. Levine
      • Re: IETF privacy policy - still a bad idea, Fred Baker
      • What does a privacy policy mean?, John R. Levine
      • Re: What does a privacy policy mean?, Phillip Hallam-Baker
      • Re: IETF privacy policy - still a bad idea, todd glassey
      • Re: IETF privacy policy - still a bad idea, Arnt Gulbrandsen
      • Re: IETF privacy policy - still a bad idea, Marshall Eubanks
  • Re: IETF privacy policy - update, Cullen Jennings
    • Re: IETF privacy policy - update, Fred Baker
      • Re: IETF privacy policy - update, Peter Saint-Andre
      • RE: IETF privacy policy - update, Monique Morrow (mmorrow)
  • Comments on <draft-cooper-privacy-policy-01.txt>, Bob Hinden
    • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Hannes Tschofenig
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Randy Bush
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Hannes Tschofenig
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Randy Bush
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Hannes Tschofenig
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Randy Bush
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Joel Jaeggli
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Hannes Tschofenig
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, todd glassey
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Hannes Tschofenig
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Fred Baker
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Randy Bush
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Phillip Hallam-Baker
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Randy Bush
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Donald Eastlake
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, todd glassey
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Dave CROCKER
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Joel Jaeggli
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Dave CROCKER
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Randy Bush
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Dave CROCKER
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Randy Bush
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Dave CROCKER
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, John C Klensin
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Dave CROCKER
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Randy Bush
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Dave CROCKER
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Randy Bush
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Dave CROCKER
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, John C Klensin
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Dave CROCKER
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Fred Baker
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Martin Rex
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, todd glassey
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Martin Rex
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Joel Jaeggli
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, todd glassey
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Andrew Sullivan
    • Re: Comments on <draft-cooper-privacy-policy-01.txt>, Alissa Cooper
      • Re: Comments on <draft-cooper-privacy-policy-01.txt>, John C Klensin
• draft-housley-two-maturity-levels, John C Klensin
  • Re: draft-housley-two-maturity-levels, SM
    • Re: draft-housley-two-maturity-levels, Brian E Carpenter
      • Re: draft-housley-two-maturity-levels, Dave CROCKER
      • Re: draft-housley-two-maturity-levels, John C Klensin
      • Re: draft-housley-two-maturity-levels, Eric Rosen
      • Re: draft-housley-two-maturity-levels, Dave CROCKER
      • Re: draft-housley-two-maturity-levels, Julian Reschke
      • Re: draft-housley-two-maturity-levels, Dave CROCKER
      • Re: draft-housley-two-maturity-levels, Russ Housley
      • Re: draft-housley-two-maturity-levels, Brian E Carpenter
      • Re: draft-housley-two-maturity-levels, James M. Polk
      • Re: draft-housley-two-maturity-levels, Brian E Carpenter
      • Re: draft-housley-two-maturity-levels, Russ Housley
      • Re: draft-housley-two-maturity-levels, Barry Leiba
      • Re: draft-housley-two-maturity-levels, Brian E Carpenter
      • Re: draft-housley-two-maturity-levels, Eric Burger
      • Re: draft-housley-two-maturity-levels, John Levine
      • Re: draft-housley-two-maturity-levels, James M. Polk
      • Re: draft-housley-two-maturity-levels, Michael Richardson
      • Re: draft-housley-two-maturity-levels, Andrew Sullivan
      • Re: draft-housley-two-maturity-levels, Michael Richardson
      • Re: draft-housley-two-maturity-levels, Martin Rex
      • two independent implementations (Re: draft-housley-two-maturity-levels), Lars Eggert
      • Re: two independent implementations (Re: draft-housley-two-maturity-levels), James M. Polk
      • Re: two independent implementations (Re: draft-housley-two-maturity-levels), James M. Polk
      • RE: draft-housley-two-maturity-levels, Ross Callon
      • Re: draft-housley-two-maturity-levels, Phillip Hallam-Baker
      • Re: draft-housley-two-maturity-levels, Keith Moore
      • Re: draft-housley-two-maturity-levels, Ted Hardie
      • Re: draft-housley-two-maturity-levels, SM
      • Re: draft-housley-two-maturity-levels, Phillip Hallam-Baker
  • <Possible follow-ups>
  • Re: draft-housley-two-maturity-levels, Scott O. Bradner
    • Re: draft-housley-two-maturity-levels, Bert (IETF) Wijnen
    • Re: draft-housley-two-maturity-levels, Eric Burger
      • Re: draft-housley-two-maturity-levels, Dave CROCKER
      • Re: draft-housley-two-maturity-levels, Julian Reschke
      • Re: draft-housley-two-maturity-levels, Ralph Droms
      • Re: draft-housley-two-maturity-levels, John Leslie
    • Re: draft-housley-two-maturity-levels, Russ Housley
  • Re: draft-housley-two-maturity-levels, Scott O. Bradner
    • Re: draft-housley-two-maturity-levels, Michael Richardson
    • RE: draft-housley-two-maturity-levels, Tony Hain
      • Re: draft-housley-two-maturity-levels, John Leslie
      • RE: draft-housley-two-maturity-levels, Tony Hain
      • Re: draft-housley-two-maturity-levels, Phillip Hallam-Baker
      • Re: draft-housley-two-maturity-levels, Michael Richardson
      • Re: draft-housley-two-maturity-levels, Lars Eggert
      • Re: draft-housley-two-maturity-levels, Lars Eggert
      • RE: draft-housley-two-maturity-levels, Tony Hain
      • Re: two independent implementations, John Leslie
      • RE: two independent implementations, Tony Hain
      • Re: draft-housley-two-maturity-levels, Ralph Droms
  • Re: draft-housley-two-maturity-levels, Scott O. Bradner
    • Re: draft-housley-two-maturity-levels, Barry Leiba
    • Re: draft-housley-two-maturity-levels, Keith Moore
    • Re: draft-housley-two-maturity-levels, Phillip Hallam-Baker
  • Re: draft-housley-two-maturity-levels, RJ Atkinson
    • Re: draft-housley-two-maturity-levels, ned+ietf
      • Re: draft-housley-two-maturity-levels, Dave CROCKER
      • Re: draft-housley-two-maturity-levels, Peter Saint-Andre
      • Re: draft-housley-two-maturity-levels, Eric Burger
      • Re: draft-housley-two-maturity-levels, Phillip Hallam-Baker
      • Re: draft-housley-two-maturity-levels, ned+ietf
      • Re: draft-housley-two-maturity-levels, David Kessens
      • Re: draft-housley-two-maturity-levels, Russ Housley
      • Re: draft-housley-two-maturity-levels, Peter Saint-Andre
      • Re: draft-housley-two-maturity-levels, Joel M. Halpern
      • Re: draft-housley-two-maturity-levels, Peter Saint-Andre
      • Re: draft-housley-two-maturity-levels, Phillip Hallam-Baker
      • Re: draft-housley-two-maturity-levels, Tony Hansen
      • Re: draft-housley-two-maturity-levels, Mykyta Yevstifeyev
      • Re: draft-housley-two-maturity-levels, ned+ietf
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Re: draft-housley-two-maturity-levels, Russ Housley
      • New version of NroffEdit released for IETF80, Stefan Santesson
      • Re: New version of NroffEdit released for IETF80, Stefan Santesson
      • Re: draft-housley-two-maturity-levels, Joel M. Halpern
      • Re: draft-housley-two-maturity-levels, Mykyta Yevstifeyev
      • Re: draft-housley-two-maturity-levels, Joel M. Halpern
      • Re: draft-housley-two-maturity-levels, Mykyta Yevstifeyev
      • Re: draft-housley-two-maturity-levels, Dave CROCKER
      • Re: draft-housley-two-maturity-levels, Bob Hinden
      • Re: draft-housley-two-maturity-levels, Eric Burger
  • Re: draft-housley-two-maturity-levels, Scott O. Bradner
  • Re: draft-housley-two-maturity-levels, Scott O. Bradner
    • Re: draft-housley-two-maturity-levels, Phillip Hallam-Baker
      • RE: draft-housley-two-maturity-levels, Tony Hain
      • Re: draft-housley-two-maturity-levels, Bob Braden
      • Re: draft-housley-two-maturity-levels, Yoav Nir
      • RE: draft-housley-two-maturity-levels, Tony Hain
      • Re: draft-housley-two-maturity-levels, Bob Braden
      • Re: draft-housley-two-maturity-levels, Phillip Hallam-Baker
      • Re: draft-housley-two-maturity-levels, Joel Jaeggli
      • Re: draft-housley-two-maturity-levels, Phillip Hallam-Baker
  • Re: draft-housley-two-maturity-levels, Scott O. Bradner
  • Re: draft-housley-two-maturity-levels, RJ Atkinson
  • Re: draft-housley-two-maturity-levels, Scott O. Bradner
    • Re: draft-housley-two-maturity-levels, John C Klensin
      • Re: draft-housley-two-maturity-levels, Gonzalo Camarillo
      • Re: draft-housley-two-maturity-levels, John C Klensin
      • Re: draft-housley-two-maturity-levels, Doug Barton
    • Re: draft-housley-two-maturity-levels, Dave CROCKER
    • Re: draft-housley-two-maturity-levels, SM
    • Re: draft-housley-two-maturity-levels, Martin Rex
      • Re: draft-housley-two-maturity-levels, Mark Atwood
      • Re: draft-housley-two-maturity-levels, John Leslie
    • Re: draft-housley-two-maturity-levels, Brian E Carpenter
      • Re: draft-housley-two-maturity-levels, Dave CROCKER
      • Re: draft-housley-two-maturity-levels, Brian E Carpenter
  • draft-housley-two-maturity-levels, Jari Arkko
    • Re: draft-housley-two-maturity-levels, Brian E Carpenter
    • Re: draft-housley-two-maturity-levels, Chris Newman
  • Re: draft-housley-two-maturity-levels, Scott O. Bradner
    • Re: draft-housley-two-maturity-levels, Robert Sparks
      • Re: draft-housley-two-maturity-levels, Eric Burger
      • Re: draft-housley-two-maturity-levels, Peter Saint-Andre
      • Re: draft-housley-two-maturity-levels, Keith Moore
      • Re: draft-housley-two-maturity-levels, Peter Saint-Andre
      • Re: draft-housley-two-maturity-levels, Brian E Carpenter
      • Re: draft-housley-two-maturity-levels, Pete Resnick
      • Re: draft-housley-two-maturity-levels, Joel M. Halpern
      • Re: draft-housley-two-maturity-levels, Peter Saint-Andre
      • Re: draft-housley-two-maturity-levels, John C Klensin
      • Re: draft-housley-two-maturity-levels, Joel M. Halpern
      • Re: draft-housley-two-maturity-levels, John C Klensin
      • Re: draft-housley-two-maturity-levels, John Leslie
      • Re: draft-housley-two-maturity-levels, Brian E Carpenter
      • Re: draft-housley-two-maturity-levels, Scott O Bradner
    • Conclusion of the last call on draft-housley-two-maturity-levels, Jari Arkko
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, SM
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, Hector Santos
      • RE: Conclusion of the last call on draft-housley-two-maturity-levels, Ross Callon
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, Andrew Sullivan
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, Keith Moore
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, ned+ietf
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, Ted Hardie
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, John C Klensin
      • Who raised the bar? [Conclusion of the last call on draft-housley-two-maturity-levels], Brian E Carpenter
      • Re: Who raised the bar? [Conclusion of the last call on draft-housley-two-maturity-levels], Julian Reschke
      • Re: Who raised the bar?, Brian E Carpenter
      • Re: Who raised the bar? [Conclusion of the last call on draft-housley-two-maturity-levels], Ted Hardie
      • Re: Who raised the bar? [Conclusion of the last call on draft-housley-two-maturity-levels], Keith Moore
      • Re: Who raised the bar? [Conclusion of the last call on draft-housley-two-maturity-levels], Dave Cridland
      • Re: Who raised the bar? [Conclusion of the last call on draft-housley-two-maturity-levels], Cullen Jennings
      • Re: Who raised the bar? [Conclusion of the last call on draft-housley-two-maturity-levels], Hector Santos
      • Re: Who raised the bar? [Conclusion of the last call on draft-housley-two-maturity-levels], SM
      • Re: Who raised the bar? [Conclusion of the last call on draft-housley-two-maturity-levels], JP Vasseur
      • Re: Who raised the bar? [Conclusion of the last call on draft-housley-two-maturity-levels], JP Vasseur
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, Keith Moore
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, Ted Hardie
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, Fred Baker
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, Keith Moore
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, John Leslie
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, Keith Moore
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, t.petch
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, Keith Moore
      • Re: Conclusion of the last call on draft-housley-two-maturity-levels, ned+ietf