IETF Discussion

• Thread Index

• Re: Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Daniel Brown
• Re: Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Marshall Eubanks
• [Inquiry #98454] Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Stephane Bortzmeyer
• Re: Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Roy Arends
• Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Stephane Bortzmeyer
• Re: Transitioning IETF DNS services
  • From: Ray Pelletier
• Re: Transitioning IETF DNS services
  • From: Ray Pelletier
• Re: IETF Hosting Opportunity - March 2009
  • From: Kurt Erik Lindqvist
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Retention policy for list's and the processes which show the lists integrity
  • From: TS Glassey
• IETF Survey December 2007
  • From: Ray Pelletier
• Re: Transitioning IETF DNS services
  • From: Ray Pelletier
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4) (was: Lists and aliases)
  • From: Ned Freed
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4)
  • From: Frank Ellermann
• Re: DNS when target services are unavailable (was: Re: Transitioning IETF DNS services)
  • From: Mark Andrews
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Russ Housley
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4) (was: Lists and aliases)
  • From: John C Klensin
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4) (was: Lists and aliases)
  • From: Ned Freed
• Re: DNS when target services are unavailable
  • From: Dave Crocker
• Re: DNS when target services are unavailable (was: Re: Transitioning IETF DNS services)
  • From: John C Klensin
• Re: DNS when target services are unavailable (was: Re: Transitioning IETF DNS services)
  • From: Stephane Bortzmeyer
• DNS when target services are unavailable (was: Re: Transitioning IETF DNS services)
  • From: John C Klensin
• Re: Transitioning IETF DNS services
  • From: Daniel Brown
• Re: Transitioning IETF DNS services
  • From: Russ Housley
• RE: [secdir] Review of draft-ietf-l2vpn-oam-req-frmk-09
  • From: Tobias Gondrom
• RE: [secdir] Review of draft-ietf-l2vpn-oam-req-frmk-09
  • From: Dinesh Mohan
• RE: [secdir] Review of draft-ietf-l2vpn-oam-req-frmk-09
  • From: Tobias Gondrom
• Re: Transitioning IETF DNS services
  • From: Mark Andrews
• Re: Transitioning IETF DNS services
  • From: Bill Manning
• Re: Transitioning IETF DNS services
  • From: Dave Crocker
• Re: Transitioning IETF DNS services
  • From: Mark Andrews
• Re: Transitioning IETF DNS services
  • From: Brian Dickson
• Re: Transitioning IETF DNS services
  • From: Mark Andrews
• Re: Transitioning IETF DNS services
  • From: Mr. James W. Laferriere
• RE: Revising full standards
  • From: Bob Braden
• Transitioning IETF DNS services
  • From: Ray Pelletier
• Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4) (was: Lists and aliases)
  • From: Frank Ellermann
• Re: Lists and aliases (Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1))
  • From: Ned Freed
• RE: Revising full standards
  • From: Hallam-Baker, Phillip
• RE: Revising full standards
  • From: Hallam-Baker, Phillip
• Re: Lists and aliases (Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1))
  • From: Tony Finch
• Re: Revising full standards
  • From: Tony Finch
• Re: Lists and aliases (Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1))
  • From: Ned Freed
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)
  • From: Pete Resnick
• Re: Revising full standards
  • From: Dave Crocker
• Re: Revising full standards
  • From: Bob Braden
• Re: Revising full standards
  • From: Harald Tveit Alvestrand
• Lists and aliases (Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1))
  • From: Harald Tveit Alvestrand
• Re: Revising full standards
  • From: Iain Calder
• Re: Last Call: draft-ietf-nea-requirements (Network Endpoint Assessment (NEA): Overview and Requirements) to Informational RFC
  • From: Frank Ellermann
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)
  • From: Ned Freed
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4)
  • From: John C Klensin
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4)
  • From: Frank Ellermann
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)
  • From: Dave Crocker
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)
  • From: Frank Ellermann
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)
  • From: Ned Freed
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)
  • From: Pete Resnick
• RE: Last Call: draft-ietf-16ng-ps-goals (IP over 802.16 Problem Statement and Goals) to Informational RFC
  • From: Romascanu, Dan (Dan)
• Re: Revising full standards
  • From: John C Klensin
• RE: Revising full standards
  • From: Hallam-Baker, Phillip
• Re: Revising full standards
  • From: Brian E Carpenter
• Re: Revising full standards
  • From: John C Klensin
• Re: Revising full standards
  • From: Dave Crocker
• Re: Revising full standards
  • From: Bob Braden
• Re: Revising full standards
  • From: Bob Braden
• RE: Revising full standards
  • From: Bob Braden
• Re: Revising full standards
  • From: Bob Braden
• Re: Revising full standards
  • From: Bob Braden
• Securing login and control channel transactions only
  • From: Barry
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (3)
  • From: Frank Ellermann
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (2)
  • From: Frank Ellermann
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)
  • From: Frank Ellermann
• The code sprint
  • From: Kurt Erik Lindqvist
• Draft IETF 70 Wednesday Plenary Minutes
  • From: Russ Housley
• RE: Revising full standards
  • From: Hallam-Baker, Phillip
• Re: Revising full standards
  • From: Eric Burger
• Re: Revising full standards
  • From: John C Klensin
• 2821bis issues (was: Revising full standards)
  • From: Frank Ellermann
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Re: Revising full standards
  • From: Eric Burger
• Re: IETF Eurasia
  • From: Daniel Brown
• Re: Revising full standards
  • From: John C Klensin
• RE: IETF Eurasia
  • From: Hallam-Baker, Phillip
• Re: Revising full standards
  • From: Eric Burger
• Re: IETF Eurasia
  • From: Margaret Wasserman
• RE: Revising full standards
  • From: Hallam-Baker, Phillip
• RE: IETF Eurasia
  • From: Hallam-Baker, Phillip
• Re: Revising full standards
  • From: Brian E Carpenter
• Revising full standards
  • From: John C Klensin
• Re[2]: Last Call: draft-shimaoka-multidomain-pki-11.txt
  • From: Masaki SHIMAOKA
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: JP Vasseur
• Re: SAVI BOF notes
  • From: Barry Leiba
• SAVI BOF notes
  • From: Barry Leiba
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Loa Andersson
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Henrik Levkowetz
• Re: Audio streaming server challenges tuesday afternoon.
  • From: Joel Jaeggli
• RE: Audio streaming server challenges tuesday afternoon.
  • From: David B. Nelson
• Re: Last Call: draft-shimaoka-multidomain-pki-11.txt
  • From: Stephen Kent
• Re: Audio streaming server challenges tuesday afternoon.
  • From: Ned Freed
• RE: Audio streaming server challenges tuesday afternoon.
  • From: David B. Nelson
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Frank Ellermann
• RE: Audio streaming server challenges tuesday afternoon.
  • From: Romascanu, Dan (Dan)
• Audio streaming server challenges tuesday afternoon.
  • From: Joel Jaeggli
• RE: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Tobias Gondrom
• Re: [NGO] Last Minute Reminder: New Sunday Tutorials
  • From: Benoit Claise
• Re: Last Call: draft-shimaoka-multidomain-pki (Memorandum for
  • From: Martin Rex
• RE: Gen-ART review of draft-ietf-sipping-toip-08.txt
  • From: Guido Gybels
• Re: Fwd: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard
  • From: Erik Wilde
• secdir review of draft-ietf-sip-uri-list-conferencing-02.txt
  • From: Glen Zorn
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
  • From: Cullen Jennings
• RE: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS) IANA Considerations) to BCP
  • From: Eastlake III Donald-LDE008
• Please comment on IAOC candidates be appointed by the IESG
  • From: IETF Chair
• Re: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS) IANA Considerations) to BCP
  • From: Sam Weiler
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Robert Elz
• Re: Westin Vancouver Update
  • From: Joe Touch
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Scott O. Bradner
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Harald Tveit Alvestrand
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Brian E Carpenter
• Re: Last Call: draft-ietf-pkix-rfc3280bis (Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile) to Proposed Standard
  • From: Stephen Kent
• iFARE Bar-BOF
  • From: Hannes Tschofenig
• Audio Streaming has begun - IETF 70 Vancouver BC Canada December 2-7
  • From: Joel Jaeggli
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Daniel Brown
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Tom.Petch
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Norbert Bollow
• OOXML (was Re: Should the RFC Editor...)
  • From: Norbert Bollow
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Robert Elz
• Re: Gathering for Itojun
  • From: RYUJI WAKIKAWA
• Gathering for Itojun
  • From: Jun Murai
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Hallam-Baker, Phillip
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Frank Ellermann
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Iljitsch van Beijnum
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Frank Ellermann
• Last Minute Reminder: New Sunday Tutorials
  • From: Margaret Wasserman
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Lixia Zhang
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Bob Hinden
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Frank Ellermann
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: John C Klensin
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Harald Tveit Alvestrand
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Bob Hinden
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Russ Housley
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Jari Arkko
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Alexey Melnikov
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: John C Klensin
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Frank Ellermann
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Magnus Westerlund
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Spencer Dawkins
• RE: IETF Hosting Opportunity - March 2009
  • From: Terry Monroe
• RE: Gen-ART review of draft-ietf-sipping-toip-08.txt
  • From: Guido Gybels
• TLS authorization
  • From: Kenneth Jacobs
• Secdir review of draft-ietf-manet-jitter-03.txt
  • From: patrick cain
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: John C Klensin
• RFC2821 Implementation Survey
  • From: Dave Crocker
• RFC2821 Implementation Survey
  • From: Dave Crocker
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Frank Ellermann
• Re: IETF Eurasia
  • From: James M. Polk
• RE: IETF Eurasia
  • From: James M. Polk
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Bob Hinden
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Brian E Carpenter
• Re: IETF Eurasia
  • From: Lars Eggert
• Re: Westin Vancouver Update
  • From: Sam Weiler
• RE: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard
  • From: Hollenbeck, Scott
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Harald Alvestrand
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Tom.Petch
• Re: IETF Hosting Opportunity - March 2009
  • From: rajesh rajesh
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• RE: Westin Vancouver Update
  • From: Yaakov Stein
• Re: IETF Hosting Opportunity - March 2009
  • From: Joel Jaeggli
• RE: Westin Bayshore throwing us out
  • From: Livingood, Jason
• IETF 71 Info
  • From: Livingood, Jason
• Re: Westin Bayshore throwing us out
  • From: Adam Roach
• Re: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS)IANA Considerations) to BCP
  • From: Stephane Bortzmeyer
• RE: IETF Eurasia
  • From: Darryl (Dassa) Lynch
• RE: Hotel selection
  • From: Livingood, Jason
• RE: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS)IANA Considerations) to BCP
  • From: Eastlake III Donald-LDE008
• Re: IETF Hosting Opportunity - March 2009
  • From: Pete Resnick
• RE: Westin Bayshore throwing us out
  • From: Livingood, Jason
• RE: Westin Bayshore throwing us out
  • From: Livingood, Jason
• Re: Westin Bayshore throwing us out
  • From: John C Klensin
• Re: Westin Vancouver Update
  • From: Ted Hardie
• Re: Westin Bayshore throwing us out
  • From: Dave Crocker
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Sam Hartman
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Paul Hoffman
• RE: IETF Eurasia
  • From: michael.dillon
• Re: IETF Hosting Opportunity - March 2009
  • From: John C Klensin
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: John C Klensin
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: John C Klensin
• Re: IETF Hosting Opportunity - March 2009
  • From: Theodore Tso
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Sam Hartman
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Jari Arkko
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Alexey Melnikov
• Re: Westin Bayshore throwing us out
  • From: John C Klensin
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Dave Crocker
• Re: IETF Eurasia
  • From: Adrian Farrel
• Continental Distribution
  • From: Fred Baker
• Re: IETF Eurasia
  • From: Fred Baker
• IETF Eurasia
  • From: michael.dillon
• Re: Westin Bayshore throwing us out
  • From: Norbert Bollow
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Julian Reschke
• Re: IETF Hosting Opportunity - March 2009
  • From: Stephane Bortzmeyer
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Iljitsch van Beijnum
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Norbert Bollow
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: John C Klensin
• Re: Westin Vancouver Update
  • From: Cullen Jennings
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Harald Alvestrand
• Re: Hotel selection
  • From: Jari Arkko
• Re: Westin Bayshore throwing us out
  • From: John C Klensin
• Hotel selection
  • From: Fred Baker
• Re: Westin Bayshore throwing us out
  • From: Bill Strahm
• Re: IETF Hosting Opportunity - March 2009
  • From: Pekka Savola
• Re: Westin Bayshore throwing us out
  • From: Dave Crocker
• Re: Westin Vancouver Update
  • From: Spencer Dawkins
• Re: Westin Bayshore throwing us out
  • From: Fred Baker
• Re: Westin Vancouver Update
  • From: Dave Crocker
• Re: Westin Bayshore throwing us out
  • From: Dave Crocker
• Re: Missing materials
  • From: Frank Ellermann
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Eric Rescorla
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Frank Ellermann
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Sam Hartman
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Sam Hartman
• Gen-ART Last Call review of draft-ietf-sip-uri-list-message-02.txt
  • From: Spencer Dawkins
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Paul Hoffman
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Tim Polk
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Ned Freed
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Julian Reschke
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Sam Hartman
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Cullen Jennings
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Ned Freed
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Russ Housley
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Leslie Daigle
• Re: Westin Vancouver Update
  • From: Marshall Eubanks
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Brian E Carpenter
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Ted Hardie
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Eric Rescorla
• RE: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Wassim Haddad
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: John C Klensin
• Re: Should the RFC Editor publish an RFC in less than 2 months?
  • From: Brian E Carpenter
• Re: IETF Hosting Opportunity - March 2009
  • From: Harald Tveit Alvestrand
• Should the RFC Editor publish an RFC in less than 2 months?
  • From: IETF Chair
• Re: Missing materials
  • From: Eric Rescorla
• RE: Westin Bayshore throwing us out
  • From: Hallam-Baker, Phillip
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Tony Li
• Re: Missing materials
  • From: Frank Ellermann
• Westin Vancouver Update
  • From: Ray Pelletier
• Re: IETF Hosting Opportunity - March 2009
  • From: Russ Housley
• Re: IETF Hosting Opportunity - March 2009
  • From: Lars Eggert
• Re: IETF Hosting Opportunity - March 2009
  • From: Russ Housley
• Re: IETF Hosting Opportunity - March 2009
  • From: Jari Arkko
• Re: IETF Hosting Opportunity - March 2009
  • From: Lars Eggert
• Re: IETF Hosting Opportunity - March 2009
  • From: Joel Jaeggli
• Re: IETF Hosting Opportunity - March 2009
  • From: Pete Resnick
• Re: IETF Hosting Opportunity - March 2009
  • From: Alexey Melnikov
• Re: IETF Hosting Opportunity - March 2009
  • From: Alexey Melnikov
• Re: IETF Hosting Opportunity - March 2009
  • From: Mohsen Souissi
• Re: Westin Bayshore throwing us out
  • From: Ole Jacobsen
• Re: IETF Hosting Opportunity - March 2009
  • From: Ole Jacobsen
• Re: Westin Bayshore throwing us out
  • From: Dave Crocker
• Re: IETF Hosting Opportunity - March 2009
  • From: Peter Sylvester
• Re: IETF Hosting Opportunity - March 2009
  • From: Alexey Melnikov
• Re: IETF Hosting Opportunity - March 2009
  • From: Lars Eggert
• Missing materials
  • From: Eric Rescorla
• Re: Westin Bayshore throwing us out
  • From: Dave Crocker
• Re: Westin Bayshore throwing us out
  • From: John C Klensin
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Lars Eggert
• Re: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS) IANA Considerations) to BCP
  • From: Stephane Bortzmeyer
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Julian Reschke
• Re: Westin Bayshore throwing us out
  • From: Dave Crocker
• Re: Westin Bayshore throwing us out
  • From: Yangwoo Ko
• RE: Westin Bayshore throwing us out
  • From: GOLDMAN, STUART O (STUART)
• IETF Hosting Opportunity - March 2009
  • From: Terry Monroe
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Marshall Rose
• Re: Westin Bayshore throwing us out
  • From: Dave Crocker
• Re: Westin Bayshore throwing us out
  • From: Dave Crocker
• RE: Westin Bayshore throwing us out
  • From: Yaakov Stein
• Re: Westin Bayshore throwing us out
  • From: John Levine
• Re: Westin Bayshore throwing us out
  • From: YAO
• Re: Westin Bayshore throwing us out
  • From: Fred Baker
• Re: Westin Bayshore throwing us out
  • From: Sam Weiler
• Re: Westin Bayshore throwing us out
  • From: Cullen Jennings
• Re: Westin Bayshore throwing us out
  • From: Ray Pelletier
• Re: Westin Bayshore throwing us out
  • From: Joel Jaeggli
• Re: Westin Bayshore throwing us out
  • From: Cullen Jennings
• Re: Westin Bayshore throwing us out
  • From: Matt Lepinski
• Re: Westin Bayshore throwing us out
  • From: Eric Rescorla
• Re: Westin Bayshore throwing us out
  • From: Tony Li
• Re: Westin Bayshore throwing us out
  • From: Pete Resnick
• Westin Bayshore throwing us out
  • From: Yaakov Stein
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Jari Arkko
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Joe Abley
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Dave Crocker
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Jari Arkko
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Derek Atkins
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Marshall Rose
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Sandy Ginoza
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Paul Hoffman
• Gen-ART review of draft-ietf-mip4-vpn-problem-solution-03.txt
  • From: Suresh Krishnan
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Jari Arkko
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Jari Arkko
• RE: Lets be careful with those XML submissions to the RFC Editor
  • From: WIJNEN, Bert (Bert)
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Lars Eggert
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Spencer Dawkins
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Paul Hoffman
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Noel Chiappa
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Steven M. Bellovin
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
  • From: Peter Saint-Andre
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Brian E Carpenter
• RE: Our deadlines are dizzyingly complex and confusing
  • From: Hallam-Baker, Phillip
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Henrik Levkowetz
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Lakshminath Dondeti
• Audio Streaming - IETF 70 Vancouver BC Canada December 2-7
  • From: Joel Jaeggli
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Lakshminath Dondeti
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Eric Rescorla
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Lakshminath Dondeti
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Spencer Dawkins
• RE: Lets be careful with those XML submissions to the RFC Editor
  • From: Hallam-Baker, Phillip
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Joel Jaeggli
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Ned Freed
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: John C Klensin
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Eric Rescorla
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Jari Arkko
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Eliot Lear
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Iljitsch van Beijnum
• Energy and Networks
  • From: Bruce Nordman
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Eric Rescorla
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Brian E Carpenter
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Henrik Levkowetz
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Mark Andrews
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Henrik Levkowetz
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Paul Hoffman
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Jari Arkko
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Jari Arkko
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Paul Hoffman
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Henrik Levkowetz
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Brian E Carpenter
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Julian Reschke
• Re: Lets be careful with those XML submissions to the RFC Editor
  • From: Paul Hoffman
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Eric Rescorla
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Brian E Carpenter
• Lets be careful with those XML submissions to the RFC Editor
  • From: Jari Arkko
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Eric Rescorla
• Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt
  • From: Bernard Aboba
• Security area review of draft-ietf-smime-bfibecms-08.txt
  • From: glenzorn
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Hannes Tschofenig
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Eric Rescorla
• Re: Last Call Comments on draft-ietf-shim6-hba-04
  • From: Hannes Tschofenig
• Last Call Comments on draft-ietf-shim6-hba-04
  • From: Eric Rescorla
• Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt
  • From: Iljitsch van Beijnum
• Re: Our deadlines are dizzyingly complex and confusing
  • From: Spencer Dawkins
• Gen-ART Last Call review of draft-ietf-shim6-hba-04
  • From: Spencer Dawkins
• Our deadlines are dizzyingly complex and confusing
  • From: Lakshminath Dondeti
• Re: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard
  • From: Lisa Dusseault
• Re: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard
  • From: Andrew Newton
• Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt
  • From: Bernard Aboba
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Re: [tsv-dir] Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt
  • From: Bernard_Aboba
• Re: Gen-ART review of draft-cheshire-ipv4-acd-05.txt
  • From: C. M. Heard
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
  • From: Cullen Jennings
• Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt
  • From: Bernard Aboba
• Fwd: Africa and IPv6
  • From: Marc Manthey
• Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt
  • From: Iljitsch van Beijnum
• TSV-DIR Review of draft-ietf-shim6-protocol-09.txt
  • From: Bernard Aboba
• Re: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard
  • From: Cullen Jennings
• RE: SAFE BoF in Vancouver
  • From: Markus.Isomaki
• Gen-art review of draft-ietf-l2vpn-vpls-bridge-interop-02.txt
  • From: Elwyn Davies
• Re: SAFE BoF in Vancouver
  • From: Colin Perkins
• Re: SAFE BoF in Vancouver
  • From: Ted Hardie
• Re: SAFE BoF in Vancouver
  • From: James M. Polk
• Re: SAFE BoF in Vancouver
  • From: Ted Hardie
• Re: SAFE BoF in Vancouver
  • From: Colin Perkins
• Re: SAFE BoF in Vancouver
  • From: Ted Hardie
• draft-van-beijnum-multi-mtu-01.txt
  • From: Iljitsch van Beijnum
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Iljitsch van Beijnum
• Fwd: Africa and IPv6
  • From: rajesh rajesh
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Brian E Carpenter
• Gen-ART review of draft-ietf-sipping-toip-08.txt
  • From: Suresh Krishnan
• 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
  • From: Tom.Petch
• Fw: Last Call: draft-evain-ebu-urn (A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU)) to Informational RFC
  • From: Tom.Petch
• Re: Gen-ART review of draft-cheshire-ipv4-acd-05.txt
  • From: Spencer Dawkins
• Re: Africa and IPv6
  • From: philemon
• Gen-ART review of draft-cheshire-ipv4-acd-05.txt
  • From: Spencer Dawkins
• Gen-ART review of draft-evain-ebu-urn-01.txt
  • From: Black_David
• RE: Gen-ART review of draft-evain-ebu-urn-01.txt
  • From: Evain, Jean-Pierre
• Re: Africa and IPv6
  • From: SM
• Re: Africa and IPv6
  • From: JORDI PALET MARTINEZ
• SAFE BoF in Vancouver
  • From: Colin Perkins
• Re: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Iljitsch van Beijnum
• RE: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: michael.dillon
• Africa and IPv6
  • From: philemon
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Keith Moore
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Stephen Sprunk
• Re: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: JORDI PALET MARTINEZ
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Sam Hartman
• Re: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Sam Hartman
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Jari Arkko
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Tom.Petch
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: David Kessens
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Joe Touch
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Keith Moore
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Iljitsch van Beijnum
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Stephen Kent
• Note on submitting non -00 drafts automatically
  • From: Philip Matthews
• Re: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: JORDI PALET MARTINEZ
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Iljitsch van Beijnum
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Noel Chiappa
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Marc Manthey
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Pekka Savola
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Keith Moore
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Rémi Després
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Jari Arkko
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: RJ Atkinson
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: RJ Atkinson
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Joe Touch
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Eliot Lear
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Keith Moore
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Hallam-Baker, Phillip
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Steven M. Bellovin
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Spencer Dawkins
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Iljitsch van Beijnum
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Rémi Després
• RE: terminology proposal: NAT+PT
  • From: Sheng Jiang
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Keith Moore
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Rémi Després
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: David Kessens
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Joe Touch
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Steven M. Bellovin
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Sam Hartman
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Joe Touch
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Steven M. Bellovin
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Joe Touch
• RE: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Hallam-Baker, Phillip
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Keith Moore
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Stephen Kent
• Re: terminology proposal: NAT+PT
  • From: Keith Moore
• Re: terminology proposal: NAT+PT
  • From: Stephen Sprunk
• Re: terminology proposal: NAT+PT
  • From: Harald Tveit Alvestrand
• Re: terminology proposal: NAT+PT (or NAT64 ?)
  • From: Rémi Després
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Francis Dupont
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Iljitsch van Beijnum
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Lucy Lynch
• RE: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Hallam-Baker, Phillip
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Jari Arkko
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Joe Touch
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: Iljitsch van Beijnum
• Reject the "experimental" TLS authorization proposal
  • From: Ben Caplan
• NAT+PT for IPv6 Transition & Operator Feedback generally
  • From: RJ Atkinson
• terminology proposal: NAT+PT
  • From: RJ Atkinson
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Greg Skinner
• NAT-PT (Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt)
  • From: Harald Alvestrand
• RE: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: michael.dillon
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Thomas Narten
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Eliot Lear
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Tom.Petch
• Re: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Iljitsch van Beijnum
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Mohsen Souissi
• RE: New web-based submission tool
  • From: Janet P Gunn
• Re: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Iljitsch van Beijnum
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Noel Chiappa
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Pars Mutaf
• Re: New web-based submission tool
  • From: Tim Chown
• Re: New web-based submission tool
  • From: Dave Crocker
• RE: New web-based submission tool
  • From: Eric Gray
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: Thomas Narten
• FW: I-D Action:draft-narten-ipv6-statement-00.txt
  • From: JORDI PALET MARTINEZ
• secdir review of draft-ietf-l2vpn-vpls-mcast-reqts-05.txt
  • From: Stephen Hanna
• [secdir] Review of draft-ietf-l2vpn-oam-req-frmk-09
  • From: Tobias Gondrom
• RE: [Sipping] Last Call: draft-ietf-sipping-service-examples (SessionInitiation Protocol Service Examples) to BCP
  • From: Henry Sinnreich
• RE: [Sipping] Last Call: draft-ietf-sipping-service-examples (Ses sion Initiation Protocol Service Examples) to BCP
  • From: Hutton, Andrew
• Re: [PSAMP] FW: Last Call: draft-ietf-psamp-protocol (Packet Sampling (PSAMP) Protocol Specifications) to Proposed Standard
  • From: Benoit Claise
• New web-based submission tool
  • From: Tim Chown
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
  • From: Alexey Melnikov
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Re: Gen-ART Last Call review of draft-klensin-unicode-escapes-06.txt
  • From: Spencer Dawkins
• Re: Gen-ART Last Call review of draft-klensin-unicode-escapes-06.txt
  • From: Sam Hartman
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
  • From: Sam Hartman
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
  • From: Peter Saint-Andre
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Jari Arkko
• RE: Last Call: draft-levin-mmusic-xml-media-control (XML Schema forMedia Control) to Informational RFC
  • From: Even, Roni
• More Vancouver Hotels
  • From: Lyndon Nerenberg
• Re: Hotels in YVR
  • From: Lyndon Nerenberg
• Hotels in YVR
  • From: lconroy
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Bill Fenner
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
  • From: Peter Saint-Andre
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Bernard Aboba
• Re: I oppose making TLS-authz an experimental standard
  • From: Noel Chiappa
• RE: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched)
  • From: Hallam-Baker, Phillip
• Re: I oppose making TLS-authz an experimental standard
  • From: Byung-Hee HWANG
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
  • From: SM
• RE: Last Call: draft-levin-mmusic-xml-media-control (XML Schema for Media Control) to Informational RFC
  • From: Hollenbeck, Scott
• Re: Daily Dose version 2 launched
  • From: Henrik Levkowetz
• I oppose making TLS-authz an experimental standard
  • From: Franky Almonte
• Fwd: Gen-art review of draft-ietf-ccamp-inter-domain-pd-path-comp-05.txt
  • From: JP Vasseur
• Re: Daily Dose version 2 launched
  • From: Cullen Jennings
• RE: Daily Dose version 2 launched
  • From: michael.dillon
• Re: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched)
  • From: Dave Crocker
• IETF Liaison to ITU-NGN
  • From: Joe Abley
• Re: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched)
  • From: Theodore Tso
• Re: Daily Dose version 2 launched
  • From: Thomas Narten
• RE: Daily Dose version 2 launched
  • From: Eric Gray
• RE: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched)
  • From: michael.dillon
• Re: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched)
  • From: Henrik Levkowetz
• RE: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched)
  • From: michael.dillon
• Re: Daily Dose version 2 launched
  • From: Henrik Levkowetz
• Re: Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched)
  • From: Stephen Farrell
• RE: Daily Dose version 2 launched
  • From: Pasi.Eronen
• Putting requirements on volunteer tool developers (Was: Re: Daily Dose version 2 launched)
  • From: Jari Arkko
• RE: Daily Dose version 2 launched
  • From: michael.dillon
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
  • From: Peter Saint-Andre
• RE: Daily Dose version 2 launched
  • From: Pasi.Eronen
• RE: Daily Dose version 2 launched
  • From: Pasi.Eronen
• Re: Gen-ART Last Call review of draft-klensin-unicode-escapes-06.txt
  • From: John C Klensin
• Gen-ART Last Call review of draft-klensin-unicode-escapes-06.txt
  • From: Spencer Dawkins
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
  • From: SM
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Jari Arkko
• Re: [Ietf-message-headers] Re: Re:I-DAction:draft-saintandre-header-pres-00.txt
  • From: Peter Saint-Andre
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Stephane Bortzmeyer
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Stephane Bortzmeyer
• Re: Daily Dose version 2 launched
  • From: Jari Arkko
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt
  • From: Peter Saint-Andre
• Re: Last Call: draft-goodwin-iso-urn (A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO)) to Informational RFC
  • From: Frank Ellermann
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Bill Fenner
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Michelle Cotton
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Jari Arkko
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Ted Hardie
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Russ Housley
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Bernard Aboba
• Re: Daily Dose version 2 launched
  • From: Lars Eggert
• Re: Daily Dose version 2 launched
  • From: Hannes Tschofenig
• Re: Daily Dose version 2 launched
  • From: Stephane Bortzmeyer
• RE: Daily Dose version 2 launched
  • From: michael.dillon
• Re: Daily Dose version 2 launched
  • From: Stephane Bortzmeyer
• RE: Daily Dose version 2 launched
  • From: Pasi.Eronen
• Re: Daily Dose version 2 launched
  • From: Stephane Bortzmeyer
• Re: Daily Dose version 2 launched
  • From: Jari Arkko
• Re: Reminder: Offer of time on the IPR WG agenda for rechartering
  • From: Norbert Bollow
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Jari Arkko
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Lars Eggert
• Re: Last Call: draft-korhonen-mip6-service (Service Selection for Mobile IPv6) to Informational RFC
  • From: Brian E Carpenter
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Brian E Carpenter
• Re: Last Call: draft-arkko-rfc2780-proto-update (IANA Allocation Guidelines for the Protocol Field) to BCP
  • From: Frank Ellermann
• Re: Reminder: Offer of time on the IPR WG agenda for rechartering
  • From: Brian E Carpenter
• Re: Reminder: Offer of time on the IPR WG agenda for rechartering
  • From: Spencer Dawkins
• Re: Reminder: Offer of time on the IPR WG agenda for rechartering
  • From: Keith Moore
• Re: Reminder: Offer of time on the IPR WG agenda for rechartering
  • From: Steven M. Bellovin
• RE: Reminder: Offer of time on the IPR WG agenda for rechartering
  • From: Lawrence Rosen
• FW: Last Call: draft-ietf-psamp-sample-tech (Sampling and Filtering Techniques for IP Packet Selection) to Proposed Standard
  • From: Romascanu, Dan (Dan)
• FW: Last Call: draft-ietf-psamp-protocol (Packet Sampling (PSAMP) Protocol Specifications) to Proposed Standard
  • From: Romascanu, Dan (Dan)
• Re: Daily Dose version 2 launched
  • From: Henrik Levkowetz
• Re: 2026, draft, full, etc.
  • From: John C Klensin
• Reminder: Offer of time on the IPR WG agenda for rechartering
  • From: Harald Tveit Alvestrand
• Re: Daily Dose version 2 launched
  • From: Dave Crocker
• RE: Patents can be for good, not only evil
  • From: Eric Burger
• RE: Daily Dose version 2 launched
  • From: Eric Burger
• Re: tools everywhere (was Daily Dose version 2 launched
  • From: Dave Crocker
• Re: Daily Dose version 2 launched
  • From: Lyndon Nerenberg
• Re: tools everywhere
  • From: Frank Ellermann
• Re: tools everywhere (was Daily Dose version 2 launched
  • From: Harald Tveit Alvestrand
• Re: Daily Dose version 2 launched
  • From: Harald Tveit Alvestrand
• Re: tools everywhere (was Daily Dose version 2 launched
  • From: John C Klensin
• Re: 2026, draft, full, etc.
  • From: Dave Crocker
• New IETF Journal available now
  • From: Mirjam Kuehne
• Re: tools everywhere (was Daily Dose version 2 launched
  • From: Brian E Carpenter
• Re: tools everywhere (was Daily Dose version 2 launched
  • From: Scott O. Bradner
• Re: Daily Dose version 2 launched
  • From: Lyndon Nerenberg
• Re: Daily Dose version 2 launched
  • From: SM
• tools everywhere (was Daily Dose version 2 launched
  • From: Scott O. Bradner
• Re: Daily Dose version 2 launched
  • From: Olafur Gudmundsson
• Re: Daily Dose version 2 launched
  • From: Joel M. Halpern
• Re: Daily Dose version 2 launched
  • From: Lixia Zhang
• Re: Daily Dose version 2 launched
  • From: John C Klensin
• Re: 2026, draft, full, etc.
  • From: Brian E Carpenter
• Re: Daily Dose version 2 launched
  • From: Henrik Levkowetz
• Re: Daily Dose version 2 launched
  • From: Steven M. Bellovin
• Re: [PMOL] Re: A question about [Fwd: WG Review: PerformanceMetrics atOther Layers (pmol)]
  • From: Randy Presuhn
• RE: 2026, draft, full, etc.
  • From: Hallam-Baker, Phillip
• Re: Daily Dose version 2 launched
  • From: Joel M. Halpern
• Re: 2026, draft, full, etc.
  • From: Bob Braden
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Bill Sommerfeld
• Re: Daily Dose version 2 launched
  • From: John C Klensin
• Re: 2026, draft, full, etc.
  • From: Ned Freed
• Daily Dose version 2 launched
  • From: Pasi.Eronen
• Re: Please oppose patent-encumbered technologies, including draft-housley-tls-authz-extns
  • From: Ben Finney
• Re: 2026, draft, full, etc.
  • From: Eliot Lear
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Re: About referenced documents...
  • From: Tom Yu
• Re: About referenced documents...
  • From: Chris Grigg
• Re: Patents can be for good, not only evil
  • From: Alexander Terekhov
• Opposing tls-authz-extns
  • From: Alessandro Forghieri
• Re: Patents can be for good, not only evil
  • From: Russ Nelson
• Re: Please oppose patent-encumbered technologies, including draft-housley-tls-authz-extns
  • From: Ben Finney
• Re: Patents can be for good, not only evil
  • From: Richard Stallman
• Re: Experimental track
  • From: Frank Ellermann
• Re: Free? Software Foundation
  • From: Stefanos Harhalakis
• Re: 2026, draft, full, etc.
  • From: Peter Saint-Andre
• Re: Experimental track
  • From: Brian E Carpenter
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: David R Oran
• Re: 2026, draft, full, etc.
  • From: Brian E Carpenter
• Re: About referenced documents...
  • From: Brian E Carpenter
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)]
  • From: Brian E Carpenter
• Re: About referenced documents...
  • From: Randy Presuhn
• Re: About referenced documents...
  • From: Tom Yu