IETF Discussion Archive - Thread Index

• Nomcom 2009-2010: IETF-76 Office hours, Mary Barnes
• Fwd: (Forward to attendees) Meeting invitation: Smart Grid IETF "Bar" BOF, Fred Baker
• IETF 76 Streaming, Sunday update..., Joel Jaeggli
• Update: Audio Streaming Info - IETF 76 November 8-13, 2009, Joel Jaeggli
• Global Telecom Companies Announce A Standards Based Solution For Voice And SMS Services Over LTE, Ingemar Johansson S
• RE: Last Call: draft-ietf-l3vpn-2547bis-mcast-bgp (BGP Encodings andProcedures for Multicast in MPLS/BGP IP VPNs) to Proposed Standard, Jie Dong
• Python IDIQ Development RFP, Ray Pelletier
• A session for resolving my DISCUSSes, Alexey Melnikov
  • Re: A session for resolving my DISCUSSes, Dave CROCKER
    • Re: A session for resolving my DISCUSSes, Lars Eggert
      • RE: A session for resolving my DISCUSSes, Romascanu, Dan (Dan)
      • Re: A session for resolving my DISCUSSes, Alexey Melnikov
      • Re: A session for resolving my DISCUSSes, Dave CROCKER
      • Re: A session for resolving my DISCUSSes, Dave CROCKER
• IDNAbis spec, Husni Al-Muhtaseb
  • Re: IDNAbis spec, Stephane Bortzmeyer
• Re: Sponsorship for FOSS developers (was: Re: [codec] *draft* agenda), Peter Saint-Andre
  • Re: Sponsorship for FOSS developers, Alexey Melnikov
• Circle of Fifths, Ole Jacobsen
  • Re: Circle of Fifths, JORDI PALET MARTINEZ
    • Re: Circle of Fifths, Ole Jacobsen
      • Re: Circle of Fifths, Paul Hoffman
      • Re: Circle of Fifths, Ole Jacobsen
      • Re: Circle of Fifths, Paul Hoffman
      • Re: funding the IETF, was Circle of Fifths, John Levine
      • Re: Circle of Fifths, Phillip Hallam-Baker
      • Re: Circle of Fifths, John Levine
      • Re: Circle of Fifths, Steve Crocker
      • Re: our pals at ICANN, was Circle of Fifths, John R. Levine
      • Re: our pals at ICANN, was Circle of Fifths, Steve Crocker
      • Re: our pals at ICANN, was Circle of Fifths, Bill Manning
      • Message not available
      • Re: Circle of Fifths, Steve Crocker
      • Re: Circle of Fifths, Doug Ewell
      • Re: Circle of Fifths, David Morris
      • Re: Circle of Fifths, joel jaeggli
    • Re: Circle of Fifths, Doug Barton
  • Re: Circle of Fifths, Dave CROCKER
• Re: Last Call: draft-ietf-sasl-gs2 (Using GSS-API Mechanisms in SASL: The GS2 Mechanism Family) to Proposed Standard, Alexey Melnikov
  • Re: Last Call: draft-ietf-sasl-gs2 (Using GSS-API Mechanisms in SASL: The GS2 Mechanism Family) to Proposed Standard, Simon Josefsson
• ISOC Panel at IETF 76 Registration Information, Greg Wood
• ISOC Panel at IETF 76 -- Internet Bandwidth Growth: Dealing with Reality, IETF Chair
• Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, Nikunj R. Mehta
  • Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, Julian Reschke
  • Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, Lisa Dusseault
    • Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, Nikunj R. Mehta
      • Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, Eliot Lear
      • Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, mike amundsen
      • Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, Scott Lawrence
  • <Possible follow-ups>
  • Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, SM
    • Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, Lisa Dusseault
      • Message not available
      • Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, SM
• Nomcom 2009-10: Request for additional TSV nominations, Mary Barnes
• Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, Julian Reschke
• Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard, IETF Member Dave Aronson
• Re: Last Call: draft-hammer-oauth (The OAuth Core 1.0 Protocol) to Informational RFC, Cullen Jennings
  • RE: Last Call: draft-hammer-oauth (The OAuth Core 1.0 Protocol) to Informational RFC, Eran Hammer-Lahav
    • Re: Last Call: draft-hammer-oauth (The OAuth Core 1.0 Protocol) to Informational RFC, Peter Saint-Andre
  • Re: Last Call: draft-hammer-oauth (The OAuth Core 1.0 Protocol) to Informational RFC, Stephan Wenger
• request for feedback: change to the ID boilerplate, Lars Eggert
  • RE: request for feedback: change to the ID boilerplate, Pasi.Eronen
  • Re: request for feedback: change to the ID boilerplate, Scott Lawrence
    • Re: request for feedback: change to the ID boilerplate, Lars Eggert
      • Re: request for feedback: change to the ID boilerplate, Lars Eggert
      • RE: request for feedback: change to the ID boilerplate, Pasi.Eronen
      • RE: request for feedback: change to the ID boilerplate, Eric Gray
  • Re: request for feedback: change to the ID boilerplate, Julian Reschke
    • Re: request for feedback: change to the ID boilerplate, Spencer Dawkins
      • Re: request for feedback: change to the ID boilerplate, Julian Reschke
  • Re: request for feedback: change to the ID boilerplate, Scott Brim
    • Re: request for feedback: change to the ID boilerplate, Lars Eggert
    • Re: request for feedback: change to the ID boilerplate, Spencer Dawkins
      • RE: request for feedback: change to the ID boilerplate, Eric Gray
      • Re: request for feedback: change to the ID boilerplate, Spencer Dawkins
      • RE: request for feedback: change to the ID boilerplate, Eric Gray
      • Re: request for feedback: change to the ID boilerplate, Spencer Dawkins
    • RE: request for feedback: change to the ID boilerplate, Eric Gray
  • Re: request for feedback: change to the ID boilerplate, Paul Hoffman
    • Re: request for feedback: change to the ID boilerplate, Dave CROCKER
  • Re: request for feedback: change to the ID boilerplate, SM
    • Re: request for feedback: change to the ID boilerplate, Lars Eggert
      • Re: request for feedback: change to the ID boilerplate, SM
  • <Possible follow-ups>
  • RE: request for feedback: change to the ID boilerplate, Alfred Hönes
    • Re: request for feedback: change to the ID boilerplate, Spencer Dawkins
• Audio setup for conferences WAS:RE: Audio Streaming Info - IETF 76 November 8-13, 2009, Mehmet Ersue
  • Re: Audio setup for conferences WAS:RE: Audio Streaming Info - IETF 76 November 8-13, 2009, joel jaeggli
• Audio Streaming Info - IETF 76 November 8-13, 2009, Joel Jaeggli
• NAT Not Needed To Make Renumbering Easy, Sabahattin Gucukoglu
  • Re: NAT Not Needed To Make Renumbering Easy, Masataka Ohta
  • Re: NAT Not Needed To Make Renumbering Easy, Andrew G. Malis
    • Re: NAT Not Needed To Make Renumbering Easy, Masataka Ohta
    • Re: NAT Not Needed To Make Renumbering Easy, Christian Vogt
      • Re: NAT Not Needed To Make Renumbering Easy, Sam Hartman
      • Re: NAT Not Needed To Make Renumbering Easy, Phillip Hallam-Baker
      • Re: NAT Not Needed To Make Renumbering Easy, Masataka Ohta
      • Re: NAT Not Needed To Make Renumbering Easy, Christian Vogt
      • Re: NAT Not Needed To Make Renumbering Easy, Phillip Hallam-Baker
      • Re: NAT Not Needed To Make Renumbering Easy, Sam Hartman
      • Re: NAT Not Needed To Make Renumbering Easy, Masataka Ohta
      • Re: NAT Not Needed To Make Renumbering Easy, Christian Vogt
      • Re: NAT Not Needed To Make Renumbering Easy, Masataka Ohta
      • Re: NAT Not Needed To Make Renumbering Easy, Christian Vogt
  • Re: NAT Not Needed To Make Renumbering Easy, AJ Jaghori
  • Re: NAT Not Needed To Make Renumbering Easy, Dean Willis
    • RE: NAT Not Needed To Make Renumbering Easy, Greg Daley
      • Re: NAT Not Needed To Make Renumbering Easy, Brian E Carpenter
  • <Possible follow-ups>
  • Re: NAT Not Needed To Make Renumbering Easy, Noel Chiappa
    • Re: NAT Not Needed To Make Renumbering Easy, Sabahattin Gucukoglu
  • Re: NAT Not Needed To Make Renumbering Easy, Noel Chiappa
• Request for comments on proposed changes to the IETF Trust Legal Provisions (TLP), Marshall Eubanks
• draft-nottingham-site-meta: put key bit (/.well-known/) in the abstract, Dan Connolly
• draft-nottingham-site-meta: registration too slow, opaque, Dan Connolly
  • Re: draft-nottingham-site-meta: registration too slow, opaque, Nicolas Williams
  • Re: draft-nottingham-site-meta: registration too slow, opaque, Mark Nottingham
  • Re: draft-nottingham-site-meta: registration too slow, opaque, Mark Nottingham
• Gen-ART Review of draft-ietf-dhc-vpn-option-11.txt, Spencer Dawkins
  • Re: Gen-ART Review of draft-ietf-dhc-vpn-option-11.txt, Kim Kinnear
• Gen-ART review of draft-ietf-geopriv-lis-discovery-11, Spencer Dawkins
• Gen-ART LC Review of draft-ietf-l3vpn-e2e-rsvp-te-reqts-04, Ben Campbell
• Review of draft-ietf-dna-simple-09, Bernard Aboba
  • Re: Review of draft-ietf-dna-simple-09, Suresh Krishnan
    • RE: Review of draft-ietf-dna-simple-09, Bernard Aboba
• draft-ietf-geopriv-held-identity-extensions-00, Donald Eastlake
• Review of draft-ietf-idnabis-tables, Bernard Aboba
  • Re: Review of draft-ietf-idnabis-tables, Patrik Fältström
• Review of draft-ietf-idnabis-defs, Bernard Aboba
• Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard], Ted Hardie
  • Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard], Marc Petit-Huguenin
    • Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard], Ted Hardie
      • Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard], Marc Petit-Huguenin
      • Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard], Ted Hardie
      • Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard], Marc Petit-Huguenin
      • Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard], Andrew Newton
      • Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard], Marc Petit-Huguenin
      • Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard], Andrew Newton
      • Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard], Marc Petit-Huguenin
  • RE: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri(Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers)to Proposed Standard], Dan Wing
    • Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri(Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers)to Proposed Standard], Ted Hardie
• SECDIR and OPSDIR review of draft-ietf-dhc-vpn-option-11, David Harrington
• spd for tunnel, Naveen BN
• spd tunnel mode, Naveen BN
• Re: Last Call: draft-gennai-smime-cnipa-pec (Certified Electrinic Mail) to Proposed Standard, Alfred Hönes
• RFC Production Center and RFC Publisher Contracts Awarded, Ray Pelletier
• Re: Last Call: draft-gennai-smime-cnipa-pec (Certified Electronic Mail) to Proposed Standard, Simon Josefsson
  • Re: Last Call: draft-gennai-smime-cnipa-pec (Certified Electronic Mail) to Proposed Standard, Steven Bellovin
  • <Possible follow-ups>
  • Re: Last Call: draft-gennai-smime-cnipa-pec (Certified Electronic Mail) to Proposed Standard, SM
• Gen-ART LC Review of draft-ietf-idnabis-rationale-13, Ben Campbell
  • Re: Gen-ART LC Review of draft-ietf-idnabis-rationale-13, Vint Cerf
• Re: Last Call: draft-gennai-smime-cnipa-pec (Certified Electronic Mail) to Proposed Standard, John C Klensin
  • Re: Last Call: draft-gennai-smime-cnipa-pec (Certified Electronic Mail) to Proposed Standard, SM
    • Re: Last Call: draft-gennai-smime-cnipa-pec (Certified Electronic Mail) to Proposed Standard, John C Klensin
      • Re: Last Call: draft-gennai-smime-cnipa-pec (Certified Electronic Mail) to Proposed Standard, SM
      • Re: Last Call: draft-gennai-smime-cnipa-pec (Certified Electronic Mail) to Proposed Standard, Sam Hartman
• Requesting a Non Smoking Room at the IETF 76 Overflow Properties, Alexa Morris
  • Re: [76all] Requesting a Non Smoking Room at the IETF 76 Overflow Properties, Sorin Faibish
• FW: [IP] AMA -- H1N1 CrRapidly; Predominantly Affects Young Patientsitical Illness Can Occur, Richard Shockey
• Re: Last Call: draft-ietf-idnabis-protocol (Internationalized Domain Names in Applications (IDNA): Protocol) to Proposed Standard, SM
• Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Noel Chiappa
  • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
    • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Theodore Tso
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
    • Re: Legality of IETF meetings in PRC. Was: Re: Request for communityguidance on issue concerning a future meeting of the IETF, Doug Ewell
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Stephan Wenger
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Michael StJohns
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Dave CROCKER
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Doug Barton
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Michael StJohns
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Eliot Lear
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Stephan Wenger
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Doug Ewell
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Doug Ewell
    • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, SM
• RE: [mpls] Last Call: draft-ietf-mpls-tp-oam-requirements,> (Requirementsfor OAM in MPLS Transport Networks) to Proposed Standard, Huub van Helvoort
  • RE: [mpls] Last Call: draft-ietf-mpls-tp-oam-requirements,> (Requirementsfor OAM in MPLS Transport Networks) to Proposed Standard, Yaakov Stein
    • Re: [mpls] Last Call: draft-ietf-mpls-tp-oam-requirements,> (Requirementsfor OAM in MPLS Transport Networks) to Proposed Standard, Huub van Helvoort
    • RE: [mpls] Last Call: draft-ietf-mpls-tp-oam-requirements, >(Requirementsfor OAM in MPLS Transport Networks) to Proposed Standard, Maarten Vissers
• Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, Noel Chiappa
  • RE: Legality of IETF meetings in PRC. Was: Re: Request for communityguidance on issue concerning a future meeting of the IETF, HUANG, ZHIHUI (JERRY), ATTLABS
  • Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF, John C Klensin
• Support for publication of draft-housley-iesg-3932bis, Sam Hartman
• Re: I-D Action:draft-davies-dtnrg-uri-find-00.txt, Bill McQuillan
• One more take on rfc3932bis, Alfred Hönes
• RE: Last Call: draft-ietf-l3vpn-e2e-rsvp-te-reqts (Requirements forsupporting Customer RSVP and RSVP-TE over a BGP/MPLS IP-VPN) toInformational RFC, julien.meuric
• Re: Last Call: draft-ietf-mpls-tp-oam-requirements (RequirementsforOAMin MPLS Transport Networks) to Proposed Standard, ruiquan . jing
• Re: [CHANNEL-BINDING] Last Call: draft-altman-tls-channel-bindings (Channel Bindings for TLS) to Proposed Standard, Simon Josefsson
  • Re: [CHANNEL-BINDING] Last Call: draft-altman-tls-channel-bindings (Channel Bindings for TLS) to Proposed Standard, Nicolas Williams
• The IETF and the SmartGrid, Richard Shockey
  • Re: The IETF and the SmartGrid, Fred Baker
    • Re: The IETF and the SmartGrid, Peny Yang
      • Re: The IETF and the SmartGrid, Fred Baker
      • Message not available
      • Re: The IETF and the SmartGrid, Cyrus Daboo
  • Re: The IETF and the SmartGrid, Michael Dillon
    • RE: The IETF and the SmartGrid, Richard Shockey
    • Re: The IETF and the SmartGrid, Hiroshi Esaki
      • RE: The IETF and the SmartGrid, Richard Shockey
  • Re: The IETF and the SmartGrid, Brian E Carpenter
    • Re: The IETF and the SmartGrid, Dave CROCKER
  • Re: The IETF and the SmartGrid, Peter Dambier
  • <Possible follow-ups>
  • The IETF and the SmartGrid, Richard Shockey
• Re: [mpls] Last Call: draft-ietf-mpls-tp-oam-requirements (Requirements for OAM in MPLS Transport Networks) to Proposed Standard, Yoshinori KOIKE
• Re: Last Call: draft-ietf-mpls-tp-oam-requirements (Requirements for OAMin MPLS Transport Networks) to Proposed Standard, Sadler, Jonathan B.
  • Re: Last Call: draft-ietf-mpls-tp-oam-requirements (Requirements for OAMin MPLS Transport Networks) to Proposed Standard, Stewart Bryant
  • Re: Last Call: draft-ietf-mpls-tp-oam-requirements (Requirementsfor OAMin MPLS Transport Networks) to Proposed Standard, Adrian Farrel
  • <Possible follow-ups>
  • Fwd: Re: Last Call: draft-ietf-mpls-tp-oam-requirements (Requirements for OAMin MPLS Transport Networks) to Proposed Standard, ruiquan . jing
  • Re: Last Call: draft-ietf-mpls-tp-oam-requirements (Requirements for OAMin MPLS Transport Networks) to Proposed Standard, Loa Andersson
• RE: [mpls] Last Call: draft-ietf-mpls-tp-oam-requirements (Requirementsfor OAM in MPLS Transport Networks) to Proposed Standard, Rui Costa
  • RE: [mpls] Last Call: draft-ietf-mpls-tp-oam-requirements (Requirementsfor OAM in MPLS Transport Networks) to Proposed Standard, Yaakov Stein
    • Re: [mpls] Last Call: draft-ietf-mpls-tp-oam-requirements (Requirementsfor OAM in MPLS Transport Networks) to Proposed Standard, Francesco Fondelli
      • RE: [mpls] Last Call: draft-ietf-mpls-tp-oam-requirements (Requirementsfor OAM in MPLS Transport Networks) to Proposed Standard, Yaakov Stein
    • RE: [mpls] Last Call: draft-ietf-mpls-tp-oam-requirements (Requirementsfor OAM in MPLS Transport Networks) to Proposed Standard, Rui Costa
• Review of draft-ietf-dime-diameter-cmd-iana, Bernard Aboba
• Results of Venue Contract Survey, Bob Hinden
• Re: Local Beijing people response - RE: Request for community guidance on issue concerning a future meeting of the IETF, Noel Chiappa
  • Re: Local Beijing people response - RE: Request for community guidance on issue concerning a future meeting of the IETF, John C Klensin
    • Re: Local Beijing people response - RE: Request for community guidance on issue concerning a future meeting of the IETF, Dean Willis
  • Re: Local Beijing people response - RE: Request for community guidance on issue concerning a future meeting of the IETF, Dean Willis
• Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC, Samuel Weiler
• Update on IETF 76 ANA Hotel Availability, Alexa Morris
  • Re: Update on IETF 76 ANA Hotel Availability, Ben Campbell
    • Re: Update on IETF 76 ANA Hotel Availability, Alexa Morris
• Re: Local Beijing people response - RE: Request for community guidance on issue concerning a future meeting of the IETF, Bernard Aboba
  • Re: Local Beijing people response - RE: Request for community guidance on issue concerning a future meeting of the IETF, David Morris
• Re: Last Call: draft-ietf-idnabis-bidi (Right-to-left scripts for IDNA) to Draft Standard, Simon Josefsson
  • Re: Last Call: draft-ietf-idnabis-bidi (Right-to-left scripts for IDNA) to Draft Standard, Lisa Dusseault
    • Message not available
      • Re: Last Call: draft-ietf-idnabis-bidi (Right-to-left scripts for IDNA) to Draft Standard, SM
    • Re: Last Call: draft-ietf-idnabis-bidi (Right-to-left scripts for IDNA) to Draft Standard, Simon Josefsson
• Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Brian E Carpenter
  • <Possible follow-ups>
  • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, John C Klensin
    • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Russ Housley
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Dave CROCKER
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Stephen Kent
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, SM
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, ned+ietf
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Stephen Kent
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, SM
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Stephen Kent
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Jari Arkko
      • Message not available
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Russ Housley
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Brian E Carpenter
      • Message not available
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Robert Elz
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Jari Arkko
    • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Jari Arkko
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Dave CROCKER
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Jari Arkko
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Sam Hartman
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, John Leslie
      • Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt, Lars Eggert
• Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC, Ted Hardie
  • Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC, Russ Housley
    • Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC, Eliot Lear
    • Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC, Ted Hardie
      • Re: Last Call: draft-weiler-rsync-uri (The rsync URI Scheme) to Informational RFC, Paul Hoffman
• Application referrals - GROBJ, Dan Wing
• Input about possible reclassification of COPS-PR and SPPI to Historic, Romascanu, Dan (Dan)
• 10th TAHI IPv6 Interoperability test event, Yukiyo Akisada
• New IETF Journal available now (Volume 5, Issue 2), Mirjam Kuehne
• IAOC Member Selection, The IESG
  • Message not available
    • Message not available
      • Message not available
      • RE: IAOC Member Selection, Russ Housley
• TSVDIR review of draft-ietf-mipshop-pfmipv6-09.txt, Joe Touch
  • RE: TSVDIR review of draft-ietf-mipshop-pfmipv6-09.txt, Koodli, Rajeev
  • Message not available
    • Re: TSVDIR review of draft-ietf-mipshop-pfmipv6-09.txt, Hidetoshi Yokota
• Entirely new topic: Ten days in Japan!, Ole Jacobsen
• Regarding Internet Connectivity for the proposed IETF Meeting in China, David Morris
  • Re: Regarding Internet Connectivity for the proposed IETF Meeting in China, Scott Brim
  • Re: Regarding Internet Connectivity for the proposed IETF Meeting in China, Simon Josefsson
• One level up on the IAOC decision in re: China., Ted Hardie
  • Re: One level up on the IAOC decision in re: China., Dave CROCKER
    • RE: One level up on the IAOC decision in re: China., Glen Zorn
  • Re: One level up on the IAOC decision in re: China., Bill Manning
    • Re: One level up on the IAOC decision in re: China., Ted Hardie
    • Re: One level up on the IAOC decision in re: China., Arnt Gulbrandsen
      • Re: One level up on the IAOC decision in re: China., Peter Saint-Andre
      • Re: One level up on the IAOC decision in re: China., Dave CROCKER
      • RE: One level up on the IAOC decision in re: China., HUANG, ZHIHUI (JERRY), ATTLABS
      • Re: One level up on the IAOC decision in re: China., Dave CROCKER
      • Re: One level up on the IAOC decision in re: China., James M. Polk
      • Re: One level up on the IAOC decision in re: China., Marshall Eubanks
• RFID Test Class, psuger
  • Re: RFID Test Class, Todd Glassey
• Gen-ART LC Review of draft-ietf-sasl-scram-07, Ben Campbell
  • Re: Gen-ART LC Review of draft-ietf-sasl-scram-07, Alexey Melnikov
    • Re: Gen-ART LC Review of draft-ietf-sasl-scram-07, Nicolas Williams
      • Re: Gen-ART LC Review of draft-ietf-sasl-scram-07, Nicolas Williams
      • Re: Gen-ART LC Review of draft-ietf-sasl-scram-07, Alexey Melnikov
  • Re: Gen-ART LC Review of draft-ietf-sasl-scram-07, Alexey Melnikov
    • Re: Gen-ART LC Review of draft-ietf-sasl-scram-07, Ben Campbell
  • Re: Gen-ART LC Review of draft-ietf-sasl-scram-07, Nicolas Williams
    • Re: Gen-ART LC Review of draft-ietf-sasl-scram-07, Alexey Melnikov
  • Gen-ART Telechat Review of draft-ietf-sasl-scram-10, Ben Campbell
    • Re: Gen-ART Telechat Review of draft-ietf-sasl-scram-10, Simon Josefsson
      • Re: Gen-ART Telechat Review of draft-ietf-sasl-scram-10, Ben Campbell
      • Re: Gen-ART Telechat Review of draft-ietf-sasl-scram-10, Nicolas Williams
• Hiroshima IETF Codesprint, IETF Chair
• Re: Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer Security (TLS) Extensions: Extension Definitions) to Proposed Standard, Simon Josefsson
  • Message not available
    • Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer Security (TLS) Extensions: Extension Definitions) to Proposed Standard, Eric Rescorla
  • RE: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer Security (TLS) Extensions: Extension Definitions) to Proposed Standard, Pasi.Eronen
    • Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer Security (TLS) Extensions: Extension Definitions) to Proposed Standard, Peter Sylvester
  • Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer, Martin Rex
    • Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer, Michael D'Errico
      • Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer, Martin Rex
      • Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer, Michael D'Errico
      • RE: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer, Joseph Salowey (jsalowey)
      • Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer, Simon Josefsson
      • RE: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer, Joseph Salowey (jsalowey)
      • Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer, Peter Saint-Andre
      • Re: [TLS] Last Call: draft-ietf-tls-rfc4366-bis (Transport Layer, Blumenthal, Uri
• GenArt Telechat Review of draft-ietf-pkix-other-certs-05, Ben Campbell
  • Re: GenArt Telechat Review of draft-ietf-pkix-other-certs-05, Stephen Farrell
    • Re: GenArt Telechat Review of draft-ietf-pkix-other-certs-05, Ben Campbell
• RE: [mpls] Last Call: draft-ietf-mpls-tp-nm-req (MPLS TP Network Management Requirements) to Proposed Standard, Shahram Davari
  • RE: [mpls] Last Call: draft-ietf-mpls-tp-nm-req (MPLS TP Network Management Requirements) to Proposed Standard, benjamin.niven-jenkins
    • RE: [mpls] Last Call: draft-ietf-mpls-tp-nm-req (MPLS TP Network Management Requirements) to Proposed Standard, Shahram Davari
• Proposed (updated) ARF WG charter, Murray S. Kucherawy
• RE: [rohc] Last Call: draft-ietf-rohc-ikev2-extensions-hcoipsec (IKEv2 Extensions to Support Robust Header Compression over IPsec (ROHCoIPsec)) to Proposed Standard, Emre Ertekin
• RE: Last Call: draft-ietf-rohc-ipsec-extensions-hcoipsec (IPsec Extensions to Support Robust Header Compression over IPsec (ROHCoIPsec)) to Proposed Standard, Emre Ertekin
  • RE: Last Call: draft-ietf-rohc-ipsec-extensions-hcoipsec (IPsec Extensions to Support Robust Header Compression over IPsec (ROHCoIPsec)) to Proposed Standard, Robert Stangarone
• RE: Last call comments for ROHCoIPsec: draft-ietf-rohc-hcoipsec, draft-ietf-rohc-ikev2-extensions-hcoipsec, draft-ietf-rohc-ipsec-extensions-hcoipsec, Emre Ertekin
  • RE: Last call comments for ROHCoIPsec: draft-ietf-rohc-hcoipsec, draft-ietf-rohc-ikev2-extensions-hcoipsec, draft-ietf-rohc-ipsec-extensions-hcoipsec, Pasi.Eronen
    • Re: Last call comments for ROHCoIPsec: draft-ietf-rohc-hcoipsec, draft-ietf-rohc-ikev2-extensions-hcoipsec, draft-ietf-rohc-ipsec-extensions-hcoipsec, Carsten Bormann
      • RE: Last call comments for ROHCoIPsec: draft-ietf-rohc-hcoipsec, draft-ietf-rohc-ikev2-extensions-hcoipsec, draft-ietf-rohc-ipsec-extensions-hcoipsec, Pasi.Eronen
      • Re: Last call comments for ROHCoIPsec: draft-ietf-rohc-hcoipsec, draft-ietf-rohc-ikev2-extensions-hcoipsec, draft-ietf-rohc-ipsec-extensions-hcoipsec, Emre Ertekin
      • RE: [rohc] Last call comments for ROHCoIPsec: draft-ietf-rohc-hcoipsec, draft-ietf-rohc-ikev2-extensions-hcoipsec, draft-ietf-rohc-ipsec-extensions-hcoipsec, Pasi.Eronen
    • Re: Last call comments for ROHCoIPsec: draft-ietf-rohc-hcoipsec, draft-ietf-rohc-ikev2-extensions-hcoipsec, draft-ietf-rohc-ipsec-extensions-hcoipsec, Emre Ertekin
• FW: Last Call: draft-ietf-rohc-ipsec-extensions-hcoipsec (IPsec Extensions to Support Robust Header Compression over IPsec (ROHCoIPsec)) to Proposed Standard, Robert Stangarone
• FW: [rohc] Last Call: draft-ietf-rohc-ikev2-extensions-hcoipsec (IKEv2 Extensions to Support Robust Header Compression over IPsec (ROHCoIPsec)) to Proposed Standard, Robert Stangarone
• FW: [rohc] Last Call: draft-ietf-rohc-hcoipsec (Integration of Robust Header Compression (ROHC) over IPsec Security Associations) to Informational RFC, Robert Stangarone
• Re: [IAOC] Request for community guidance on issue concerning a future meeting of the IETF, Noel Chiappa
  • RE: [IAOC] Request for community guidance on issue concerning afuture meeting of the IETF, HUANG, ZHIHUI (JERRY), ATTLABS
• Re: Request for community guidance on issue concerning afuture mee ting of the IETF, Soininen, Jonne (NSN - FI/Espoo)
  • Message not available
    • Re: Request for community guidance on issue concerning afuture mee ting of the IETF, Tim Chown
• Revision 3, SM
• Re: China venue survey, Yaron Sheffer
  • Re: China venue survey, Ole Jacobsen
    • RE: China venue survey, Yaron Sheffer
      • RE: China venue survey, Ole Jacobsen
      • RE: China venue survey, James M. Polk
      • Re: China venue survey, Peter Saint-Andre
      • RE: China venue survey, HUANG, ZHIHUI (JERRY), ATTLABS
      • Re: China venue survey, Melinda Shore
      • RE: China venue survey, Ole Jacobsen
      • RE: China venue survey, Scott Kitterman
      • Re: China venue survey, Dave Cridland
      • Re: China venue survey, James M. Polk
      • Re: China venue survey, Peter Saint-Andre
      • Re: China venue survey, Dean Willis
      • Re: China venue survey, Dave Cridland
      • Re: China venue survey, Ben Campbell
      • Re: China venue survey, Ole Jacobsen
      • Re: China venue survey, Dave CROCKER
      • Re: China venue survey, Ben Campbell
      • Re: China venue survey, Marshall Eubanks
      • Re: China venue survey, Cullen Jennings
      • Re: China venue survey, Ole Jacobsen
      • Re: China venue survey, Melinda Shore
      • Re: China venue survey, Ole Jacobsen
      • Re: China venue survey, Peter Saint-Andre
      • Re: China venue survey, Ole Jacobsen
      • Re: China venue survey, Marshall Eubanks
      • Re: China venue survey, JORDI PALET MARTINEZ
      • Re: China venue survey, James M. Polk
• RE: Request for community guidance on issue concerning a future me etingof the IETF, Soininen, Jonne (NSN - FI/Espoo)
• Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Noel Chiappa
• Re: [IAOC] [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Noel Chiappa
• Request for community guidance on issue concerning a future meeting of the IETF, Marshall Eubanks
  • Re: Request for community guidance on issue concerning a future meeting of the IETF, Tim Bray
    • Re: Request for community guidance on issue concerning a future meeting of the IETF, Peter Saint-Andre
    • Re: Request for community guidance on issue concerning a future meeting of the IETF, Eric Rescorla
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Eric Rescorla
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Message not available
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Tim Chown
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Adam Roach
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Ray Pelletier
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Pete Resnick
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Eric Rescorla
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Dave CROCKER
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Eric Rescorla
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Eric Rescorla
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Eric Rescorla
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Marshall Eubanks
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Theodore Tso
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Jari Arkko
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Theodore Tso
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Peter Saint-Andre
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Michael StJohns
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Wes Hardaker
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Dean Willis
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Dave CROCKER
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Request for community guidance on issue concerning a futuremeeting of the IETF, Doug Ewell
      • Re: Request for community guidance on issue concerning a futuremeeting of the IETF, Ole Jacobsen
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Dean Willis
      • Message not available
      • Re: Request for community guidance on issue concerning a futuremeeting of the IETF, Health
      • Re: Request for community guidance on issue concerning a futuremeeting of the IETF, Dean Willis
      • Message not available
      • Re: Request for community guidance on issue concerning afuturemeeting of the IETF, Health
      • Re: Request for community guidance on issue concerning afuturemeeting of the IETF, Dean Willis
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Scott Brim
  • Re: Request for community guidance on issue concerning a future meeting of the IETF, Matt Crawford
    • Re: Request for community guidance on issue concerning a future meeting of the IETF, Steven M. Bellovin
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, John C Klensin
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Jari Arkko
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Rich Kulawiec
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Lindqvist Kurt Erik
  • Re: Request for community guidance on issue concerning a future meeting of the IETF, Scott Brim
    • Re: Request for community guidance on issue concerning a future meeting of the IETF, Marshall Eubanks
  • Re: Request for community guidance on issue concerning a future meeting of the IETF, Ben Campbell
    • Re: Request for community guidance on issue concerning a future meeting of the IETF, Dean Willis
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Enrico Marocco
    • Re: Request for community guidance on issue concerning a future meeting of the IETF, Dean Willis
  • Re: Request for community guidance on issue concerning a future meeting of the IETF, Carsten Bormann
    • Re: Request for community guidance on issue concerning a future meeting of the IETF, Eric Burger
      • Visas and Costs, Ole Jacobsen
      • Re: Visas and Costs, John C Klensin
      • RE: Visas and Costs, HUANG, ZHIHUI (JERRY), ATTLABS
      • Re: Visas and Costs, Andrew G. Malis
      • RE: Visas and Costs, HUANG, ZHIHUI (JERRY), ATTLABS
      • RE: Visas and Costs, John C Klensin
      • RE: Visas and Costs, HUANG, ZHIHUI (JERRY), ATTLABS
      • RE: Visas and Costs, Glen Zorn
      • RE: Visas and Costs, Ross Callon
      • Re: Visas and Costs, Ray Pelletier
      • Re: Visas and Costs, Brian E Carpenter
      • RE: Visas and Costs, Ole Jacobsen
      • Re: Visas and Costs, Michael Richardson
      • Re: Visas and Costs, Stefan Winter
      • Re: Visas and Costs, John C Klensin
      • RE: Request for community guidance on issue concerning a future meeting of the IETF, Stephane H Maes
    • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, John C Klensin
      • Re: [IAOC] [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Paul Wouters
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Andrew Sullivan
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, John C Klensin
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Pete Resnick
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Henk Uijterwaal
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Scott Kitterman
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, John Levine
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Scott Kitterman
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Adam Roach
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Stephen Farrell
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Peter Saint-Andre
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Dave Cridland
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Dean Willis
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Dean Willis
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Peter Saint-Andre
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Peter Saint-Andre
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Dave Cridland
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Adam Roach
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Scott Brim
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Henk Uijterwaal
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Melinda Shore
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Tim Bray
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Scott Brim
      • Re: [IAOC] [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Fred Baker
      • Re: [IAOC] [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Brian E Carpenter
      • Re: [IAOC] [IAB] Request for community guidance on issue concerning a future meeting of the IETF, Marshall Eubanks
      • Re: [IAB] Request for community guidance on issue concerning a future meeting of the IETF, John C Klensin
  • Re: Request for community guidance on issue concerning a future meeting of the IETF, Peter Saint-Andre
  • Re: Request for community guidance on issue concerning a future meeting of the IETF, Dave CROCKER
  • Re: Request for community guidance on issue concerning a future meeting of the IETF, Alan DeKok
    • Re: Request for community guidance on issue concerning a future meeting of the IETF, Eric Burger
  • RE: Request for community guidance on issue concerning a future meeting of the IETF, Ross Callon
    • RE: Request for community guidance on issue concerning a future meeting of the IETF, Rahul Aggarwal
    • Re: Request for community guidance on issue concerning a future meeting of the IETF, John G. Scudder
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Adam Roach
    • RE: Request for community guidance on issue concerning a future meeting of the IETF, Bernard Aboba
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Gene Gaines
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Marshall Eubanks
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Peter Saint-Andre
      • RE: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Robert Elz
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Theodore Tso
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Ole Jacobsen
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Dave CROCKER
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Steve Crocker
      • RE: Request for community guidance on issue concerning a future meeting of the IETF, Roni Even
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Melinda Shore
      • RE: Request for community guidance on issue concerning a future meeting of the IETF, Roni Even
      • RE: Request for community guidance on issue concerning a future meeting of the IETF, Richard Golodner
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Adrian Farrel
      • Re: [IAOC] Request for community guidance on issue concerning a future meeting of the IETF, Marshall Eubanks
      • RE: [IAOC] Request for community guidance on issue concerning a future meeting of the IETF, Eran Hammer-Lahav
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Eric Rescorla
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Simon Perreault
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Michael StJohns
      • Message not available
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Steve Crocker
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Michael StJohns
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Olaf Kolkman
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Dave CROCKER
      • Re: Request for community guidance on issue concerning a future meeting of the IETF, Michael StJohns
      • Message not available
      • Re: Request for community guidance on issue concerninga future meeting of the IETF, Health
      • Re: Request for community guidance on issue concerninga future meeting of the IETF, Joel Jaeggli