IETF Discussion Archive - Thread Index

• Re: Our deadlines are dizzyingly complex and confusing, (continued)
  • Re: Our deadlines are dizzyingly complex and confusing, Spencer Dawkins
    • Re: Our deadlines are dizzyingly complex and confusing, Joel Jaeggli
      • Re: Our deadlines are dizzyingly complex and confusing, Spencer Dawkins
      • Re: Our deadlines are dizzyingly complex and confusing, Lakshminath Dondeti
      • Re: Our deadlines are dizzyingly complex and confusing, Eric Rescorla
      • Re: Our deadlines are dizzyingly complex and confusing, Lakshminath Dondeti
      • Re: Our deadlines are dizzyingly complex and confusing, Henrik Levkowetz
      • Re: Our deadlines are dizzyingly complex and confusing, Lars Eggert
      • Re: Our deadlines are dizzyingly complex and confusing, Tony Li
      • Re: Our deadlines are dizzyingly complex and confusing, Lakshminath Dondeti
      • RE: Our deadlines are dizzyingly complex and confusing, Hallam-Baker, Phillip
      • Re: Our deadlines are dizzyingly complex and confusing, Jari Arkko
  • Re: Our deadlines are dizzyingly complex and confusing, Noel Chiappa
    • Re: Our deadlines are dizzyingly complex and confusing, Spencer Dawkins
    • Re: Our deadlines are dizzyingly complex and confusing, Jari Arkko
• TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Bernard Aboba
  • Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Iljitsch van Beijnum
    • Re: [tsv-dir] Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Bernard_Aboba
  • Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Bernard Aboba
    • Message not available
      • Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Bernard Aboba
      • Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Iljitsch van Beijnum
      • Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Bernard Aboba
• Re: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard, Cullen Jennings
  • Re: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard, Andrew Newton
    • Re: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard, Lisa Dusseault
  • Message not available
    • Re: Fwd: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard, Erik Wilde
• Gen-art review of draft-ietf-l2vpn-vpls-bridge-interop-02.txt, Elwyn Davies
• draft-van-beijnum-multi-mtu-01.txt, Iljitsch van Beijnum
• Gen-ART review of draft-ietf-sipping-toip-08.txt, Suresh Krishnan
  • <Possible follow-ups>
  • RE: Gen-ART review of draft-ietf-sipping-toip-08.txt, Guido Gybels
  • RE: Gen-ART review of draft-ietf-sipping-toip-08.txt, Guido Gybels
• Re: Last Call: draft-sjdcox-cgi-urn (A URN namespace for the Commission for the Management and Application of Geoscience Information (CGI)) to Informational RFC, Tom.Petch
• Fw: Last Call: draft-evain-ebu-urn (A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU)) to Informational RFC, Tom.Petch
• Gen-ART review of draft-cheshire-ipv4-acd-05.txt, Spencer Dawkins
  • Re: Gen-ART review of draft-cheshire-ipv4-acd-05.txt, Spencer Dawkins
  • Re: Gen-ART review of draft-cheshire-ipv4-acd-05.txt, C. M. Heard
• Gen-ART review of draft-evain-ebu-urn-01.txt, Black_David
  • RE : Gen-ART review of draft-evain-ebu-urn-01.txt, Evain, Jean-Pierre
• SAFE BoF in Vancouver, Colin Perkins
  • Re: SAFE BoF in Vancouver, Ted Hardie
    • Re: SAFE BoF in Vancouver, Colin Perkins
      • Re: SAFE BoF in Vancouver, Ted Hardie
      • Re: SAFE BoF in Vancouver, James M. Polk
      • Re: SAFE BoF in Vancouver, Ted Hardie
      • Re: SAFE BoF in Vancouver, Colin Perkins
    • RE: SAFE BoF in Vancouver, Markus.Isomaki
• Note on submitting non -00 drafts automatically, Philip Matthews
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Hallam-Baker, Phillip
• NAT+PT for IPv6 Transition & Operator Feedback generally, RJ Atkinson
  • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Iljitsch van Beijnum
    • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Lucy Lynch
      • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Iljitsch van Beijnum
    • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Marc Manthey
      • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Iljitsch van Beijnum
  • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Jari Arkko
  • RE: NAT+PT for IPv6 Transition & Operator Feedback generally, Hallam-Baker, Phillip
  • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Francis Dupont
  • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, David Kessens
    • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Iljitsch van Beijnum
      • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, RJ Atkinson
      • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, David Kessens
      • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Sam Hartman
    • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Spencer Dawkins
    • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, RJ Atkinson
  • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Eliot Lear
  • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Brian E Carpenter
    • Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Iljitsch van Beijnum
• terminology proposal: NAT+PT, RJ Atkinson
  • Re: terminology proposal: NAT+PT (or NAT64 ?), Rémi Després
    • Re: terminology proposal: NAT+PT (or NAT64 ?), Keith Moore
      • RE: terminology proposal: NAT+PT (or NAT64 ?), Hallam-Baker, Phillip
      • Re: terminology proposal: NAT+PT (or NAT64 ?), Rémi Després
      • Re: terminology proposal: NAT+PT (or NAT64 ?), Keith Moore
      • Re: terminology proposal: NAT+PT (or NAT64 ?), Rémi Després
      • Re: terminology proposal: NAT+PT (or NAT64 ?), Keith Moore
      • Re: terminology proposal: NAT+PT (or NAT64 ?), Rémi Després
      • Re: terminology proposal: NAT+PT (or NAT64 ?), Keith Moore
      • Re: terminology proposal: NAT+PT (or NAT64 ?), Iljitsch van Beijnum
      • Re: terminology proposal: NAT+PT (or NAT64 ?), Keith Moore
      • Re: terminology proposal: NAT+PT (or NAT64 ?), Pekka Savola
      • Re: terminology proposal: NAT+PT (or NAT64 ?), Stephen Sprunk
      • Re: terminology proposal: NAT+PT (or NAT64 ?), Keith Moore
  • Re: terminology proposal: NAT+PT, Harald Tveit Alvestrand
  • Re: terminology proposal: NAT+PT, Stephen Sprunk
  • Re: terminology proposal: NAT+PT, Keith Moore
    • RE: terminology proposal: NAT+PT, Sheng Jiang
• Reject the "experimental" TLS authorization proposal, Ben Caplan
• FW: I-D Action:draft-narten-ipv6-statement-00.txt, JORDI PALET MARTINEZ
  • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Thomas Narten
    • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Pars Mutaf
    • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Mohsen Souissi
      • Re: I-D Action:draft-narten-ipv6-statement-00.txt, Iljitsch van Beijnum
    • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Tom.Petch
      • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Eliot Lear
      • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Thomas Narten
      • RE: FW: I-D Action:draft-narten-ipv6-statement-00.txt, michael.dillon
      • NAT-PT (Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt), Harald Alvestrand
      • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Tom.Petch
      • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Jari Arkko
      • RE: FW: I-D Action:draft-narten-ipv6-statement-00.txt, michael.dillon
      • Re: I-D Action:draft-narten-ipv6-statement-00.txt, Iljitsch van Beijnum
      • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Jari Arkko
    • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Greg Skinner
    • Africa and IPv6, philemon
      • Re: Africa and IPv6, JORDI PALET MARTINEZ
      • Message not available
      • Fwd: Africa and IPv6, rajesh rajesh
      • Fwd: Africa and IPv6, Marc Manthey
      • Re: Africa and IPv6, SM
      • Re: Africa and IPv6, philemon
  • <Possible follow-ups>
  • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Noel Chiappa
    • Re: I-D Action:draft-narten-ipv6-statement-00.txt, Iljitsch van Beijnum
  • Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Noel Chiappa
    • Re: I-D Action:draft-narten-ipv6-statement-00.txt, JORDI PALET MARTINEZ
      • Re: I-D Action:draft-narten-ipv6-statement-00.txt, Sam Hartman
      • Re: I-D Action:draft-narten-ipv6-statement-00.txt, JORDI PALET MARTINEZ
• secdir review of draft-ietf-l2vpn-vpls-mcast-reqts-05.txt, Stephen Hanna
• RE: [Sipping] Last Call: draft-ietf-sipping-service-examples (Ses sion Initiation Protocol Service Examples) to BCP, Hutton, Andrew
• RE: [Sipping] Last Call: draft-ietf-sipping-service-examples (SessionInitiation Protocol Service Examples) to BCP, Henry Sinnreich
• New web-based submission tool, Tim Chown
  • RE: New web-based submission tool, Eric Gray
    • RE: New web-based submission tool, Janet P Gunn
  • Re: New web-based submission tool, Dave Crocker
    • Re: New web-based submission tool, Tim Chown
• November 75% OFF, VIAGRA ® Official Site
  • <Possible follow-ups>
  • November 75% OFF, Canadian Doctor Nigel Elkins
• More Vancouver Hotels, Lyndon Nerenberg
• Hotels in YVR, lconroy
  • Re: Hotels in YVR, Lyndon Nerenberg
• Fwd: Gen-art review of draft-ietf-ccamp-inter-domain-pd-path-comp-05.txt, JP Vasseur
• IETF Liaison to ITU-NGN, Joe Abley
• Gen-ART Last Call review of draft-klensin-unicode-escapes-06.txt, Spencer Dawkins
  • Re: Gen-ART Last Call review of draft-klensin-unicode-escapes-06.txt, John C Klensin
    • Re: Gen-ART Last Call review of draft-klensin-unicode-escapes-06.txt, Sam Hartman
      • Re: Gen-ART Last Call review of draft-klensin-unicode-escapes-06.txt, Spencer Dawkins
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Peter Saint-Andre
  • Message not available
    • Re: [Ietf-message-headers] Re: Re:I-DAction:draft-saintandre-header-pres-00.txt, Peter Saint-Andre
  • Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, SM
    • Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Peter Saint-Andre
      • Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, SM
      • Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Peter Saint-Andre
      • Message not available
      • Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Peter Saint-Andre
      • Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Sam Hartman
      • Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Alexey Melnikov
      • Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Cullen Jennings
      • Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Peter Saint-Andre
      • Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Cullen Jennings
• Re: Last Call: draft-goodwin-iso-urn (A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO)) to Informational RFC, Frank Ellermann
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Bernard Aboba
  • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Russ Housley
  • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Ted Hardie
    • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Stephane Bortzmeyer
  • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Jari Arkko
  • <Possible follow-ups>
  • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Michelle Cotton
    • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Stephane Bortzmeyer
      • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Jari Arkko
  • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Bernard Aboba
    • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Bill Fenner
      • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Jari Arkko
• Re: Last Call: draft-korhonen-mip6-service (Service Selection for Mobile IPv6) to Informational RFC, Brian E Carpenter
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Frank Ellermann
  • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Brian E Carpenter
    • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Lars Eggert
    • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Jari Arkko
  • <Possible follow-ups>
  • Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP, Bill Fenner
• FW: Last Call: draft-ietf-psamp-sample-tech (Sampling and Filtering Techniques for IP Packet Selection) to Proposed Standard, Romascanu, Dan (Dan)
• FW: Last Call: draft-ietf-psamp-protocol (Packet Sampling (PSAMP) Protocol Specifications) to Proposed Standard, Romascanu, Dan (Dan)
  • Re: [PSAMP] FW: Last Call: draft-ietf-psamp-protocol (Packet Sampling (PSAMP) Protocol Specifications) to Proposed Standard, Benoit Claise
• Reminder: Offer of time on the IPR WG agenda for rechartering, Harald Tveit Alvestrand
  • RE: Reminder: Offer of time on the IPR WG agenda for rechartering, Lawrence Rosen
    • Re: Reminder: Offer of time on the IPR WG agenda for rechartering, Steven M. Bellovin
      • Re: Reminder: Offer of time on the IPR WG agenda for rechartering, Keith Moore
      • Re: Reminder: Offer of time on the IPR WG agenda for rechartering, Spencer Dawkins
      • Re: Reminder: Offer of time on the IPR WG agenda for rechartering, Brian E Carpenter
    • Re: Reminder: Offer of time on the IPR WG agenda for rechartering, Norbert Bollow
• tools everywhere (was Daily Dose version 2 launched, Scott O. Bradner
  • Re: tools everywhere (was Daily Dose version 2 launched, Brian E Carpenter
  • <Possible follow-ups>
  • Re: tools everywhere (was Daily Dose version 2 launched, Scott O. Bradner
    • Re: tools everywhere (was Daily Dose version 2 launched, Harald Tveit Alvestrand
  • Re: tools everywhere (was Daily Dose version 2 launched, John C Klensin
    • Re: tools everywhere, Frank Ellermann
    • Re: tools everywhere (was Daily Dose version 2 launched, Dave Crocker
• Daily Dose version 2 launched, Pasi.Eronen
  • Re: Daily Dose version 2 launched, John C Klensin
    • Message not available
      • Re: Daily Dose version 2 launched, Joel M. Halpern
      • Re: Daily Dose version 2 launched, Henrik Levkowetz
      • Message not available
      • Re: Daily Dose version 2 launched, Olafur Gudmundsson
      • Re: Daily Dose version 2 launched, Joel M. Halpern
      • Re: Daily Dose version 2 launched, SM
      • Re: Daily Dose version 2 launched, Lyndon Nerenberg
      • RE: Daily Dose version 2 launched, Eric Burger
      • Re: Daily Dose version 2 launched, Dave Crocker
      • Re: Daily Dose version 2 launched, Henrik Levkowetz
      • Re: Daily Dose version 2 launched, Jari Arkko
      • Re: Daily Dose version 2 launched, Stephane Bortzmeyer
      • RE: Daily Dose version 2 launched, Pasi.Eronen
      • Re: Daily Dose version 2 launched, Stephane Bortzmeyer
      • RE: Daily Dose version 2 launched, michael.dillon
      • Re: Daily Dose version 2 launched, Stephane Bortzmeyer
      • Re: Daily Dose version 2 launched, Hannes Tschofenig
      • Re: Daily Dose version 2 launched, Lars Eggert
      • RE: Daily Dose version 2 launched, Pasi.Eronen
      • RE: Daily Dose version 2 launched, michael.dillon
      • Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched), Jari Arkko
      • Re: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched), Stephen Farrell
      • RE: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched), Hallam-Baker, Phillip
      • RE: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched), michael.dillon
      • Re: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched), Henrik Levkowetz
      • RE: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched), michael.dillon
      • Re: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched), Theodore Tso
      • Re: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched), Dave Crocker
      • RE: Daily Dose version 2 launched, Pasi.Eronen
      • RE: Daily Dose version 2 launched, Eric Gray
      • Re: Daily Dose version 2 launched, Henrik Levkowetz
      • Re: Daily Dose version 2 launched, Thomas Narten
      • RE: Daily Dose version 2 launched, michael.dillon
      • Re: Daily Dose version 2 launched, Henrik Levkowetz
      • Re: Daily Dose version 2 launched, Jari Arkko
      • RE: Daily Dose version 2 launched, Pasi.Eronen
      • Re: Daily Dose version 2 launched, Cullen Jennings
      • Re: Daily Dose version 2 launched, Harald Tveit Alvestrand
      • Re: Daily Dose version 2 launched, Lyndon Nerenberg
      • Re: Daily Dose version 2 launched, Steven M. Bellovin
• Opposing tls-authz-extns, Alessandro Forghieri
• ccamp-archive, want to become a porn star?, walker
• secdir review of draft-ietf-v6ops-scanning-implications-03, Jeffrey Hutzelman
• Dr. JunIchiro 'Itojun' Hagino, Jun Murai
• Re: Last Call: draft-ietf-xcon-framework (A Framework for Centralized Conferencing) to Proposed Standard, Sam Hartman
  • Re: Last Call: draft-ietf-xcon-framework (A Framework for Centralized Conferencing) to Proposed Standard, SM
• Re: Patents can be for good, not only evil, Eric Burger
  • Re: Patents can be for good, not only evil, Dave Crocker
    • Re: Patents can be for good, not only evil, Russ Nelson
      • Re: Patents can be for good, not only evil, Alexander Terekhov
  • <Possible follow-ups>
  • Re: Patents can be for good, not only evil, Richard Stallman
• 2026, draft, full, etc., Eliot Lear
  • Re: 2026, draft, full, etc., Dave Cridland
    • RE: 2026, draft, full, etc., michael.dillon
    • Re: 2026, draft, full, etc., Peter Saint-Andre
  • Re: 2026, draft, full, etc., James M. Polk
  • Re: 2026, draft, full, etc., Brian E Carpenter
    • Re: 2026, draft, full, etc., Frank Ellermann
  • Re: 2026, draft, full, etc., Ned Freed
    • Re: 2026, draft, full, etc., Dave Crocker
  • RE: 2026, draft, full, etc., Hallam-Baker, Phillip
  • Re: 2026, draft, full, etc., Simon Josefsson
    • Re: 2026, draft, full, etc., Brian E Carpenter
      • Re: 2026, draft, full, etc., Peter Saint-Andre
      • Re: 2026, draft, full, etc., John C Klensin
    • Re: 2026, draft, full, etc., Eliot Lear
    • Re: 2026, draft, full, etc., Ned Freed
  • <Possible follow-ups>
  • Re: 2026, draft, full, etc., Bob Braden
    • RE: 2026, draft, full, etc., Hallam-Baker, Phillip
    • Re: 2026, draft, full, etc., Brian E Carpenter
• A question about [Fwd: WG Review: Performance Metrics at Other Layers (pmol)], Leslie Daigle
  • Re: A question about [Fwd: WG Review: Performance Metrics at Other Layers (pmol)], Sam Hartman
    • RE: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Romascanu, Dan (Dan)
      • RE: [PMOL] Re: A question about [Fwd: WG Review: PerformanceMetrics atOther Layers (pmol)], Dan Schutzer
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Sam Hartman
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Brian E Carpenter
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], David R Oran
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Bill Sommerfeld
      • Re: [PMOL] Re: A question about [Fwd: WG Review: PerformanceMetrics atOther Layers (pmol)], Randy Presuhn
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Joe Touch
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Stephen Kent
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Joe Touch
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Steven M. Bellovin
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Joe Touch
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Sam Hartman
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Steven M. Bellovin
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Joe Touch
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Steven M. Bellovin
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Joe Touch
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Stephen Kent
      • Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Joe Touch
  • Re: A question about [Fwd: WG Review: Performance Metrics at Other Layers (pmol)], Yangwoo Ko
• Oppose draft-carpenter-ipr-patent-frswds-00, James M. Polk
  • Re: Oppose draft-carpenter-ipr-patent-frswds-00, Henning Schulzrinne
    • Re: Oppose draft-carpenter-ipr-patent-frswds-00, Brian E Carpenter
  • RE: Oppose draft-carpenter-ipr-patent-frswds-00, Eric Burger
    • Re: Oppose draft-carpenter-ipr-patent-frswds-00, Simon Josefsson
      • Re: Oppose draft-carpenter-ipr-patent-frswds-00, James M. Polk
      • Re: Oppose draft-carpenter-ipr-patent-frswds-00, Simon Josefsson
      • Re: Oppose draft-carpenter-ipr-patent-frswds-00, James M. Polk
      • Re: Oppose draft-carpenter-ipr-patent-frswds-00, James M. Polk
• Nominet position paper about Signing the Root., Roy Arends
  • Re: Nominet position paper about Signing the Root., Thierry Moreau
• Minor addition to draft-williams-on-channel-binding; one week to respond, Sam Hartman
  • Re: [saag] Minor addition to draft-williams-on-channel-binding; one week to respond, Jeffrey Hutzelman
• Re: rejection of patents and standards, Eric Burger
• Free? Software Foundation, Scott O. Bradner
  • Re: Free? Software Foundation, Stephane Bortzmeyer
    • Re: Free? Software Foundation, Scott O. Bradner
      • Re: Free? Software Foundation, Stephane Bortzmeyer
      • Re: Free? Software Foundation, Scott O. Bradner
      • Re: Free? Software Foundation, Stefanos Harhalakis
• Silly TLS Auth lobbying, RJ Atkinson
  • Re: Silly TLS Auth lobbying, Masataka Ohta
  • RE: Silly TLS Auth lobbying, michael.dillon
  • Re: Silly TLS Auth lobbying, Sam Hartman
  • Re: Silly TLS Auth lobbying, Simon Josefsson
  • RE: Silly TLS Auth lobbying, Hallam-Baker, Phillip
• Please oppose patent-encumbered technologies, including draft-housley-tls-authz-extns, Ben Finney
  • Re: Please oppose patent-encumbered technologies, including draft-housley-tls-authz-extns, Sam Hartman
    • Re: Please oppose patent-encumbered technologies, including draft-housley-tls-authz-extns, Ben Finney
      • Re: Please oppose patent-encumbered technologies, including draft-housley-tls-authz-extns, Ben Finney
• About referenced documents..., lconroy
  • Re: About referenced documents..., Randy Presuhn
    • Re: About referenced documents..., Andrew G. Malis
  • Re: About referenced documents..., Tom Yu
    • Re: About referenced documents..., lconroy
      • Re: About referenced documents..., Brian E Carpenter
      • Re: About referenced documents..., Tom Yu
      • Re: About referenced documents..., Randy Presuhn
      • Re: About referenced documents..., Frank Ellermann
      • Re: About referenced documents..., Tom Yu
      • Re: About referenced documents..., Randy Presuhn
      • Re: About referenced documents..., Brian E Carpenter
      • Re: About referenced documents..., Tom Yu
      • Re: About referenced documents..., Chris Grigg
• Musical commentary from the RIPE meeting, Harald Tveit Alvestrand
  • Re: Musical commentary from the RIPE meeting, Dave Crocker
  • RE: Musical commentary from the RIPE meeting, David B. Nelson
    • RE: Musical commentary from the RIPE meeting, Ole Jacobsen
  • RE: Musical commentary from the RIPE meeting, Gordon.Lennox
    • Re: Musical commentary from the RIPE meeting, Dave Crocker
      • Re: Musical commentary from the RIPE meeting, Marc Manthey
• Gen-ART Last Call review of draft-ietf-avt-rtp-vorbis-06, Spencer Dawkins
  • Re: Gen-ART Last Call review of draft-ietf-avt-rtp-vorbis-06, Luca Barbato
• Experimental makes sense for tls-authz, Randy Presuhn
  • Re: Experimental makes sense for tls-authz, Melinda Shore
  • RE: Experimental makes sense for tls-authz, Powers Chuck-RXCP20
  • Experimental makes sense for tls-authz, Joel M. Halpern
    • Re: Experimental makes sense for tls-authz, Ned Freed
    • Re: Experimental makes sense for tls-authz, Ben Finney
    • RE: Experimental makes sense for tls-authz, David Harrington
    • Re: Experimental makes sense for tls-authz, Ben Finney
  • Re: Experimental makes sense for tls-authz, Brian E Carpenter
    • Re: Experimental makes sense for tls-authz, Scott Kitterman
      • RE: Experimental makes sense for tls-authz, Hallam-Baker, Phillip
    • DOS (was: Experimental makes sense for tls-authz), Frank Ellermann
      • RE: DOS (was: Experimental makes sense for tls-authz), Hallam-Baker, Phillip
      • Re: DOS, Frank Ellermann
  • Re: Experimental makes sense for tls-authz, Stjepan Gros
  • <Possible follow-ups>
  • Re: Experimental makes sense for tls-authz, Noel Chiappa
    • Re: Experimental makes sense for tls-authz, Ben Finney
      • Re: Experimental makes sense for tls-authz, David Morris
      • Re: Experimental makes sense for tls-authz, Ben Finney
      • Re: Experimental makes sense for tls-authz, Andrew Newton
      • Re: Experimental makes sense for tls-authz, David Morris
      • Re: Experimental makes sense for tls-authz, Andrew Newton
      • Re: Experimental makes sense for tls-authz, Rob Evans
      • Non-participants [Re: Experimental makes sense for tls-authz], Brian E Carpenter
      • Re: Non-participants [Re: Experimental makes sense for tls-authz], Bill Manning
      • Re: Non-participants [Re: Experimental makes sense for tls-authz], Brian E Carpenter
      • Re: Non-participants [Re: Experimental makes sense for tls-authz], Andrew Newton
      • Re: Non-participants [Re: Experimental makes sense for tls-authz], Ned Freed
      • Re: Non-participants, Frank Ellermann
      • Re: Non-participants [Re: Experimental makes sense for tls-authz], Dan Riley
      • Experimental track (was: Non-participants), Frank Ellermann
      • Re: Experimental track, Brian E Carpenter
      • Re: Experimental track, Frank Ellermann
      • Re: Experimental makes sense for tls-authz, Bill Fenner
      • Re: Experimental makes sense for tls-authz, Bill Sommerfeld
    • Re: Experimental makes sense for tls-authz, James Seng
    • Re: Experimental makes sense for tls-authz, Ben Finney
  • Re: Experimental makes sense for tls-authz, Bernard Aboba
    • Re: Experimental makes sense for tls-authz, Brian E Carpenter
      • Re: Experimental makes sense for tls-authz, Brian Dickson
      • Re: Experimental makes sense for tls-authz, Bernard Aboba
      • Re: Experimental makes sense for tls-authz, Andrew Newton
      • Re: Experimental makes sense for tls-authz, Brian E Carpenter
      • Re: Experimental makes sense for tls-authz, Bernard Aboba
  • Re: Experimental makes sense for tls-authz, Noel Chiappa
  • Re: Experimental makes sense for tls-authz, Noel Chiappa
    • Re: Experimental makes sense for tls-authz, Eric Rosen
      • Re: Experimental makes sense for tls-authz, Sam Hartman
  • Re: Experimental makes sense for tls-authz, Bob Braden
• Call for IAOC Nominations and Volunteers, The IESG
  • <Possible follow-ups>
  • Call for IAOC Nominations and Volunteers, IAB Chair
• Opposition to accepting TLS-authz an experimental standard, Richard Hartmann
• We oppose TLS-authz "experimental" standard, Reinhard Moosauer
• I oppose making TLS-authz an experimental standard, Sven Lilienthal
  • <Possible follow-ups>
  • I oppose making TLS-authz an experimental standard, Franky Almonte
    • Re: I oppose making TLS-authz an experimental standard, Byung-Hee HWANG
  • Re: I oppose making TLS-authz an experimental standard, Noel Chiappa
• TLS-authz "experimental" standard, Richard Wilbur
  • <Possible follow-ups>
  • TLS-authz "experimental" standard, Christoph Resch
  • TLS-authz "experimental" standard, Richard Wilbur
    • Re: TLS-authz "experimental" standard and RESPONSIBILITY TO PUBLISH, TS Glassey
    • The Sgt at Arms Please? RE: TLS-authz "experimental" standard, Hallam-Baker, Phillip
      • Re: The Sgt at Arms Please? RE: TLS-authz "experimental" standard, Sam Hartman
      • Re: The Sgt at Arms Please? RE: TLS-authz "experimental" standard, Brian E Carpenter
      • Re: The Sgt at Arms Please? RE: TLS-authz "experimental" standard, Theodore Tso
      • Re: The Sgt at Arms Please? RE: TLS-authz "experimental" standard, Dave Crocker
      • RE: The Sgt at Arms Please? RE: TLS-authz "experimental" standard, Hallam-Baker, Phillip
      • Re: The Sgt at Arms Please? RE: TLS-authz "experimental" standard, TS Glassey
      • Hallam-Baker's First Law of Internet Lawyering Was: The Sgt at Arms Please? RE: TLS-authz "experimental" standard, Hallam-Baker, Phillip
      • Re: Hallam-Baker's First Law of Internet Lawyering Was: The Sgt at Arms Please? RE: TLS-authz "experimental" standard, TS Glassey
      • Re: The Sgt at Arms Please? RE: TLS-authz "experimental" standard, TS Glassey
      • Message not available
      • Re: [gnu.org #353281] The Sgt at Arms Please? RE: TLS-authz "experimental" standard, John Sullivan
• Please reject proprietary standards., Ismael Jones
  • Re: Please reject proprietary standards., Harald Tveit Alvestrand
• A pattented standard is not a standard, J. Pablo FernÃndez
  • RE: A pattented standard is not a standard, Hallam-Baker, Phillip
    • RE: A pattented standard is not a standard, Scott Brim
    • Re: A pattented standard is not a standard, Bill Fenner
    • RE: A pattented standard is not a standard, Byung-Hee HWANG
      • Message not available
      • RE: A pattented standard is not a standard, Byung-Hee HWANG
• TLS Authorisation, Willy Weisz
  • <Possible follow-ups>
  • TLS Authorisation, Eugeny Shkrigunov
  • TLS authorisation, Nicholas Bohm
• TLS Auth, Eike Lange
  • <Possible follow-ups>
  • TLS auth, Crazy Mister
• Concerns on TLS authorization extensions, John Wyatt
• Experimental TLS Authorization Standard, Craig, David
• Comment on TLS authorization, Bernhard Damberger
• TLS Authorization, Ringo Kamens
  • <Possible follow-ups>
  • TLS Authorization, Bryan Quigley
  • TLS authorization, Kenneth Jacobs
  • TLS authorization, Daniel Richman
  • TLS authorization, Edward Bishop
  • TLS authorization, matthew Alborough
  • TLS authorization, Gill Fitzgerald
  • TLS authorization, Sean Gant
  • TLS authorization, Giulio Fidente
  • TLS Authorization, Sheldon Gruber
  • Re: TLS authorization, Tim O'Kelly
  • TLS authorization, Zaine Ridling
  • TLS authorization, lukasz . stelmach
  • TLS authorization, George Georgalis
  • TLS authorization, Aaron Griffin
  • TLS authorization, malcolm mcqueen
• TLS Authorization Extensions, Matthew Flaschen
  • <Possible follow-ups>
  • TLS Authorization Extensions, Roman Kononov
• Please reject draft-housley-tls-authz-extns, Toni Mueller
  • Re: Please reject draft-housley-tls-authz-extns (supplementary note), Toni Mueller
• I oppose the publication of draft-housley-tls-authz-extns as an experimental standard., Michel Debar
• TLS-authz standardization, Jan.Haul
• Opposing making TLS-authz an experimental standard, Darko Ivancan
• FIfF opposes making TLS-authz an experimental standard, Jakob SchrÃter
• draft-housley-tls-authz-extns, Andreas Huennebeck
  • <Possible follow-ups>
  • draft-housley-tls-authz-extns, Daniel Kauffman
• comment opposing TLS-authz "experimental", Diez B. Roggisch
• patented standards that go along with TLS-authz, Walter Bender
• FSF opposes making TLS-authz an experimental standard, John Sullivan
• please REJECT tls-authz until it is patent-free!, Chris MacGregor
• We oppose TLS-authz., Jo
• opposing TLS-authz "experimental", Bruno Delcourt
• NO to TLS-authz, Chuck Burgess
• TLS-authz, Joshua N Pritikin
  • Megatron (was: TLS-authz), Frank Ellermann
    • Re: Megatron, Brian E Carpenter
      • Re: Megatron, Harald Alvestrand
      • Re: Megatron, Frank Ellermann
  • <Possible follow-ups>
  • TLS-authz, Benj. Mako Hill
  • TLS-authz, Leandro Guimarães Faria Corcete DUTRA
  • TLS-authz, Alex Schröder
  • TLS-authz, Aubrey Jaffer
• IETF 70 - meeting conflict - any way to juggle schedule to accommodate?, Brian Dickson
  • Re: IETF 70 - meeting conflict - any way to juggle schedule to accommodate?, Jari Arkko
• Offer of time on the IPR WG agenda for rechartering, Harald Tveit Alvestrand
  • RE: Offer of time on the IPR WG agenda for rechartering, Lawrence Rosen
    • Re: Offer of time on the IPR WG agenda for rechartering, Harald Alvestrand
  • Re: Offer of time on the IPR WG agenda for rechartering, Ted Hardie
    • Re: Offer of time on the IPR WG agenda for rechartering, Harald Alvestrand
• ccamp-archive sitting next to a hot blonde, quinn
• RE: Last Call: draft-ietf-psamp-framework (A Framework for Packet Selection and Reporting) to Informational RFC, Romascanu, Dan (Dan)
  • RE: [PSAMP] RE: Last Call: draft-ietf-psamp-framework (A Framework forPacket Selection and Reporting) to Informational RFC, DUFFIELD, NICHOLAS G (NICK)
• Re: A priori IPR choices, Lawrence Rosen
  • RE: A priori IPR choices, Philippe Verdy
    • FYI 28 (was: A priori IPR choices), Frank Ellermann
      • RE: FYI 28 (was: A priori IPR choices), Hallam-Baker, Phillip
    • Re: A priori IPR choices, Brian E Carpenter
• An example of what is wrong with the IETF's IPv6 documentation, michael.dillon
  • Re: An example of what is wrong with the IETF's IPv6 documentation, David Conrad
    • RE: An example of what is wrong with the IETF's IPv6 documentation, michael.dillon
      • Re: An example of what is wrong with the IETF's IPv6 documentation, JORDI PALET MARTINEZ
      • Re: An example of what is wrong with the IETF's IPv6 documentation, Mark Smith
  • Re: An example of what is wrong with the IETF's IPv6 documentation, Stephane Bortzmeyer
• Gen-ART review of draft-ietf-avt-topologies-06.txt, Suresh Krishnan
  • Re: Gen-ART review of draft-ietf-avt-topologies-06.txt, Magnus Westerlund
• Re: Last Call: draft-klensin-unicode-escapes (ASCII Escaping ofUnicode Characters) to BCP, Peter Constable
  • Re: Last Call: draft-klensin-unicode-escapes (ASCII Escaping ofUnicode Characters) to BCP, Stephane Bortzmeyer
    • RE: Last Call: draft-klensin-unicode-escapes (ASCII Escaping ofUnicode Characters) to BCP, Peter Constable
  • <Possible follow-ups>
  • Re: Last Call: draft-klensin-unicode-escapes (ASCII Escaping ofUnicode Characters) to BCP, Peter Constable
• Re: A priori IPR choices [Re: Third Last Call:draft-housley-tls-authz-extns], Hallam-Baker, Phillip
• Re: Last Call: draft-klensin-unicode-escapes (ASCII Escaping of Unicode Characters) to BCP, Stephane Bortzmeyer
  • Re: Last Call: draft-klensin-unicode-escapes (ASCII Escaping ofUnicode Characters) to BCP, Frank Ellermann
• secdir review of draft-ietf-tsvwg-ecn-mpls-02.txt, Tom Yu
  • Re: secdir review of draft-ietf-tsvwg-ecn-mpls-02.txt, Bob Briscoe
    • Re: secdir review of draft-ietf-tsvwg-ecn-mpls-02.txt, Tom Yu
      • Re: secdir review of draft-ietf-tsvwg-ecn-mpls-02.txt, Lars Eggert
• Gen-art review of draft-ietf-rmt-bb-fec-rs-04.txt, Elwyn Davies
• review of draft-ietf-nfsv4-nfs-rdma-problem-statement-07.txt, Sandy Murphy
• Gen-ART review of draft-ietf-sip-answermode-06.txt, Suresh Krishnan
• FW: ITU-T Recommendations, Yaakov Stein
• Host for IETF 73, Ray Pelletier
• Vancouver Host & Sponsor Lineup!, Ray Pelletier
• RFC3678: header incompatibility, Jun-ichiro itojun Hagino
  • <Possible follow-ups>
  • Re: RFC3678: header incompatibility, Bill Fenner
    • Re: RFC3678: header incompatibility, Jun-ichiro itojun Hagino