IETF Discussion Archive - Thread Index

• Re: PKIs and trust, (continued)
  • Re: PKIs and trust, Valdis . Kletnieks
  • Re: PKIs and trust, Paul Hoffman / IMC
  • Re: PKIs and trust, Valdis . Kletnieks
  • Re: PKIs and trust, Paul Hoffman / IMC
  • Re: PKIs and trust, Valdis . Kletnieks
  • Re: PKIs and trust, Eliot Lear
  • Re: PKIs and trust, Leif Johansson
  • Re: PKIs and trust, Keith Moore
  • RE: PKIs and trust, Tony Hain
  • Re: PKIs and trust, Neal McBurnett
  • Message not available
  • Re: PKIs and trust, Keith Moore
  • Re: PKIs and trust, Masataka Ohta
  • Re: PKIs and trust, Leif Johansson
  • Re: PKIs and trust, Valdis . Kletnieks
  • Re: PKIs and trust, Keith Moore
  • Re: PKIs and trust, Stephen Kent
  • Re: PKIs and trust, Masataka Ohta
  • Re: PKIs and trust, Stephen Kent
  • Re: PKIs and trust, Masataka Ohta
  • Re: PKIs and trust, Stephen Kent
  • Re: PKIs and trust, Masataka Ohta
  • Message not available
  • Re[2]: PKIs and trust, Anthony G. Atkielski
  • Re: PKIs and trust, Franck Martin
  • Re: ITU takes over?, Ole J. Jacobsen
    • Re: ITU takes over?, Einar Stefferud
    • Message not available
    • Re[2]: ITU takes over?, Anthony G. Atkielski
    • Re: ITU takes over?, Ole J. Jacobsen
    • www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Simon Leinen
    • Re: www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Stig Venaas
    • Re: www.isoc.org unreachable when ECN is used, Simon Leinen
    • Re[2]: www.isoc.org unreachable when ECN is used, Anthony G. Atkielski
    • Re: Re[2]: www.isoc.org unreachable when ECN is used, Valdis . Kletnieks
    • Re[4]: www.isoc.org unreachable when ECN is used, Anthony G. Atkielski
    • Re: Re[4]: www.isoc.org unreachable when ECN is used, Theodore Ts'o
    • Re[6]: www.isoc.org unreachable when ECN is used, Anthony G. Atkielski
    • Re: Re[6]: www.isoc.org unreachable when ECN is used, Theodore Ts'o
    • Re: Re[6]: www.isoc.org unreachable when ECN is used, Mark Smith
    • Re[8]: www.isoc.org unreachable when ECN is used, Anthony G. Atkielski
    • Re: Re[8]: www.isoc.org unreachable when ECN is used, Franck Martin
    • Re[10]: www.isoc.org unreachable when ECN is used, Anthony G. Atkielski
    • Re: Re[10]: www.isoc.org unreachable when ECN is used, Franck Martin
    • Re[12]: www.isoc.org unreachable when ECN is used, Anthony G. Atkielski
    • Re: Re[8]: www.isoc.org unreachable when ECN is used, James M Galvin
    • Re: Re[8]: www.isoc.org unreachable when ECN is used, Spencer Dawkins
    • Re[8]: www.isoc.org unreachable when ECN is used, Anthony G. Atkielski
    • Re: www.isoc.org unreachable when ECN is used, kent
    • Re[2]: www.isoc.org unreachable when ECN is used, Anthony G. Atkielski
    • Re: www.isoc.org unreachable when ECN is used, kent
    • Re: www.isoc.org unreachable when ECN is used, Franck Martin
    • Re[2]: www.isoc.org unreachable when ECN is used, Einar Stefferud
    • Re[2]: www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Anthony G. Atkielski
    • Re: Re[2]: www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Scott Bradner
    • Re[4]: www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Anthony G. Atkielski
    • Re: Re[2]: www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Valdis . Kletnieks
    • Re: Re[2]: www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Scott Bradner
    • Re: Re[2]: www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Vernon Schryver
    • Re[4]: www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Anthony G. Atkielski
    • Re: www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Franck Martin
    • Re: www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Theodore Ts'o
    • Re: www.isoc.org unreachable when ECN is used [was: Re: ITU takes over?], Tim Chown
  • Re: ITU takes over?, vinton g. cerf
• just a brief note about anycast, Eliot Lear
  • Re: just a brief note about anycast, jfcm
    • Re: just a brief note about anycast, Bill Manning
      • Re: just a brief note about anycast, jfcm
      • Re: just a brief note about anycast, Dean Anderson
      • Re: just a brief note about anycast, Bill Manning
      • Re: just a brief note about anycast, jfcm
      • Re: just a brief note about anycast, Bill Manning
    • Re: just a brief note about anycast, Randy Presuhn
      • RE: just a brief note about anycast, Steve Schieberl
      • Re: just a brief note about anycast, Dean Anderson
      • Re: just a brief note about anycast, Randy Presuhn
      • Re: just a brief note about anycast, Franck Martin
      • Re: just a brief note about anycast, Paul Hoffman / IMC
      • Re: just a brief note about anycast, Michael Richardson
      • Re: just a brief note about anycast, Dean Anderson
      • Re: just a brief note about anycast, Dean Anderson
      • Re: just a brief note about anycast, Franck Martin
      • Re: just a brief note about anycast, Kurtis Lindqvist
      • Re: just a brief note about anycast, jfcm
      • Re: just a brief note about anycast, Franck Martin
      • Message not available
      • Re: just a brief note about anycast, Franck Martin
      • Re: just a brief note about anycast, Kurtis Lindqvist
      • Re[2]: just a brief note about anycast, Anthony G. Atkielski
      • Re: Re[2]: just a brief note about anycast, Franck Martin
• Re: national security - proposed follow-up, jfcm
  • Re: national security - proposed follow-up, grenville armitage
• Synopsis of Internet relevant White house document(s) regarding security, Dan Kolis
• FYI - US DoC NIST Workshop on SPAM, Richard Shockey
• SMTP compressed protocol..., Franck Martin
  • Re: SMTP compressed protocol..., John C Klensin
    • Re: SMTP compressed protocol..., Carsten Bormann
      • Re: SMTP compressed protocol..., John C Klensin
      • Re: SMTP compressed protocol..., stanislav shalunov
      • Re: SMTP compressed protocol..., John C Klensin
      • Re: SMTP compressed protocol..., stanislav shalunov
      • Re: SMTP compressed protocol..., Valdis . Kletnieks
    • Re: SMTP compressed protocol..., Spencer Dawkins
  • Re: SMTP compressed protocol..., stanislav shalunov
  • Re: SMTP compressed protocol..., John Stracke
    • Re: SMTP compressed protocol..., ned . freed
  • <Possible follow-ups>
  • RE: SMTP compressed protocol..., Eric Burger
• An apology of sorts, Dan Kolis
  • RE: An apology of sorts, Tomson Eric \(Yahoo.fr\)
• Ietf ITU DNS stuff III, Dan Kolis
  • Re: Ietf ITU DNS stuff III, Franck Martin
    • Re: Ietf ITU DNS stuff III, Stephen Sprunk
  • <Possible follow-ups>
  • Re: Ietf ITU DNS stuff III, USPhoenix
    • Re: Ietf ITU DNS stuff III, Paul Vixie
      • Re: Ietf ITU DNS stuff III, jfcm
      • Re: Ietf ITU DNS stuff III, Franck Martin
  • Re: Ietf ITU DNS stuff III, Dan Kolis
  • Re: Ietf ITU DNS stuff III, Franck Martin
• Ietf ITU DNS stuff, Dan Kolis
  • Re: Ietf ITU DNS stuff, Dean Anderson
    • Re: Ietf ITU DNS stuff, Mike S
      • RE: Ietf ITU DNS stuff, Steve Silverman
      • RE: Ietf ITU DNS stuff, Mike S
      • Re: Ietf ITU DNS stuff, grenville armitage
      • Re: Ietf ITU DNS stuff, jfcm
      • Re: Ietf ITU DNS stuff, John C Klensin
      • Re: Ietf ITU DNS stuff, Masataka Ohta
      • Re: Ietf ITU DNS stuff, jfcm
      • Re: Ietf ITU DNS stuff, Jaap Akkerhuis
• RE: IPv6 addressing limitations (was "national security"), Schiro, Dan
  • Re: IPv6 addressing limitations (was "national security"), Keith Moore
  • Re[2]: IPv6 addressing limitations (was "national security"), Anthony G. Atkielski
  • Re: IPv6 addressing limitations (was "national security"), Iljitsch van Beijnum
  • <Possible follow-ups>
  • Re: Re[6]: IPv6 addressing limitations (was "national security"), Johnny Eriksson
    • Re[8]: IPv6 addressing limitations (was "national security"), Anthony G. Atkielski
• arguments against NAT?, Zefram
  • Re: arguments against NAT?, Anthony G. Atkielski
    • Re: arguments against NAT?, Spencer Dawkins
      • Re: arguments against NAT?, Spencer Dawkins
      • Re[2]: arguments against NAT?, Anthony G. Atkielski
      • Re: arguments against NAT?, Masataka Ohta
      • Re: arguments against NAT?, Valdis . Kletnieks
      • Re: arguments against NAT?, Melinda Shore
      • Re: arguments against NAT?, Joe Touch
      • Re: arguments against NAT?, Zefram
    • Re: arguments against NAT? - what breaks, Doug Royer
      • Re: arguments against NAT? - what breaks, Joe Touch
  • Re: arguments against NAT?, Eliot Lear
  • Re: arguments against NAT?, Joe Touch
  • Re: arguments against NAT?, Keith Moore
  • Re: arguments against NAT?, Paul Vixie
  • <Possible follow-ups>
  • RE: arguments against NAT?, Michel Py
    • Re: arguments against NAT?, Melinda Shore
  • RE: arguments against NAT?, Michel Py
    • Re: arguments against NAT?, Masataka Ohta
    • RE: arguments against NAT?, Armando L. Caro Jr.
  • RE: arguments against NAT?, Michel Py
  • RE: arguments against NAT?, Jeff Johnson
  • RE: arguments against NAT?, Michel Py
    • Re: arguments against NAT?, Valdis . Kletnieks
    • Re: arguments against NAT?, Keith Moore
      • Re: arguments against NAT?, Leif Johansson
    • RE: arguments against NAT?, Armando L. Caro Jr.
    • Re: arguments against NAT?, grenville armitage
  • Re: arguments against NAT?, Joe Touch
• ICANN but I CAN'T, sometimes, Dan Kolis
• U.S. Anti-spam Bill and the IETF, Yakov Shafranovich
• Crypto tokens in addresses, Christian Huitema
• Re[4]: national security, Anthony G. Atkielski
  • Re: Re[4]: national security, Valdis . Kletnieks
    • Re: Re[4]: national security, Tim Chown
      • Re: Re[4]: national security, shogunx
      • Re: Re[4]: national security, Valdis . Kletnieks
      • Re: IPv6 address space lifetime, was: national security, Iljitsch van Beijnum
      • Re: IPv6 address space lifetime, was: national security, Loa Andersson
      • Re[2]: IPv6 address space lifetime, was: national security, Anthony G. Atkielski
  • <Possible follow-ups>
  • RE: national security, Michel Py
  • RE: Re[4]: national security, Michel Py
    • RE: Re[4]: national security, shogunx
• media type?, Jeroen Bekaert
  • Re: media type?, Valdis . Kletnieks
    • RE: media type?, Jeroen Bekaert
      • Re: media type?, Nathaniel Borenstein
• From Unicode Consortium: Proposed changes to Bidi, Patrik Fältström
• AW: IETF58 - Network Facts, Hans Peter Dittler
  • Message not available
    • national security, jfcm
      • Message not available
      • Message not available
      • RE: national security, jfcm
      • Re: national security, Iljitsch van Beijnum
      • Re[2]: national security, Anthony G. Atkielski
      • Re: Re[2]: national security, Iljitsch van Beijnum
      • Re[4]: national security, Anthony G. Atkielski
      • Re[4]: national security, Donald Eastlake 3rd
      • Re[5]: national security, Anthony G. Atkielski
      • Re: national security, John Kristoff
      • Re: Re[4]: national security, Iljitsch van Beijnum
      • Re[6]: national security, Anthony G. Atkielski
      • Re: Re[6]: national security, Kurt Erik Lindqvist
      • Re[8]: national security, Anthony G. Atkielski
      • Re: Re[4]: national security, Valdis . Kletnieks
      • Re[6]: national security, Anthony G. Atkielski
      • IPv6 addressing limitations (was "national security"), Keith Moore
      • Re: IPv6 addressing limitations (was "national security"), Anthony G. Atkielski
      • Re: IPv6 addressing limitations (was "national security"), Iljitsch van Beijnum
      • Re[2]: IPv6 addressing limitations (was "national security"), Anthony G. Atkielski
      • Re: IPv6 addressing limitations (was "national security"), Bob Hinden
      • Re[2]: IPv6 addressing limitations (was "national security"), Anthony G. Atkielski
      • Re[2]: IPv6 addressing limitations (was "national security"), Anthony G. Atkielski
      • Re: Re[2]: IPv6 addressing limitations (was "national security"), Iljitsch van Beijnum
      • Re: IPv6 addressing limitations (was "national security"), Masataka Ohta
      • Re: IPv6 addressing limitations (was "national security"), jfcm
      • Re: IPv6 addressing limitations (was "national security"), Masataka Ohta
      • Re[4]: IPv6 addressing limitations (was "national security"), Anthony G. Atkielski
      • Re: Re[4]: IPv6 addressing limitations (was "national security"), Valdis . Kletnieks
      • Re[6]: IPv6 addressing limitations (was "national security"), Anthony G. Atkielski
      • Re: IPv6 addressing limitations (was "national security"), Masataka Ohta
      • Re[2]: IPv6 addressing limitations (was "national security"), Anthony G. Atkielski
      • Re: IPv6 addressing limitations (was "national security"), Masataka Ohta
      • Re[2]: IPv6 addressing limitations (was "national security"), Anthony G. Atkielski
      • Re: IPv6 addressing limitations (was "national security"), Masataka Ohta
      • Re[2]: IPv6 addressing limitations (was "national security"), Anthony G. Atkielski
      • Re: IPv6 addressing limitations (was "national security"), Iljitsch van Beijnum
      • Re: IPv6 addressing limitations (was "national security"), Keith Moore
      • Re: IPv6 addressing limitations (was "national security"), Masataka Ohta
      • Re: national security, Jari Arkko
      • Re[2]: national security, Anthony G. Atkielski
      • Re: Re[2]: national security, Spencer Dawkins
      • Re[4]: national security, Anthony G. Atkielski
      • Re: Re[2]: national security, Valdis . Kletnieks
      • Re[4]: national security, Anthony G. Atkielski
      • Re[2]: national security, jfcm
      • Re[3]: national security, Anthony G. Atkielski
      • Re: Re[3]: national security, Valdis . Kletnieks
      • Re: Re[3]: national security, jfcm
      • Re[3]: national security, jfcm
      • Re: Re[3]: national security, John C Klensin
      • Re: national security, Paul Robinson
      • Re: national security, vinton g. cerf
      • Re: national security, jfcm
      • Re: national security, Dean Anderson
      • Re: national security, Valdis . Kletnieks
      • Re: national security, Kurt Erik Lindqvist
      • Re: national security, Franck Martin
      • Re: national security, Kurt Erik Lindqvist
      • Re: national security, jfcm
      • Re: national security, Kurt Erik Lindqvist
      • Re: national security, Dean Anderson
      • Re: national security, jfcm
      • Re: national security, Kurt Erik Lindqvist
      • Re: national security, Franck Martin
      • Message not available
      • Re: national security, Franck Martin
      • Re: national security, Paul Vixie
      • Re: national security, Dean Anderson
      • Re: national security, jfcm
      • Re: national security, Franck Martin
      • Re: national security, jfcm
      • Re: national security, Matt Larson
      • Re: national security, Iljitsch van Beijnum
      • Re: national security, Dean Anderson
      • Re: national security, Iljitsch van Beijnum
      • Re: national security, jfcm
      • Re: national security, Jaap Akkerhuis
      • Re: national security, Bill Manning
      • Re: national security, Dean Anderson
      • Re: national security, Iljitsch van Beijnum
      • Re: national security, Paul Vixie
      • Re: national security, Iljitsch van Beijnum
      • Re: national security, Paul Vixie
      • Re: /48 micro allocations for v6 root servers, was: national security, Iljitsch van Beijnum
      • Re: /48 micro allocations for v6 root servers, was: national security, Paul Vixie
      • Re: /48 micro allocations for v6 root servers, was: national security, Bill Manning
      • Re: /48 micro allocations for v6 root servers, was: national security, Paul Vixie
      • Re: /48 micro allocations for v6 root servers, was: national security, Bill Manning
      • Re: /48 micro allocations for v6 root servers, was: national security, John Stracke
      • RE: /48 micro allocations for v6 root servers, was: national security, Jeroen Massar
      • Re: [ipv6-wg at ripe.net] RE: /48 micro allocations for v6 root servers, was: national security, Gert Doering
      • RE: [ipv6-wg at ripe.net] RE: /48 micro allocations for v6 root servers, was: national security, Jeroen Massar
      • Re: [ipv6-wg at ripe.net] RE: /48 micro allocations for v6 root servers, was: national security, Bill Manning
      • RE: /48 micro allocations for v6 root servers, was: national security, Jeroen Massar
      • Re: /48 micro allocations for v6 root servers, was: national security, Paul Vixie
      • Re: /48 micro allocations for v6 root servers, was: national security, Bill Manning
      • Re: [ipv6-wg at ripe.net] RE: /48 micro allocations for v6 root servers, was: national security, Joao Damas
      • RE: [ipv6-wg at ripe.net] RE: /48 micro allocations for v6 root servers, was: national security, Jeroen Massar
      • Re: [ipv6-wg at ripe.net] RE: /48 micro allocations for v6 root servers, was: national security, Sascha Lenz
      • Re: /48 micro allocations for v6 root servers, was: national security, Iljitsch van Beijnum
      • Re: /48 micro allocations for v6 root servers, was: national security, jfcm
      • Re: /48 micro allocations for v6 root servers, was: national security, Iljitsch van Beijnum
      • Re: /48 micro allocations for v6 root servers, was: national security, Iljitsch van Beijnum
      • Re: /48 micro allocations for v6 root servers, was: national security, leo vegoda
      • Re: /48 micro allocations for v6 root servers, was: national security, Iljitsch van Beijnum
      • Re: /48 micro allocations for v6 root servers, was: national security, leo vegoda
      • Re: /48 micro allocations for v6 root servers, was: national security, Bill Manning
      • Re: /48 micro allocations for v6 root servers, was: national security, leo vegoda
      • Re: /48 micro allocations for v6 root servers, was: national security, leo vegoda
      • Re: /48 micro allocations for v6 root servers, was: national security, Zefram
      • Re: /48 micro allocations for v6 root servers, was: national security, Bill Manning
      • Re: /48 micro allocations for v6 root servers, was: national security, Valdis . Kletnieks
      • Re: /48 micro allocations for v6 root servers, was: national security, Zefram
      • RE: /48 micro allocations for v6 root servers, was: national security, Jeroen Massar
      • Re: /48 micro allocations for v6 root servers, was: national security, Bill Manning
      • Re: /48 micro allocations for v6 root servers, was: national security, Masataka Ohta
      • Re: /48 micro allocations for v6 root servers, was: national security, Iljitsch van Beijnum
      • Re: /48 micro allocations for v6 root servers, was: national security, Franck Martin
      • RE: /48 micro allocations for v6 root servers, was: nationalsecurity, Jeroen Massar
      • Re: /48 micro allocations for v6 root servers, was: national security, Ted Hardie
      • Re: /48 micro allocations for v6 root servers, was: national security, Mark Prior
      • Re: national security, Joe Abley
      • Re: national security, Masataka Ohta
      • Re: national security, Joe Abley
      • Re: national security, Masataka Ohta
      • Re: national security, Dean Anderson
      • Re: national security, Joe Abley
      • Re: national security, Franck Martin
      • Re: national security, Kurt Erik Lindqvist
      • Re: national security, Karl Auerbach
      • Re: national security, vinton g. cerf
      • Re: national security, Karl Auerbach
      • Re: national security, vinton g. cerf
      • Re: national security, Bill Manning
      • Re: national security, Karl Auerbach
      • Re: national security, Paul Vixie
      • Re: national security, Karl Auerbach
      • Re: national security, vinton g. cerf
      • Re: national security, John C Klensin
      • Re: national security, Michael Froomkin - U.Miami School of Law
      • Re: national security, Masataka Ohta
      • Re: national security, vinton g. cerf
      • Re: Re[3]: national security, jfcm
      • Re: Re[3]: national security, Kurt Erik Lindqvist
      • Re: Re[3]: national security, jfcm
      • Re: Re[3]: national security, John C Klensin
      • Re: Re[3]: national security, jfcm
      • Re: Re[3]: national security, Kurt Erik Lindqvist
      • Re: Re[3]: national security, vinton g. cerf
      • Re: Re[3]: national security, jfcm
      • Re[2]: national security, Philip J. Nesser II
      • Re: national security, Jaap Akkerhuis
      • Re: national security, jfcm
      • Re: national security, Paul Vixie
      • Re: national security, J-F C. (Jefsey) Morfin
      • Re: national security, Paul Vixie
      • Re: national security, jfcm
      • Re: national security, Michael H. Lambert
      • Re: national security, jfcm
      • Re: national security, Harald Tveit Alvestrand
• draft newtrk BOF minutes, Scott Bradner
• How to submit a draft, Dinesh Kumar
  • Re: How to submit a draft, Paul Hoffman / IMC
  • Re: How to submit a draft, Frank Strauss
    • Re: How to submit a draft, Tim Chown
• practical subnet sizes smaller than /26, /27, ..., John Martin
• RE: IAB Response to Tony Hain's appeal of October 9, 2003, Tony Hain
• howto WLAN, several subnets, Alexandru Petrescu
  • Re: howto WLAN, several subnets, Joel Jaeggli
    • Re: howto WLAN, several subnets, Alexandru Petrescu
      • Re: howto WLAN, several subnets, Joel Jaeggli
      • Re: howto WLAN, several subnets, Alexandru Petrescu
      • Re: howto WLAN, several subnets, Joel Jaeggli
      • Re: howto WLAN, several subnets, Michael Richardson
      • Re: howto WLAN, several subnets, Alexandru Petrescu
      • Re: howto WLAN, several subnets, shogunx
      • Re: howto WLAN, several subnets, Joel Jaeggli
      • Re: howto WLAN, several subnets, Alexandru Petrescu
      • Re: howto WLAN, several subnets, Andrew Partan
      • Re: howto WLAN, several subnets, Michael Richardson
      • Re: howto WLAN, several subnets, Alexandru Petrescu
      • Re: howto WLAN, several subnets, Vernon Schryver
  • Re: howto WLAN, several subnets, Pekka Savola
    • Re: howto WLAN, several subnets, Alexandru Petrescu
• New list to discuss interaction of APPs and proposed Lower Layer Identifiers, hardie
• Rf Id tag protocol, escom
  • Re: Rf Id tag protocol, Bill Manning
  • <Possible follow-ups>
  • Re: Rf Id tag protocol, escom
    • unsubscribe, Claudio Lori
  • RE: Rf Id tag protocol, Robert . Shaw
    • RFID and EPCglobal, Richard Shockey
      • Re: RFID and EPCglobal, Michael Mealling
• Re: i18n name badges (Modified by Iljitsch van Beijnum), Iljitsch van Beijnum
• IETF58 - Network Facts, Brett Thorson
  • Re: IETF58 - Network Facts, Theodore Ts'o
    • Re: IETF58 - Network Facts, Melinda Shore
  • RE: IETF58 - Network Facts, Vach Kompella
  • <Possible follow-ups>
  • RE: IETF58 - Network Facts, Gordon . Lennox
    • Re: WLAN's and trains (was: IETF58 - Network Facts_, Alexandru Petrescu
  • RE: IETF58 - Network Facts, Adam Roach
    • Re: IETF58 - Network Facts, Steven M. Bellovin
  • Re: IETF58 - Network Facts, Tom Petch
• i18n name badges, Peter Saint-Andre
  • Re: i18n name badges, Dave Crocker
    • Re: i18n name badges, John C Klensin
      • Re: i18n name badges, JORDI PALET MARTINEZ
  • Re: i18n name badges, Keith Moore
    • Re: i18n name badges, JORDI PALET MARTINEZ
      • Re: i18n name badges, Leif Johansson
      • Re: i18n name badges, Keith Moore
  • Re: i18n name badges, Fred Baker
    • Re: i18n name badges, John C Klensin
      • Re: i18n name badges, Ole J. Jacobsen
      • Re: i18n name badges, Valdis . Kletnieks
    • Message not available
      • Re: i18n name badges, Dave Crocker
      • Re: i18n name badges, James Seng
      • Re: i18n name badges, Iljitsch van Beijnum
      • Re: i18n name badges, John C Klensin
      • Re: i18n name badges, Dave Crocker
      • Re: i18n name badges, James Seng
      • Re: i18n name badges, Iljitsch van Beijnum
      • Re: i18n name badges, Eric A. Hall
      • Re: i18n name badges, Paul Hoffman / IMC
  • <Possible follow-ups>
  • RE: i18n name badges, Rosen, Brian
    • Re: i18n name badges, JORDI PALET MARTINEZ
      • Re: i18n name badges, Steven M. Bellovin
      • Re: i18n name badges, Ari Ollikainen
      • Re: i18n name badges, John Stracke
      • RE: i18n name badges, Steve Silverman
      • Re: i18n name badges, Iljitsch van Beijnum
      • Re: i18n name badges, John Stracke
  • RE: i18n name badges, Rosen, Brian
• Plans for IETF - 60, Brett Thorson
  • Re: Plans for IETF - 60, Paul Hoffman / IMC
  • Re: Plans for IETF - 60, Simon Leinen
• report on the wlan difficulties in IETF?, Jari Arkko
  • Re: report on the wlan difficulties in IETF?, Theodore Ts'o
    • Re: report on the wlan difficulties in IETF?, Steven M. Bellovin
  • Re: report on the wlan difficulties in IETF?, Brett Thorson
    • Re: report on the wlan difficulties in IETF?, Jari Arkko
  • Re: report on the wlan difficulties in IETF?, Mike S
• Re: Implementing DNS client for support IPv6/IPv4, Leif Johansson
  • Re: Implementing DNS client for support IPv6/IPv4, JORDI PALET MARTINEZ
• fixing the IETF, Mark Allman
  • Re: [Solutions] fixing the IETF, Spencer Dawkins
• newtrk mailing list setup, Scott Bradner
• Notes from this week's Plenaries, Spencer Dawkins
  • Re: Notes from this week's Plenaries, Franck Martin
• RE: IETF58 - Network Status, Michel Py
  • Re: IETF58 - Network Status, Perry E.Metzger
    • Re: IETF58 - Network Status, Randy Bush
      • Re: IETF58 - Network Status, Joel Jaeggli
      • Re: IETF58 - Network Status, Perry E.Metzger
      • Re: IETF58 - Network Status, Simon Leinen
      • Re: IETF58 - Network Status, Marcus Leech
      • Re: IETF58 - Network Status, Doug Barton
      • Re: IETF58 - Network Status, shogunx
      • Re: IETF58 - Network Status, Jim Martin
      • Re: IETF58 - Network Status, Tim Chown
      • Re: IETF58 - Network Status, Joel Jaeggli
      • Re: IETF58 - Network Status, Henk Uijterwaal (RIPE-NCC)
      • Re: IETF58 - Network Status, Iljitsch van Beijnum
      • Re: IETF58 - Network Status, Spencer Dawkins
  • Re: IETF58 - Network Status, Carsten Bormann
    • Re: IETF58 - Network Status, Iljitsch van Beijnum
  • <Possible follow-ups>
  • RE: IETF58 - Network Status, Romascanu, Dan (Dan)
    • Re: [58crew] RE: IETF58 - Network Status, Brett Thorson
      • Re: [58crew] RE: IETF58 - Network Status, Tim Chown
    • RE: IETF58 - Network Status, Harald Tveit Alvestrand
      • RE: IETF58 - Network Status, Randy Bush
      • Re: IETF58 - Network Status, Steven M. Bellovin
      • Re: IETF58 - Network Status, Valdis . Kletnieks
      • Re: [58crew] RE: IETF58 - Network Status, Scott Lystig Fritchie
      • Re: [58crew] RE: IETF58 - Network Status, Chris Elliott
      • Re: [58crew] RE: IETF58 - Network Status, Randy Bush
      • Re: [58crew] RE: IETF58 - Network Status, Franck Martin
      • Re: [58crew] RE: IETF58 - Network Status, Michael Richardson
      • Re: [58crew] RE: IETF58 - Network Status, Perry E.Metzger
      • Re: [58crew] RE: IETF58 - Network Status, Marcus Leech
      • Re: [58crew] RE: IETF58 - Network Status, Iljitsch van Beijnum
      • Re: [58crew] RE: IETF58 - Network Status, Perry E.Metzger
      • Re: [58crew] RE: IETF58 - Network Status, Masataka Ohta
      • Re: [58crew] RE: IETF58 - Network Status, Perry E.Metzger
      • Re: [58crew] RE: IETF58 - Network Status, Masataka Ohta
      • Re: [58crew] RE: IETF58 - Network Status, Iljitsch van Beijnum
      • Re: [58crew] RE: IETF58 - Network Status, Perry E.Metzger
      • Re: [58crew] RE: IETF58 - Network Status, Iljitsch van Beijnum
      • Re: [58crew] RE: IETF58 - Network Status, Perry E.Metzger
      • Re: [58crew] RE: IETF58 - Network Status, Masataka Ohta
      • RE: IETF58 - Network Status, Paul Hoffman / IMC
      • Re: IETF58 - Network Status, Michael Richardson
      • RE: IETF58 - Network Status, bill
      • Re: IETF58 - Network Status, Andrew Partan
      • Re: IETF58 - Network Status, Theodore Ts'o
      • Re: IETF58 - Network Status, Roland Bless
      • Re: IETF58 - Network Status, Theodore Ts'o
      • Re: IETF58 - Network Status, shogunx
      • Re: IETF58 - Network Status, Roland Bless
      • Re: IETF58 - Network Status, shogunx
      • Re: IETF58 - Network Status, Michael Richardson
  • Re: IETF58 - Network Status, JORDI PALET MARTINEZ
  • Re: IETF58 - Network Status, Kevin C. Almeroth
    • Re: IETF58 - Network Status, JORDI PALET MARTINEZ
  • RE: IETF58 - Network Status, Romascanu, Dan (Dan)
    • Re: IETF58 - Network Status, Keith Moore
      • Re: IETF58 - Network Status, Bob Hinden
      • Re: IETF58 - Network Status, JORDI PALET MARTINEZ
      • Re: IETF58 - Network Status, Roland Bless
      • Re: IETF58 - Network Status, Ole J. Jacobsen
      • Re: IETF58 - Network Status, JORDI PALET MARTINEZ
      • Re: IETF58 - Network Status, Scott W Brim
      • Re: IETF58 - Network Status, JORDI PALET MARTINEZ
      • Re: IETF58 - Network Status, Keith Moore
      • Re: IETF58 - Network Status, Iljitsch van Beijnum
      • Re: IETF58 - Network Status, Steven M. Bellovin
      • Re: IETF58 - Network Status, Iljitsch van Beijnum
      • Re: IETF58 - Network Status, Joel Jaeggli
      • Re: IETF58 - Network Status, Eliot Lear
      • Re: IETF58 - Network Status, Daniel Senie
      • Re: IETF58 - Network Status, Iljitsch van Beijnum