IETF Discussion Archive - Date Index

• Dec 17 2007
• Re: IPv4 Outage Planned for IETF 71 Plenary, Eliot Lear
• RE: IPv4 Outage Planned for IETF 71 Plenary, Yaakov Stein
• Re: IPv4 Outage Planned for IETF 71 Plenary, Ned Freed
• Re: TCP, Marshall Eubanks
• Dec 17 2007
• Re: IETF interoperability testing, Dave Crocker
• Re: IPv4 Outage Planned for IETF 71 Plenary, Joel Jaeggli
• RE: IPv4 Outage Planned for IETF 71 Plenary, Hallam-Baker, Phillip
• Re: IETF interoperability testing, Randy Presuhn
• Re: TCP, Matthew J Zekauskas
• Re: TCP, Fred Baker
• Re: IPv4 Outage Planned for IETF 71 Plenary, Ralph Droms
• Re: IPv4 Outage Planned for IETF 71 Plenary, Iljitsch van Beijnum
• IETF interoperability testing, Dave Crocker
• Re: IPv4 Outage Planned for IETF 71 Plenary, JORDI PALET MARTINEZ
• Re: IPv4 Outage Planned for IETF 71 Plenary, Fred Baker
• Re: IPv4 Outage Planned for IETF 71 Plenary, Dave Crocker
• Re: IPv4 Outage Planned for IETF 71 Plenary, Dave Crocker
• Re: IPv4 Outage Planned for IETF 71 Plenary, JORDI PALET MARTINEZ
• RE: IPv4 Outage Planned for IETF 71 Plenary, Mehmet Ersue
• RE: [secdir] Review of draft-ietf-l2vpn-oam-req-frmk-09, Tobias Gondrom
• Re: IPv4 Outage Planned for IETF 71 Plenary, Russ Housley
• Re: IPv4 Outage Planned for IETF 71 Plenary, Ralph Droms
• Re: IPv4 Outage Planned for IETF 71 Plenary, Sam Hartman
• Re: IPv4 Outage Planned for IETF 71 Plenary, Dave Crocker
• Re: TCP, Joe Abley
• Re: IPv4 Outage Planned for IETF 71 Plenary, JORDI PALET MARTINEZ
• Hey Baby, Claudette Stein
• Re: IPv4 Outage Planned for IETF 71 Plenary, Norbert Bollow
• Re: IPv4 Outage Planned for IETF 71 Plenary, Stephane Bortzmeyer
• Re: IPv4 Outage Planned for IETF 71 Plenary, Stephane Bortzmeyer
• Re: IPv4 Outage Planned for IETF 71 Plenary, JW Atwood
• RE: [16NG] RE: Last Call: draft-ietf-16ng-ps-goals (IP over 802.16Problem Statement and Goals) to Informational RFC, rana.sircar
• Re: [16NG] RE: Last Call: draft-ietf-16ng-ps-goals (IP over 802.16 Problem Statement and Goals) to Informational RFC, Daniel Park
• RE : Gen-ART review of draft-evain-ebu-urn-01.txt, Evain, Jean-Pierre
• RE: [secdir] Review of draft-ietf-l2vpn-oam-req-frmk-09, Dinesh Mohan
• Re: TCP, Greg Shepherd
• Re: IPv4 Outage Planned for IETF 71 Plenary, Bill Manning
• Dec 16 2007
• Re: TCP, Tony Finch
• Re: IPv4 Outage Planned for IETF 71 Plenary, Avri Doria
• Re: IPv4 Outage Planned for IETF 71 Plenary, Paul Hoffman
• Re: IPv4 Outage Planned for IETF 71 Plenary, Bob Braden
• Re: IPv4 Outage Planned for IETF 71 Plenary, Aki Niemi
• Re: IPv4 Outage Planned for IETF 71 Plenary, Ole Jacobsen
• Re: IPv4 Outage Planned for IETF 71 Plenary, Dave Crocker
• Re: IPv4 Outage Planned for IETF 71 Plenary, Bob Braden
• Re: IPv4 Outage Planned for IETF 71 Plenary, Bob Braden
• Re: IPv4 Outage Planned for IETF 71 Plenary, Dave Crocker
• Re: IPv4 Outage Planned for IETF 71 Plenary, Paul Hoffman
• Re: IPv4 Outage Planned for IETF 71 Plenary, Dave Crocker
• Re: IPv4 Outage Planned for IETF 71 Plenary, Iljitsch van Beijnum
• Concerns about the NoteWell Data Evidence., TS Glassey
• RE: IPv4 Outage Planned for IETF 71 Plenary, Ole Jacobsen
• RE: IPv4 Outage Planned for IETF 71 Plenary, Yaakov Stein
• Dec 15 2007
• Re: TCP, Fred Baker
• Re: IPv4 Outage Planned for IETF 71 Plenary, Lixia Zhang
• Re: IPv4 Outage Planned for IETF 71 Plenary, Jaap Akkerhuis
• Re: IPv4 Outage Planned for IETF 71 Plenary, Marshall Eubanks
• RE: IPv4 Outage Planned for IETF 71 Plenary, Edward Lewis
• Re: IPv4 Outage Planned for IETF 71 Plenary, Stewart Bryant
• Re: IPv4 Outage Planned for IETF 71 Plenary, Mohsen Souissi
• Hey Baby its Pipper, Wiley Nicholson
• Re: IPv4 Outage Planned for IETF 71 Plenary, Francis Dupont
• TCP, Jeyasekar Antony
• RE: IPv4 Outage Planned for IETF 71 Plenary, Christian Huitema
• Re: IPv4 Outage Planned for IETF 71 Plenary, Bill Manning
• Re: IPv4 Outage Planned for IETF 71 Plenary, Joel Jaeggli
• Re: IPv4 Outage Planned for IETF 71 Plenary, Bill Manning
• Re: IPv4 Outage Planned for IETF 71 Plenary, Edward Lewis
• Re: IPv4 Outage Planned for IETF 71 Plenary, Paul Hoffman
• Dec 14 2007
• Re: IPv4 Outage Planned for IETF 71 Plenary, Joel Jaeggli
• Re: IPv4 Outage Planned for IETF 71 Plenary, Pekka Savola
• Re: IPv4 Outage Planned for IETF 71 Plenary, Joao Damas
• Re: IPv4 Outage Planned for IETF 71 Plenary, Mark Andrews
• Re: IPv4 Outage Planned for IETF 71 Plenary, Stephane Bortzmeyer
• Re: IPv4 Outage Planned for IETF 71 Plenary, Stephane Bortzmeyer
• Re: IPv4 Outage Planned for IETF 71 Plenary, Joel Jaeggli
• Re: IPv4 Outage Planned for IETF 71 Plenary, Mark Andrews
• IPv4 Outage Planned for IETF 71 Plenary, IETF Chair
• Re: Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?, Stephane Bortzmeyer
• Re: Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?, Russ Housley
• Re: Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?, Bob Braden
• Re: Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?, Joe Baptista
• Re: Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?, Daniel Brown
• Re: Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?, Marshall Eubanks
• [Inquiry #98454] Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?, Stephane Bortzmeyer
• Re: Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?, Roy Arends
• Forbidden RFC (Was: Should the RFC Editor publish an RFC in less than 2 months?, Stephane Bortzmeyer
• Re: Transitioning IETF DNS services, Ray Pelletier
• Re: Transitioning IETF DNS services, Ray Pelletier
• Re: IETF Hosting Opportunity - March 2009, Kurt Erik Lindqvist
• Weekly posting summary for ietf at ietf.org, Thomas Narten
• Retention policy for list's and the processes which show the lists integrity, TS Glassey
• IETF Survey December 2007, Ray Pelletier
• Re: Transitioning IETF DNS services, Ray Pelletier
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4) (was: Lists and aliases), Ned Freed
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4), Frank Ellermann
• Re: DNS when target services are unavailable (was: Re: Transitioning IETF DNS services), Mark Andrews
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Russ Housley
• Dec 13 2007
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4) (was: Lists and aliases), John C Klensin
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4) (was: Lists and aliases), Ned Freed
• Re: DNS when target services are unavailable, Dave Crocker
• Re: DNS when target services are unavailable (was: Re: Transitioning IETF DNS services), John C Klensin
• Re: DNS when target services are unavailable (was: Re: Transitioning IETF DNS services), Stephane Bortzmeyer
• DNS when target services are unavailable (was: Re: Transitioning IETF DNS services), John C Klensin
• Re: Transitioning IETF DNS services, Daniel Brown
• Re: Transitioning IETF DNS services, Russ Housley
• RE: [secdir] Review of draft-ietf-l2vpn-oam-req-frmk-09, Dinesh Mohan
• RE: [secdir] Review of draft-ietf-l2vpn-oam-req-frmk-09, Tobias Gondrom
• RE: [secdir] Review of draft-ietf-l2vpn-oam-req-frmk-09, Tobias Gondrom
• Re: Transitioning IETF DNS services, Mark Andrews
• Re: Transitioning IETF DNS services, Bill Manning
• Re: Transitioning IETF DNS services, Dave Crocker
• Re: Transitioning IETF DNS services, Mark Andrews
• Re: Transitioning IETF DNS services, Brian Dickson
• Re: Transitioning IETF DNS services, Mark Andrews
• Re: Transitioning IETF DNS services, Mr. James W. Laferriere
• Dec 12 2007
• RE: Revising full standards, Bob Braden
• Transitioning IETF DNS services, Ray Pelletier
• Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4) (was: Lists and aliases), Frank Ellermann
• Re: Lists and aliases (Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)), Ned Freed
• RE: Revising full standards, Hallam-Baker, Phillip
• RE: Revising full standards, Hallam-Baker, Phillip
• Re: Lists and aliases (Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)), Tony Finch
• Re: Revising full standards, Tony Finch
• Re: Lists and aliases (Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)), Ned Freed
• Dec 11 2007
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1), Pete Resnick
• Re: Revising full standards, Dave Crocker
• Re: Revising full standards, Harald Tveit Alvestrand
• Lists and aliases (Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1)), Harald Tveit Alvestrand
• Re: Revising full standards, Bob Braden
• Re: Revising full standards, Iain Calder
• Re: Last Call: draft-ietf-nea-requirements (Network Endpoint Assessment (NEA): Overview and Requirements) to Informational RFC, Frank Ellermann
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1), Ned Freed
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4), John C Klensin
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (4), Frank Ellermann
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1), Dave Crocker
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1), Frank Ellermann
• Dec 10 2007
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1), Ned Freed
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1), Pete Resnick
• RE: Last Call: draft-ietf-16ng-ps-goals (IP over 802.16 Problem Statement and Goals) to Informational RFC, Romascanu, Dan (Dan)
• RE: Revising full standards, Hallam-Baker, Phillip
• Re: Revising full standards, John C Klensin
• Re: Revising full standards, Brian E Carpenter
• Re: Revising full standards, John C Klensin
• Re: Revising full standards, Dave Crocker
• Re: Revising full standards, Bob Braden
• Re: Revising full standards, Bob Braden
• RE: Revising full standards, Bob Braden
• Re: Revising full standards, Bob Braden
• Re: Revising full standards, Bob Braden
• Dec 09 2007
• Securing login and control channel transactions only, Barry
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (3), Frank Ellermann
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (2), Frank Ellermann
• Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1), Frank Ellermann
• The code sprint, Kurt Erik Lindqvist
• Dec 08 2007
• Draft IETF 70 Wednesday Plenary Minutes, Russ Housley
• Dec 07 2007
• RE: Revising full standards, Hallam-Baker, Phillip
• Re: Revising full standards, Eric Burger
• Re: Revising full standards, John C Klensin
• 2821bis issues (was: Revising full standards), Frank Ellermann
• Weekly posting summary for ietf at ietf.org, Thomas Narten
• Re: Revising full standards, Eric Burger
• Re: IETF Eurasia, Daniel Brown
• Re: Revising full standards, John C Klensin
• RE: IETF Eurasia, Hallam-Baker, Phillip
• Re: Revising full standards, Eric Burger
• Dec 06 2007
• Re: IETF Eurasia, Margaret Wasserman
• RE: Revising full standards, Hallam-Baker, Phillip
• RE: IETF Eurasia, Hallam-Baker, Phillip
• Re: Revising full standards, Brian E Carpenter
• Revising full standards, John C Klensin
• Re[2]: Last Call: draft-shimaoka-multidomain-pki-11.txt, Masaki SHIMAOKA
• Re: Should the RFC Editor publish an RFC in less than 2 months?, JP Vasseur
• Re: SAVI BOF notes, Barry Leiba
• SAVI BOF notes, Barry Leiba
• Dec 05 2007
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Loa Andersson
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Henrik Levkowetz
• Re: Audio streaming server challenges tuesday afternoon., Joel Jaeggli
• RE: Audio streaming server challenges tuesday afternoon., David B. Nelson
• Re: Last Call: draft-shimaoka-multidomain-pki-11.txt, Stephen Kent
• Re: Audio streaming server challenges tuesday afternoon., Ned Freed
• RE: Audio streaming server challenges tuesday afternoon., David B. Nelson
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Frank Ellermann
• RE: Audio streaming server challenges tuesday afternoon., Romascanu, Dan (Dan)
• Audio streaming server challenges tuesday afternoon., Joel Jaeggli
• RE: Should the RFC Editor publish an RFC in less than 2 months?, Tobias Gondrom
• Dec 04 2007
• Re: [NGO] Last Minute Reminder: New Sunday Tutorials, Benoit Claise
• Re: Last Call: draft-shimaoka-multidomain-pki (Memorandum for, Martin Rex
• RE: Gen-ART review of draft-ietf-sipping-toip-08.txt, Guido Gybels
• Re: Fwd: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard, Erik Wilde
• secdir review of draft-ietf-sip-uri-list-conferencing-02.txt, Glen Zorn
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Cullen Jennings
• RE: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS) IANA Considerations) to BCP, Eastlake III Donald-LDE008
• Please comment on IAOC candidates be appointed by the IESG, IETF Chair
• Re: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS) IANA Considerations) to BCP, Sam Weiler
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Robert Elz
• Re: Westin Vancouver Update, Joe Touch
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Scott O. Bradner
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Harald Tveit Alvestrand
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Brian E Carpenter
• Dec 03 2007
• Re: Last Call: draft-ietf-pkix-rfc3280bis (Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile) to Proposed Standard, Stephen Kent
• iFARE Bar-BOF, Hannes Tschofenig
• Audio Streaming has begun - IETF 70 Vancouver BC Canada December 2-7, Joel Jaeggli
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Daniel Brown
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Tom.Petch
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Norbert Bollow
• OOXML (was Re: Should the RFC Editor...), Norbert Bollow
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Robert Elz
• Re: Gathering for Itojun, RYUJI WAKIKAWA
• Gathering for Itojun, Jun Murai
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Hallam-Baker, Phillip
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Frank Ellermann
• Dec 02 2007
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Iljitsch van Beijnum
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Frank Ellermann
• Last Minute Reminder: New Sunday Tutorials, Margaret Wasserman
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Lixia Zhang
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Bob Hinden
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Frank Ellermann
• Re: Should the RFC Editor publish an RFC in less than 2 months?, John C Klensin
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Harald Tveit Alvestrand
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Bob Hinden
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Russ Housley
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Jari Arkko
• Dec 01 2007
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Alexey Melnikov
• Re: Should the RFC Editor publish an RFC in less than 2 months?, John C Klensin
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Frank Ellermann
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Magnus Westerlund
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Spencer Dawkins
• RE: Gen-ART review of draft-ietf-sipping-toip-08.txt, Guido Gybels
• RE: IETF Hosting Opportunity - March 2009, Terry Monroe
• TLS authorization, Kenneth Jacobs
• Secdir review of draft-ietf-manet-jitter-03.txt, patrick cain
• Re: Should the RFC Editor publish an RFC in less than 2 months?, John C Klensin
• RFC2821 Implementation Survey, Dave Crocker
• RFC2821 Implementation Survey, Dave Crocker
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Frank Ellermann
• Nov 30 2007
• Re: IETF Eurasia, James M. Polk
• RE: IETF Eurasia, James M. Polk
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Bob Hinden
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Brian E Carpenter
• Re: IETF Eurasia, Lars Eggert
• Re: Westin Vancouver Update, Sam Weiler
• RE: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard, Hollenbeck, Scott
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Harald Alvestrand
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Tom.Petch
• Re: IETF Hosting Opportunity - March 2009, rajesh rajesh
• Weekly posting summary for ietf at ietf.org, Thomas Narten
• RE: Westin Vancouver Update, Yaakov Stein
• Re: IETF Hosting Opportunity - March 2009, Joel Jaeggli
• Nov 29 2007
• RE: Westin Bayshore throwing us out, Livingood, Jason
• IETF 71 Info, Livingood, Jason
• Re: Westin Bayshore throwing us out, Adam Roach
• Re: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS)IANA Considerations) to BCP, Stephane Bortzmeyer
• RE: IETF Eurasia, Darryl \(Dassa\) Lynch
• RE: Hotel selection, Livingood, Jason
• RE: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS)IANA Considerations) to BCP, Eastlake III Donald-LDE008
• Re: IETF Hosting Opportunity - March 2009, Pete Resnick
• RE: Westin Bayshore throwing us out, Livingood, Jason
• RE: Westin Bayshore throwing us out, Livingood, Jason
• Re: Westin Bayshore throwing us out, John C Klensin
• Re: Westin Vancouver Update, Ted Hardie
• Re: Westin Bayshore throwing us out, Dave Crocker
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Sam Hartman
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Paul Hoffman
• RE: IETF Eurasia, michael.dillon
• Re: IETF Hosting Opportunity - March 2009, John C Klensin
• Re: Should the RFC Editor publish an RFC in less than 2 months?, John C Klensin
• Re: Lets be careful with those XML submissions to the RFC Editor, John C Klensin
• Re: IETF Hosting Opportunity - March 2009, Theodore Tso
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Sam Hartman
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Jari Arkko
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Alexey Melnikov
• Re: Westin Bayshore throwing us out, John C Klensin
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Dave Crocker
• Re: IETF Eurasia, Adrian Farrel
• Continental Distribution, Fred Baker
• Re: IETF Eurasia, Fred Baker
• IETF Eurasia, michael.dillon
• Re: Westin Bayshore throwing us out, Norbert Bollow
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor, Julian Reschke
• Re: IETF Hosting Opportunity - March 2009, Stephane Bortzmeyer
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Iljitsch van Beijnum
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Norbert Bollow
• Re: Should the RFC Editor publish an RFC in less than 2 months?, John C Klensin
• Re: Westin Vancouver Update, Cullen Jennings
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Harald Alvestrand
• Re: Hotel selection, Jari Arkko
• Re: Westin Bayshore throwing us out, John C Klensin
• Hotel selection, Fred Baker
• Re: Westin Bayshore throwing us out, Bill Strahm
• Re: IETF Hosting Opportunity - March 2009, Pekka Savola
• Re: Westin Bayshore throwing us out, Dave Crocker
• Re: Westin Vancouver Update, Spencer Dawkins
• Re: Westin Bayshore throwing us out, Fred Baker
• Re: Westin Vancouver Update, Dave Crocker
• Re: Westin Bayshore throwing us out, Dave Crocker
• Re: Missing materials, Frank Ellermann
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Eric Rescorla
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Frank Ellermann
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Sam Hartman
• Gen-ART Last Call review of draft-ietf-sip-uri-list-message-02.txt, Spencer Dawkins
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Sam Hartman
• Nov 28 2007
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Paul Hoffman
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Tim Polk
• Re: Lets be careful with those XML submissions to the RFC Editor, Ned Freed
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor, Julian Reschke
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Sam Hartman
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Cullen Jennings
• Re: Lets be careful with those XML submissions to the RFC Editor, Ned Freed
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Russ Housley
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Leslie Daigle
• Re: Westin Vancouver Update, Marshall Eubanks
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Brian E Carpenter
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Ted Hardie
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Eric Rescorla
• RE: Should the RFC Editor publish an RFC in less than 2 months?, Wassim Haddad
• Re: Should the RFC Editor publish an RFC in less than 2 months?, John C Klensin
• Re: Should the RFC Editor publish an RFC in less than 2 months?, Brian E Carpenter
• Re: IETF Hosting Opportunity - March 2009, Harald Tveit Alvestrand
• Should the RFC Editor publish an RFC in less than 2 months?, IETF Chair
• Re: Missing materials, Eric Rescorla
• RE: Westin Bayshore throwing us out, Hallam-Baker, Phillip
• Re: Our deadlines are dizzyingly complex and confusing, Tony Li
• Re: Missing materials, Frank Ellermann
• Westin Vancouver Update, Ray Pelletier
• Re: IETF Hosting Opportunity - March 2009, Russ Housley
• Re: IETF Hosting Opportunity - March 2009, Lars Eggert
• Re: IETF Hosting Opportunity - March 2009, Russ Housley
• Re: IETF Hosting Opportunity - March 2009, Jari Arkko
• Re: IETF Hosting Opportunity - March 2009, Lars Eggert
• Re: IETF Hosting Opportunity - March 2009, Joel Jaeggli
• Re: IETF Hosting Opportunity - March 2009, Pete Resnick
• Re: IETF Hosting Opportunity - March 2009, Alexey Melnikov
• Re: IETF Hosting Opportunity - March 2009, Alexey Melnikov
• Re: IETF Hosting Opportunity - March 2009, Mohsen Souissi
• Re: Westin Bayshore throwing us out, Ole Jacobsen
• Re: IETF Hosting Opportunity - March 2009, Ole Jacobsen
• Re: Westin Bayshore throwing us out, Dave Crocker
• Re: IETF Hosting Opportunity - March 2009, Peter Sylvester
• Re: IETF Hosting Opportunity - March 2009, Alexey Melnikov
• Re: IETF Hosting Opportunity - March 2009, Lars Eggert
• Missing materials, Eric Rescorla
• Re: Westin Bayshore throwing us out, Dave Crocker
• Re: Westin Bayshore throwing us out, John C Klensin
• Re: Our deadlines are dizzyingly complex and confusing, Lars Eggert
• Re: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS) IANA Considerations) to BCP, Stephane Bortzmeyer
• Re: Lets be careful with those XML submissions to the RFC Editor, Julian Reschke
• Re: Westin Bayshore throwing us out, Dave Crocker
• Re: Westin Bayshore throwing us out, Yangwoo Ko
• IETF Hosting Opportunity - March 2009, Terry Monroe
• RE: Westin Bayshore throwing us out, GOLDMAN, STUART O \(STUART\)
• Re: Lets be careful with those XML submissions to the RFC Editor, Marshall Rose
• Re: Westin Bayshore throwing us out, Dave Crocker
• RE: Westin Bayshore throwing us out, Yaakov Stein
• Re: Westin Bayshore throwing us out, John Levine
• Re: Westin Bayshore throwing us out, YAO
• Re: Westin Bayshore throwing us out, Fred Baker
• Re: Westin Bayshore throwing us out, Sam Weiler
• Nov 27 2007
• Re: Westin Bayshore throwing us out, Cullen Jennings
• Re: Westin Bayshore throwing us out, Ray Pelletier
• Re: Westin Bayshore throwing us out, Joel Jaeggli
• Re: Westin Bayshore throwing us out, Cullen Jennings
• Re: Westin Bayshore throwing us out, Eric Rescorla
• Re: Westin Bayshore throwing us out, Matt Lepinski
• Re: Westin Bayshore throwing us out, Tony Li
• Re: Westin Bayshore throwing us out, Pete Resnick
• Westin Bayshore throwing us out, Yaakov Stein
• Re: Lets be careful with those XML submissions to the RFC Editor, Jari Arkko
• Re: Lets be careful with those XML submissions to the RFC Editor, Joe Abley
• Re: Lets be careful with those XML submissions to the RFC Editor, Dave Crocker
• Re: Lets be careful with those XML submissions to the RFC Editor, Jari Arkko
• Re: Lets be careful with those XML submissions to the RFC Editor, Derek Atkins
• Re: Lets be careful with those XML submissions to the RFC Editor, Sandy Ginoza
• Re: Lets be careful with those XML submissions to the RFC Editor, Marshall Rose
• Re: Lets be careful with those XML submissions to the RFC Editor, Paul Hoffman
• Gen-ART review of draft-ietf-mip4-vpn-problem-solution-03.txt, Suresh Krishnan
• Re: Our deadlines are dizzyingly complex and confusing, Jari Arkko
• Re: Our deadlines are dizzyingly complex and confusing, Jari Arkko
• RE: Lets be careful with those XML submissions to the RFC Editor, WIJNEN, Bert \(Bert\)
• Re: Lets be careful with those XML submissions to the RFC Editor, Lars Eggert
• Re: Our deadlines are dizzyingly complex and confusing, Spencer Dawkins
• Re: Lets be careful with those XML submissions to the RFC Editor, Paul Hoffman
• Re: Our deadlines are dizzyingly complex and confusing, Noel Chiappa
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Steven M. Bellovin
• Nov 26 2007
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Peter Saint-Andre
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Brian E Carpenter
• RE: Our deadlines are dizzyingly complex and confusing, Hallam-Baker, Phillip
• Re: Our deadlines are dizzyingly complex and confusing, Henrik Levkowetz
• Re: Our deadlines are dizzyingly complex and confusing, Lakshminath Dondeti
• Audio Streaming - IETF 70 Vancouver BC Canada December 2-7, Joel Jaeggli
• 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, Spencer Dawkins
• RE: Lets be careful with those XML submissions to the RFC Editor, Hallam-Baker, Phillip
• Re: Our deadlines are dizzyingly complex and confusing, Joel Jaeggli
• Re: Lets be careful with those XML submissions to the RFC Editor, Ned Freed
• Re: Lets be careful with those XML submissions to the RFC Editor, Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor, John C Klensin
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Eric Rescorla
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Jari Arkko
• Re: Lets be careful with those XML submissions to the RFC Editor, Eliot Lear
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Iljitsch van Beijnum
• Energy and Networks, Bruce Nordman
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Eric Rescorla
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Brian E Carpenter
• Nov 25 2007
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor, Henrik Levkowetz
• Re: Lets be careful with those XML submissions to the RFC Editor, Mark Andrews
• Re: Lets be careful with those XML submissions to the RFC Editor, Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor, Henrik Levkowetz
• Re: Lets be careful with those XML submissions to the RFC Editor, Paul Hoffman
• Re: Lets be careful with those XML submissions to the RFC Editor, Jari Arkko
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Jari Arkko
• Re: Lets be careful with those XML submissions to the RFC Editor, Paul Hoffman
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Eric Rescorla
• Re: Lets be careful with those XML submissions to the RFC Editor, Henrik Levkowetz
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Brian E Carpenter
• Re: Lets be careful with those XML submissions to the RFC Editor, Julian Reschke
• Re: Lets be careful with those XML submissions to the RFC Editor, Paul Hoffman
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Eric Rescorla
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Brian E Carpenter
• Lets be careful with those XML submissions to the RFC Editor, Jari Arkko
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Eric Rescorla
• Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Bernard Aboba
• Security area review of draft-ietf-smime-bfibecms-08.txt, glenzorn
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Hannes Tschofenig
• Nov 24 2007
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Eric Rescorla
• Re: Last Call Comments on draft-ietf-shim6-hba-04, Hannes Tschofenig
• Last Call Comments on draft-ietf-shim6-hba-04, Eric Rescorla
• Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Iljitsch van Beijnum
• Re: Our deadlines are dizzyingly complex and confusing, Spencer Dawkins
• Gen-ART Last Call review of draft-ietf-shim6-hba-04, Spencer Dawkins
• Nov 23 2007
• Our deadlines are dizzyingly complex and confusing, Lakshminath Dondeti
• Re: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard, Lisa Dusseault
• Re: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard, Andrew Newton
• Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Bernard Aboba
• Weekly posting summary for ietf at ietf.org, Thomas Narten
• Re: [tsv-dir] Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Bernard_Aboba
• Re: Gen-ART review of draft-cheshire-ipv4-acd-05.txt, C. M. Heard
• Nov 22 2007
• Re: [Ietf-message-headers] Re: I-DAction:draft-saintandre-header-pres-00.txt, Cullen Jennings
• Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Bernard Aboba
• Fwd: Africa and IPv6, Marc Manthey
• Re: TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Iljitsch van Beijnum
• TSV-DIR Review of draft-ietf-shim6-protocol-09.txt, Bernard Aboba
• Nov 21 2007
• Re: Last Call: draft-wilde-sms-uri (URI Scheme for GSM Short Message Service) to Proposed Standard, Cullen Jennings
• RE: SAFE BoF in Vancouver, Markus.Isomaki
• November 75% OFF, Canadian Doctor Nigel Elkins
• Gen-art review of draft-ietf-l2vpn-vpls-bridge-interop-02.txt, Elwyn Davies
• Re: SAFE BoF in Vancouver, Colin Perkins
• Re: SAFE BoF in Vancouver, Ted Hardie
• Re: SAFE BoF in Vancouver, James M. Polk
• Nov 20 2007
• Re: SAFE BoF in Vancouver, Ted Hardie
• Re: SAFE BoF in Vancouver, Colin Perkins
• Re: SAFE BoF in Vancouver, Ted Hardie
• draft-van-beijnum-multi-mtu-01.txt, Iljitsch van Beijnum
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Iljitsch van Beijnum
• Fwd: Africa and IPv6, rajesh rajesh
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Brian E Carpenter
• Nov 19 2007
• Gen-ART review of draft-ietf-sipping-toip-08.txt, 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, 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
• Nov 16 2007
• Re: Gen-ART review of draft-cheshire-ipv4-acd-05.txt, Spencer Dawkins
• Re: Africa and IPv6, philemon
• Gen-ART review of draft-cheshire-ipv4-acd-05.txt, Spencer Dawkins
• Gen-ART review of draft-evain-ebu-urn-01.txt, Black_David
• Re: Africa and IPv6, SM
• Re: Africa and IPv6, JORDI PALET MARTINEZ
• SAFE BoF in Vancouver, Colin Perkins
• Re: I-D Action:draft-narten-ipv6-statement-00.txt, Iljitsch van Beijnum
• RE: FW: I-D Action:draft-narten-ipv6-statement-00.txt, michael.dillon
• Africa and IPv6, philemon
• Weekly posting summary for ietf at ietf.org, Thomas Narten
• Re: terminology proposal: NAT+PT (or NAT64 ?), Keith Moore
• Re: terminology proposal: NAT+PT (or NAT64 ?), Stephen Sprunk
• Nov 15 2007
• Re: I-D Action:draft-narten-ipv6-statement-00.txt, JORDI PALET MARTINEZ
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Sam Hartman
• Re: I-D Action:draft-narten-ipv6-statement-00.txt, Sam Hartman
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Jari Arkko
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Tom.Petch
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally, David Kessens
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Joe Touch
• Re: terminology proposal: NAT+PT (or NAT64 ?), Keith Moore
• Re: terminology proposal: NAT+PT (or NAT64 ?), Iljitsch van Beijnum
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Stephen Kent
• Note on submitting non -00 drafts automatically, Philip Matthews
• Re: I-D Action:draft-narten-ipv6-statement-00.txt, JORDI PALET MARTINEZ
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Iljitsch van Beijnum
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Noel Chiappa
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Marc Manthey
• Re: terminology proposal: NAT+PT (or NAT64 ?), Pekka Savola
• Re: terminology proposal: NAT+PT (or NAT64 ?), Keith Moore
• Re: terminology proposal: NAT+PT (or NAT64 ?), Rémi Després
• Re: FW: I-D Action:draft-narten-ipv6-statement-00.txt, Jari Arkko
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally, RJ Atkinson
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally, RJ Atkinson
• Re: [PMOL] Re: A question about [Fwd: WG Review: Performance Metrics atOther Layers (pmol)], Joe Touch
• Re: NAT+PT for IPv6 Transition & Operator Feedback generally, Eliot Lear