IETF Discussion Archive - Thread Index
[Prev Page] [Next Page] [Date Index]
Regd ospfASBdrRtrStatus,
Raj kiran
IETF-77 Clouds bar BoF at 11:30 AM on Thursday, 3/25/2010,
Bhumip Khasnabish
Re: [Sip] Last Call: draft-ietf-sip-ipv6-abnf-fix (Essential correction for IPv6 ABNF and URI comparison in RFC3261) to Proposed Standard,
Cullen Jennings
3D Technology Comes to Military and Security Forces,
Casey Farrell
Comments on draft-ogud-iana-protocol-maintenance-words-03,
Edward Lewis
Re: Last Call: draft-haberman-rpsl-reachable-test (An RPSL Interface Id for Operational Testing) to Proposed Standard,
Vesna Manojlovic
Bar BoF on Location Coherence Wednesday at 11:30 AM,
Richard Barnes
Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Brian E Carpenter
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Paul Hoffman
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Brian E Carpenter
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Andrew Sullivan
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
John C Klensin
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Andrew Sullivan
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
John C Klensin
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Paul Hoffman
- RE: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Christian Huitema
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Brian E Carpenter
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
John C Klensin
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Olafur Gudmundsson
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Paul Hoffman
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Olafur Gudmundsson
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Brian E Carpenter
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Brian E Carpenter
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries) to BCP,
Russ Housley
- secdir review/last call comments for : draft-ogud-iana-protocol-maintenance-words,
Sam Hartman
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
SM
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words,
Martin Rex
- RE: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitionsfor expressing standards requirements in IANA registries.) to BCP,
Dearlove, Christopher (UK)
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
Samuel Weiler
- <Possible follow-ups>
- Re: Last Call: draft-ogud-iana-protocol-maintenance-words (Definitions for expressing standards requirements in IANA registries.) to BCP,
SM
Change in ISOC Panel Topic for Tuesday at IETF 77,
IETF Chair
Review of draft-ietf-isms-dtls-tm-09.txt,
Bernard Aboba
RE: Last Call: draft-ietf-radext-status-server (Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol) to Informational RFC,
Bernard Aboba
Gen-ART (belated) LC Review of draft-ietf-nsis-nslp-natfw-23,
Ben Campbell
Internet wins 2010 Nobel Peace Prize...,
todd glassey
Audio Streaming Info - IETF 77 March 21-26, 2010,
Joel Jaeggli
On the IAB technical advice on the RPKI,
Phillip Hallam-Baker
Towards consensus on document format,
Phillip Hallam-Baker
- Re: Towards consensus on document format,
Melinda Shore
- Re: Towards consensus on document format,
Joe Touch
- Re: Towards consensus on document format,
Masataka Ohta
- Re: Towards consensus on document format,
Julian Reschke
- Re: Towards consensus on document format,
Masataka Ohta
- Re: Towards consensus on document format,
Julian Reschke
- Re: Towards consensus on document format,
Masataka Ohta
- Re: Towards consensus on document format,
Julian Reschke
- Re: Towards consensus on document format,
Masataka Ohta
- Re: Towards consensus on document format,
Doug Ewell
- Re: Towards consensus on document format,
Arnt Gulbrandsen
- Re: Towards consensus on document format,
Masataka Ohta
- Re: Towards consensus on document format,
Doug Ewell
- Re: Towards consensus on document format,
Phillip Hallam-Baker
- Re: Towards consensus on document format,
Masataka Ohta
- Re: Towards consensus on document format,
Phillip Hallam-Baker
- Re: Towards consensus on document format,
Masataka Ohta
- Re: Towards consensus on document format,
Doug Ewell
- Re: Towards consensus on document format,
Bill McQuillan
- Re: Towards consensus on document format,
tytso
- Re: Towards consensus on document format,
Jorge Amodio
- Re: Towards consensus on document format,
Phillip Hallam-Baker
- RE: Towards consensus on document format,
Michel Py
- Re: Towards consensus on document format,
Stewart Bryant
- [IETF] If document formats were radios was:Towards consensus on document format,
Michel Py
- Re: Towards consensus on document format,
Marshall Eubanks
- Re: Towards consensus on document format,
David Morris
- Re: Towards consensus on document format,
tytso
- Re: Towards consensus on document format,
Iljitsch van Beijnum
- <Possible follow-ups>
- RE: Towards consensus on document format,
Doug Ewell
- Re: Towards consensus on document format,
Phillip Hallam-Baker
- Re: Towards consensus on document format,
Brian E Carpenter
- Re: Towards consensus on document format,
Phillip Hallam-Baker
- Re: Towards consensus on document format,
Doug Ewell
- Re: Towards consensus on document format,
Julian Reschke
- Re: Towards consensus on document format,
JFC Morfin
- Re: Towards consensus on document format,
Richard Barnes
- Re: Towards consensus on document format,
Phillip Hallam-Baker
- Re: Towards consensus on document format,
Dave CROCKER
- Re: Towards consensus on document format,
Ole Jacobsen
- Re: Towards consensus on document format,
Tony Hansen
- Re: Towards consensus on document format,
Marshall Eubanks
- Re: Towards consensus on document format,
SM
- Re: Towards consensus on document format,
Douglas Otis
What day is 2010-01-02,
Cullen Jennings
- Re: What day is 2010-01-02,
Marshall Eubanks
- Re: What day is 2010-01-02,
Julian Reschke
- Re: What day is 2010-01-02,
Scott Brim
- Re: What day is 2010-01-02,
Robert Kisteleki
- Re: What day is 2010-01-02,
John C Klensin
- Re: What day is 2010-01-02,
Arnt Gulbrandsen
- Re: What day is 2010-01-02,
Sabahattin Gucukoglu
- <Possible follow-ups>
- Re: What day is 2010-01-02,
Phillips, Addison
- Re: What day is 2010-01-02,
John C Klensin
- RE: What day is 2010-01-02,
Phillips, Addison
- RE: What day is 2010-01-02,
John C Klensin
- RE: What day is 2010-01-02,
Phillips, Addison
- Re: What day is 2010-01-02,
Iljitsch van Beijnum
- Re: What day is 2010-01-02,
Yao Jiankang
- Re: What day is 2010-01-02,
Iljitsch van Beijnum
- Re: What day is 2010-01-02,
Michael Edward McNeil
- Re: What day is 2010-01-02,
Iljitsch van Beijnum
- RE: What day is 2010-01-02,
HUANG, JERRY (ATTLABS)
- Re: What day is 2010-01-02,
Ofer Inbar
- Message not available
- Re: What day is 2010-01-02,
YAO Jiankang
- Re: What day is 2010-01-02,
Joel Jaeggli
- Re: What day is 2010-01-02,
Alfredo Dal´Ava Júnior
- Re: What day is 2010-01-02,
Michael Edward McNeil
- Re: What day is 2010-01-02,
Alfredo Dal´Ava Júnior
- Re: What day is 2010-01-02,
Phillip Hallam-Baker
- Re: What day is 2010-01-02,
Marshall Eubanks
- Re: What day is 2010-01-02 (and what time is it),
Patrik Fältström
- Re: What day is 2010-01-02 (and what time is it),
Marshall Eubanks
- Re: What day is 2010-01-02 (and what time is it),
Patrik Fältström
- Re: What day is 2010-01-02 (and what time is it),
Tony Finch
- Re: What day is 2010-01-02 (and what time is it),
Phillip Hallam-Baker
- Re: What day is 2010-01-02,
Phillip Hallam-Baker
- Re: What day is 2010-01-02,
Marshall Eubanks
- Re: What day is 2010-01-02,
Tony Finch
- Re: What day is 2010-01-02,
Tony Finch
- Re: What day is 2010-01-02,
Bob Hinden
- Re: What day is 2010-01-02,
Michael Edward McNeil
- Re: What day is 2010-01-02,
Cullen Jennings
- Re: What day is 2010-01-02,
Loa Andersson
- Re: What day is 2010-01-02,
todd glassey
Error in Security Considerations in an RFC,
Florian Weimer
Retorical question: How do I pay for my registration?,
David Morris
IETF 80 in Prague,
Ray Pelletier
Re: FW: Last Call: draft-ietf-netmod-yang (YANG - A data modeling languagefor NETCONF) to Proposed Standard,
Graham Klyne
Why the normative form of IETF Standards is ASCII,
Donald Eastlake
- Re: Why the normative form of IETF Standards is ASCII,
Andrew Sullivan
- RE: Why the normative form of IETF Standards is ASCII,
Richard Shockey
- Re: Why the normative form of IETF Standards is ASCII,
Donald Eastlake
- Re: Why the normative form of IETF Standards is ASCII,
John Levine
- Re: Why the normative form of IETF Standards is ASCII,
David Morris
- Re: Why the normative form of IETF Standards is ASCII,
Iljitsch van Beijnum
- Re: Why the normative form of IETF Standards is ASCII,
Lars Eggert
- Re: Why the normative form of IETF Standards is ASCII,
John R. Levine
- Re: Why the normative form of IETF Standards is ASCII,
Tony Hansen
- Re: Why the normative form of IETF Standards is ASCII,
Richard Barnes
- Re: Why the normative form of IETF Standards is ASCII,
Iljitsch van Beijnum
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Iljitsch van Beijnum
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Arnt Gulbrandsen
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Marc Petit-Huguenin
- Re: Why the normative form of IETF Standards is ASCII,
Tony Finch
- Re: Why the normative form of IETF Standards is ASCII,
John Levine
- Re: Why the normative form of IETF Standards is ASCII,
Arnt Gulbrandsen
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Bob Braden
- Re: Why the normative form of IETF Standards is ASCII,
Andrew Sullivan
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
- Re: Why the normative form of IETF Standards is ASCII,
Melinda Shore
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Bob Braden
- Re: Why the normative form of IETF Standards is ASCII,
Tony Hansen
- Re: Why the normative form of IETF Standards is ASCII,
Andrew Sullivan
- Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- NroffEdit updated with December 2009 boilerplate,
Stefan Santesson
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Stefan Santesson
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Stefan Santesson
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Stefan Santesson
- Re: Why the normative form of IETF Standards is ASCII,
Yoav Nir
- Re: Why the normative form of IETF Standards is ASCII,
Bill Fenner
- Using xml2rfc (was: Re: Why the normative form of IETF Standards is ASCII),
Doug Ewell
- Re: Using xml2rfc (was: Re: Why the normative form of IETF Standards is ASCII),
Fred Baker
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
- Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- Re: Why the normative form of IETF Standards is ASCII,
Doug Ewell
- Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- Re: Why the normative form of IETF Standards is ASCII,
Doug Ewell
- Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- Re: Why the normative form of IETF Standards is ASCII,
Doug Ewell
- Re: Why the normative form of IETF Standards is ASCII,
Tim Bray
- Re: Why the normative form of IETF Standards is ASCII,
John Levine
- Make HTML and PDF more prominent, was: Re: Why the normative form of IETF Standards is ASCII,
Iljitsch van Beijnum
- Re: Make HTML and PDF more prominent, was: Re: Why the normative form of IETF Standards is ASCII,
Dave Cridland
- A state of spin ... presented in ASCII (was: Make HTML and PDF more prominent, was: Re: Why the normative form of IETF Standards is ASCII),
SM
- Re: A state of spin ... presented in ASCII,
Masataka Ohta
- Re: A state of spin ... presented in ASCII,
todd glassey
- Re: A state of spin ... presented in ASCII,
Masataka Ohta
- Re: A state of spin ... presented in ASCII,
Michael Dillon
- RE: A state of spin ... presented in ASCII,
Wes Beebee (wbeebee)
- Re: A state of spin ... presented in ASCII,
SM
- Re: A state of spin ... presented in ASCII,
Masataka Ohta
- Re: A state of spin ... presented in ASCII,
Doug Ewell
- Re: A state of spin ... presented in ASCII,
Masataka Ohta
- Re: A state of spin ... presented in ASCII,
Doug Ewell
- Re: A state of spin ... presented in ASCII,
Phillip Hallam-Baker
- Re: Make HTML and PDF more prominent, was: Re: Why the normative form of IETF Standards is ASCII,
Iljitsch van Beijnum
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Martin Rex
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Peter Saint-Andre
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Randy Presuhn
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Martin Rex
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Julian Reschke
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Dave Cridland
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Michael Dillon
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Yoav Nir
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Michael Dillon
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Donald Eastlake
- Message not available
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Tim Bray
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Yoav Nir
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Donald Eastlake
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Bob Braden
- Re: Make HTML and PDF more prominent, was: Re: Why the normative,
Martin Rex
- Re: Make HTML and PDF more prominent, was: Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- Re: Make HTML and PDF more prominent, was: Re: Why the normative form of IETF Standards is ASCII,
Ole Jacobsen
- Re: Make HTML and PDF more prominent, was: Re: Why the normative form of IETF Standards is ASCII,
todd glassey
- Re: Make HTML and PDF more prominent, was: Re: Why the normative form of IETF Standards is ASCII,
Michael Dillon
- Re: Why the normative form of IETF Standards is ASCII,
Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is ASCII,
Dave Cridland
- Re: Why the normative form of IETF Standards is ASCII,
Bob Braden
- Re: Why the normative form of IETF Standards is ASCII,
John R. Levine
- Re: Why the normative form of IETF Standards is ASCII,
Henning Schulzrinne
- Re: Why the normative form of IETF Standards is ASCII,
Phillip Hallam-Baker
- Re: I-Ds are not RFCs, was Why the normative form of IETF Standards,
John Levine
- Re: Why the normative form of IETF Standards is ASCII,
Andrew Sullivan
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
Re: Why the normative form of IETF Standards is ASCII,
Jorge Amodio
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Jorge Amodio
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Jorge Amodio
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
- Re: Why the normative form of IETF Standards is ASCII,
Doug Ewell
- Re: Why the normative form of IETF Standards is ASCII,
Stefan Winter
- Re: Why the normative form of IETF Standards is ASCII,
Henrik Levkowetz
- Re: Why the normative form of IETF Standards is ASCII,
Doug Ewell
- Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- Re: Why the normative form of IETF Standards is ASCII,
Doug Ewell
- Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- Re: Why the normative form of IETF Standards is ASCII,
Mark Andrews
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- Re: Why the normative form of IETF Standards is ASCII,
Doug Ewell
- Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- Re: Why the normative form of IETF Standards is ASCII,
Doug Ewell
- Re: Why the normative form of IETF Standards is ASCII,
Masataka Ohta
- Re: Why the normative form of IETF Standards is ASCII,
Jari Arkko
- Re: Why the normative form of IETF Standards is ASCII,
Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is ASCII,
Jari Arkko
- Re: Why the normative form of IETF Standards is ASCII,
Phillip Hallam-Baker
- Re: Why the normative form of IETF Standards is ASCII,
Jari Arkko
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Dave CROCKER
- Re: Why the normative form of IETF Standards is ASCII,
Tim Bray
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Doug Ewell
- Re: Why the normative form of IETF Standards is ASCII,
Tim Bray
- RE: Why the normative form of IETF Standards is ASCII,
Dearlove, Christopher (UK)
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
- Re: Why the normative form of IETF Standards is ASCII,
Stefan Santesson
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Tim Bray
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Martin Rex
- Re: Why the normative form of IETF Standards is ASCII,
Julian Reschke
- Re: Why the normative form of IETF Standards is ASCII,
Doug Ewell
- Re: Why the normative form of IETF Standards is ASCII,
Huub van Helvoort
- Re: Why the normative form of IETF Standards is ASCII,
Jorge Amodio
- RE: Why the normative form of IETF Standards is ASCII,
Eric Gray
- Re: Why the normative form of IETF Standards is ASCII,
Phillip Hallam-Baker
Re: Why the normative form of IETF Standards is ASCII,
Rich Kulawiec
Periodic debates,
Dave CROCKER
<Possible follow-ups>
Re: Why the normative form of IETF Standards is ASCII,
Ingemar Johansson S
Re: Why the normative form of IETF Standards is ASCII,
Doug Ewell
Internet Registration Bar BOF Update,
Edward Lewis
Namespace requirements, was: Last Call: draft-ietf-netmod-yang (YANG - A data modeling language for NETCONF) to Proposed Standard,
Julian Reschke
Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set,
RJ Atkinson
Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Russ Housley
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Ted Hardie
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Russ Housley
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Dave CROCKER
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
David Kessens
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Brian E Carpenter
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
ned+ietf
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
John Levine
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Bert (IETF) Wijnen
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Phillip Hallam-Baker
- Appeal Support ... was Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Olaf Kolkman
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Stephane Bortzmeyer
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Eliot Lear
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Henrik Levkowetz
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Stephen Farrell
- Re: Appeal to the IESG concerning the approbation of the IDNA2008 document set.,
SM
- Comments on appeal to the IESG concerning the approbation of the IDNA2008 document set.,
Andrew Sullivan
Re: [Isms] Last Call: draft-ietf-isms-dtls-tm (Transport Layer Security (TLS) Transport Model for SNMP) to Proposed Standard,
Robert Story
High Assurance Cryptographic API Bar BoF at IETF 77 in Anaheim, CA,
Novikov, Lev
Review of draft-ietf-geopriv-loc-filters-10.txt,
Russ Mundy
Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10,
Ben Campbell
- RE: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10,
Tschofenig, Hannes (NSN - FI/Espoo)
- Re: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10,
Ben Campbell
- RE: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10,
Thomson, Martin
- Re: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10,
Ben Campbell
- RE: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10,
Tschofenig, Hannes (NSN - FI/Espoo)
- Re: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10,
Ben Campbell
- RE: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10,
Thomson, Martin
- Re: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10,
Ben Campbell
- RE: Gen-ART LC/Tekechat Review of draft-ietf-geopriv-loc-filters-10,
Thomson, Martin
comments on draft-maglione-radext-ipv6-acct-extensions-01,
Glen Zorn
Archiving legacy text files,
Michelle Cotton
Request for input and participation,
Andrew Sullivan
Bar Bof on Federated Authentication Thursday at 9 PM during IETF week,
Sam Hartman
Re: Gen-ART review of draft-ietf-dnsext-axfr-clarify-13,
Alfred Hönes
IETFLC comments for draft-ietf-ipsecme-ikev2bis-08,
Pasi.Eronen
Re: Last Call: draft-ietf-sip-ipv6-abnf-fix (Essential correction for IPv6 ABNF and URI comparison in RFC3261) to Proposed Standard,
Brian E Carpenter
Re: REVISED Last Call: draft-turner-asymmetrickeyformat,
Alfred Hönes
Re: REVISED Last Call: draft-turner-asymmetrickeyformat (Asymmetric Key Packages) to Proposed Standard,
Cullen Jennings
Internet Registration Bar BOF announcement,
Edward Lewis
No Host for IETF 77 meeting in Anaheim, California,
IETF Chair
Re: Last Call: draft-ietf-tsvwg-port-randomization (Transport Protocol Port Randomization Recommendations) to BCP,
SM
Re: Last Call: draft-ietf-tsvwg-port-randomization (Part #1),
Alfred Hönes
Gen-ART LC/Telechat review of draft-ietf-ipfix-export-per-sctp-stream-06,
Ben Campbell
Patent disclosure in draft-shin-augmented-pake-00.txt,
Simon Josefsson
IETF Workshop on Broadband Home Gateways,
IESG Secretary
Re: [NSIS] Last Call: draft-ietf-nsis-rmd (RMD-QOSM - The Resource Management in Diffserv QOS Model) to Experimental RFC,
Gerald Ash
Mail converted by MHonArc
