IETF Discussion Archive - Thread Index

• Re: IASA NeuStar SOW Update, (continued)
  • Re: IASA NeuStar SOW Update, Steven M. Bellovin
• Re: Last call IETF experiments, Scott Bradner
  • Re: Last call IETF experiments, Brian E Carpenter
• FW: [blilly at erols.com: Re: Problem with IANA MIME media types registry], Michelle Cotton
• How security could benefit from high volume spam, Hadmut Danisch
  • Re: How security could benefit from high volume spam, Peter Dambier
  • Re: How security could benefit from high volume spam, Frank Ellermann
    • Re: How security could benefit from high volume spam, Hadmut Danisch
      • Re: How security could benefit from high volume spam, JFC (Jefsey) Morfin
      • Pro SPAM WG: How security could benefit from high volume spam, Peter Dambier
      • Re: Pro SPAM WG: How security could benefit from high volume spam, JFC (Jefsey) Morfin
  • Re: How security could benefit from high volume spam, JFC (Jefsey) Morfin
• Re: Individual submissions and Informational RFCs, Bob Braden
• [reminder] 8th IPv6 Interoperability Test Event, Yukiyo Akisada
• Fwd: Need for a rebuild [was I-D file formats and internationalization], Eduardo Mendez
• Problem with IANA MIME media types registry, Bruce Lilly
  • Re: Problem with IANA MIME media types registry, Chris Lilley
    • RE: Problem with IANA MIME media types registry, IANA
      • Re: Problem with IANA MIME media types registry, Chris Lilley
  • <Possible follow-ups>
  • Re: Problem with IANA MIME media types registry, Bruce Lilly
  • Re: Problem with IANA MIME media types registry, Laura Webster
    • Re: Problem with IANA MIME media types registry, Michelle Cotton
• Report: IETF Trust Consensus Call, Lucy E. Lynch
• Re: Last Call: 'NETCONF Configuration Protocol' to Proposed Standard, Sam Hartman
  • Re: Last Call: 'NETCONF Configuration Protocol' to Proposed Standard, Pekka Savola
  • Re: Last Call: 'NETCONF Configuration Protocol' to Proposed Standard, Eliot Lear
    • Re: Last Call: 'NETCONF Configuration Protocol' to Proposed Standard, Sam Hartman
• Any Final Comments on the IETF Trust, Lucy E. Lynch
  • <Possible follow-ups>
  • Re: Any Final Comments on the IETF Trust, Scott Bradner
• The Trust Agreement Proposal, John C Klensin
  • <Possible follow-ups>
  • The Trust Agreement Proposal, Bob Hinden
• Definition of SFTP ..., Noël, Richard
  • Re: Definition of SFTP ..., Harald Tveit Alvestrand
    • Re: Definition of SFTP ..., Frank Ellermann
    • Re: Definition of SFTP ..., Brian E Carpenter
      • Re: Definition of SFTP ..., Joseph Salowey
• IETF Trust last call, Elwyn Davies
• Examples of translated RFCs, Harald Tveit Alvestrand
  • Re: Examples of translated RFCs, JFC (Jefsey) Morfin
    • Re: Examples of translated RFCs, Masataka Ohta
      • Re: Examples of translated RFCs, JFC (Jefsey) Morfin
      • Re: Examples of translated RFCs, Masataka Ohta
      • Re: Examples of translated RFCs, Doug Ewell
      • Re: Examples of translated RFCs, Masataka Ohta
      • Re: Examples of translated RFCs, Doug Ewell
      • Re: Examples of translated RFCs, Masataka Ohta
      • off-topic? [was Re: Examples of translated RFCs], JFC (Jefsey) Morfin
      • Re: off-topic?, Frank Ellermann
      • Re: off-topic?, JFC (Jefsey) Morfin
      • IAB appeal (was: off-topic?), Frank Ellermann
      • Re: off-topic? [was Re: Examples of translated RFCs], Doug Ewell
      • Re: off-topic? [was Re: Examples of translated RFCs], Masataka Ohta
      • Re: Examples of translated RFCs, Frank Ellermann
      • Re: Examples of translated RFCs, Tim Bray
      • Re: Examples of translated RFCs, Masataka Ohta
  • Re: Examples of translated RFCs, Erik Huizer
  • <Possible follow-ups>
  • RE: Examples of translated RFCs, Nelson, David
    • Message not available
      • RE: Examples of translated RFCs, JFC (Jefsey) Morfin
  • RE: Examples of translated RFCs, Gray, Eric
  • RE: Examples of translated RFCs, Gray, Eric
• The IETF Trust License is too restricted, Simon Josefsson
  • Re: The IETF Trust License is too restricted, Brian E Carpenter
    • Re: The IETF Trust License is too restricted, Simon Josefsson
    • I know I am dumb stupid but I am also dumb stubborn [was IETF Trust license is too restricted], JFC (Jefsey) Morfin
      • Re: I know I am dumb stupid but I am also dumb stubborn [was IETF Trust license is too restricted], Brian E Carpenter
      • Re: I know I am dumb stupid but I am also dumb stubborn [was IETF Trust license is too restricted], JFC (Jefsey) Morfin
      • Re: [IAOC] I know I am dumb stupid but I am also dumb stubborn [was IETF Trust license is too restricted], Lucy E. Lynch
      • Re: [IAOC] I know I am dumb stupid but I am also dumb stubborn [was IETF Trust license is too restricted], JFC (Jefsey) Morfin
      • Re: [IAOC] I know I am dumb stupid but I am also dumb stubborn [was IETF Trust license is too restricted], Lucy E. Lynch
      • Re: [IAOC] I know I am dumb stupid but I am also dumb stubborn [was IETF Trust license is too restricted], JFC (Jefsey) Morfin
      • Re: [IAOC] I know I am dumb stupid but I am also dumb stubborn [was IETF Trust license is too restricted], Brian E Carpenter
  • Re: The IETF Trust License is too restricted, Francis Dupont
    • Re: The IETF Trust License is too restricted, Brian E Carpenter
  • Re: The IETF Trust License is too restricted, Frank Ellermann
  • <Possible follow-ups>
  • RE: The IETF Trust License is too restricted, Hallam-Baker, Phillip
    • Re: The IETF Trust License is too restricted, Brian E Carpenter
  • RE: The IETF Trust License is too restricted, Hallam-Baker, Phillip
    • Re: The IETF Trust License is too restricted, Brian E Carpenter
    • Re: The IETF Trust License is too restricted, Simon Josefsson
      • Re: The IETF Trust License is too restricted, Harald Tveit Alvestrand
      • Re: The IETF Trust License is too restricted, Simon Josefsson
      • Re: The IETF Trust License is too restricted, Sam Hartman
      • Re: The IETF Trust License is too restricted, Simon Josefsson
      • Re: The IETF Trust License is too restricted, Lucy E. Lynch
      • Re: [IAOC] Re: The IETF Trust License is too restricted, Brian E Carpenter
      • Re: [IAOC] Re: The IETF Trust License is too restricted, Simon Josefsson
      • Re: The IETF Trust License is too restricted, Simon Josefsson
      • Re: The IETF Trust License is too restricted, Lucy E. Lynch
      • Re: The IETF Trust License is too restricted, Simon Josefsson
      • Re: The IETF Trust License is too restricted, Sam Hartman
      • Re: The IETF Trust License is too restricted, Brian E Carpenter
      • Re: The IETF Trust License is too restricted, Simon Josefsson
  • RE: The IETF Trust License is too restricted, Gray, Eric
• RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Bernie Volz \(volz\)
  • RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Jeffrey Hutzelman
• draft-dnsbl-harmful-01, Daniel Feenberg
  • Re: draft-dnsbl-harmful-01, Sam Hartman
    • Re: draft-dnsbl-harmful-01, Douglas Otis
  • Re: draft-dnsbl-harmful-01, Harald Tveit Alvestrand
    • Re: draft-dnsbl-harmful-01, william(at)elan.net
• FW: I-D ACTION:draft-palet-ietf-meeting-venue-selection-criteria-02.txt, JORDI PALET MARTINEZ
• Final Update - IETF Trust Consensus Call, Lucy E. Lynch
  • Reply to IETF Trust Consensus Call, Harald Tveit Alvestrand
    • Re: Reply to IETF Trust Consensus Call, Lucy E. Lynch
• IETF vs. global politics (was RE: I-D file formats and internationalization), Nelson, David
• RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Bernie Volz \(volz\)
  • RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Jeffrey Hutzelman
• RE: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution ofFQDN Conflicts among DHCP Clients' to Proposed Standard], Bernie Volz \(volz\)
• RE: Why are we so exceptional [was: Translations of standards (was: RE: ASCII art)], Burger, Eric
  • Message not available
    • RE: Why are we so exceptional [was: Translations of standards (was: RE: ASCII art)], JFC (Jefsey) Morfin
• I-D file formats and internationalization, Robert Sayre
  • Re: I-D file formats and internationalization, Ole Jacobsen
    • Re: I-D file formats and internationalization, Eduardo Mendez
  • Re: I-D file formats and internationalization, Frank Ellermann
    • Re: I-D file formats and internationalization, Douglas Otis
      • Re: I-D file formats and internationalization, Paul Hoffman
      • Re: I-D file formats and internationalization, Douglas Otis
      • Re: I-D file formats and internationalization, Paul Hoffman
      • Re: I-D file formats and internationalization, Douglas Otis
      • Re: I-D file formats and internationalization, Paul Hoffman
      • Re: I-D file formats and internationalization, Douglas Otis
      • Re: I-D file formats and internationalization, Frank Ellermann
      • Re: I-D file formats and internationalization, Julian Reschke
      • Re: I-D file formats and internationalization, Frank Ellermann
      • Re: I-D file formats and internationalization, Frank Ellermann
      • Re: I-D file formats and internationalization, Tim Bray
      • Re: I-D file formats and internationalization, Keith Moore
      • Re: I-D file formats and internationalization, Tim Bray
      • Re: I-D file formats and internationalization, Keith Moore
  • Internationalization by ASCII art (was Re: I-D file formats and internationalization), Masataka Ohta
    • Re: Internationalization by ASCII art (was Re: I-D file formats and internationalization), Robert Sayre
  • <Possible follow-ups>
  • RE: I-D file formats and internationalization, Hallam-Baker, Phillip
    • Re: I-D file formats and internationalization, Eliot Lear
    • Re: I-D file formats and internationalization, Mark Baugher
    • Re: I-D file formats and internationalization, Jeroen Massar
      • Re: I-D file formats and internationalization, Robert Sayre
    • Message not available
      • RE: I-D file formats and internationalization, JFC (Jefsey) Morfin
    • Re: I-D file formats and internationalization, Brian E Carpenter
      • Re: I-D file formats and internationalization, Marshall Eubanks
      • Re: I-D file formats and internationalization, Brian E Carpenter
      • Re: I-D file formats and internationalization, Marshall Eubanks
      • Re: I-D file formats and internationalization, Harald Tveit Alvestrand
      • Re: I-D file formats and internationalization, Marshall Eubanks
      • Re: I-D file formats and internationalization, Frank Ellermann
      • Re: I-D file formats and internationalization, codewarrior
  • RE: I-D file formats and internationalization, Nelson, David
    • Message not available
      • RE: I-D file formats and internationalization, JFC (Jefsey) Morfin
  • RE: I-D file formats and internationalization, Bob Braden
    • Re: I-D file formats and internationalization, Robert Sayre
      • Re: I-D file formats and internationalization, Frank Ellermann
  • RE: I-D file formats and internationalization, Hallam-Baker, Phillip
    • Re: I-D file formats and internationalization, Keith Moore
    • Re: I-D file formats and internationalization, Robert Sayre
      • Re: I-D file formats and internationalization, Keith Moore
      • Re: I-D file formats and internationalization, Tim Bray
      • Re: I-D file formats and internationalization, Henrik Levkowetz
      • Re: I-D file formats and internationalization, JFC (Jefsey) Morfin
      • Re: I-D file formats and internationalization, Masataka Ohta
      • Re: I-D file formats and internationalization, JFC (Jefsey) Morfin
      • Re: I-D file formats and internationalization, Masataka Ohta
      • Re: I-D file formats and internationalization, John C Klensin
      • Re: I-D file formats and internationalization, Masataka Ohta
  • RE: I-D file formats and internationalization, Gray, Eric
    • Re: I-D file formats and internationalization, Randy.Dunlap
      • Re: I-D file formats and internationalization, Masataka Ohta
  • RE: I-D file formats and internationalization, Hallam-Baker, Phillip
    • Re: I-D file formats and internationalization, Keith Moore
      • Re: I-D file formats and internationalization, Frank Ellermann
  • RE: I-D file formats and internationalization, Gray, Eric
  • RE: I-D file formats and internationalization, Hallam-Baker, Phillip
    • Re: I-D file formats and internationalization, Ted Faber
  • Re: I-D file formats and internationalization, Noel Chiappa
  • RE: I-D file formats and internationalization, Hallam-Baker, Phillip
    • Re: I-D file formats and internationalization, Ted Faber
      • Re: I-D file formats and internationalization, JFC (Jefsey) Morfin
  • RE: I-D file formats and internationalization, Yaakov Stein
    • Re: I-D file formats and internationalization, Doug Ewell
      • Re: I-D file formats and internationalization, Henrik Levkowetz
      • Re: I-D file formats and internationalization, Douglas Otis
      • Re: I-D file formats and internationalization, Frank Ellermann
      • Re: I-D file formats and internationalization, Douglas Otis
      • Re: I-D file formats and internationalization, Paul Hoffman
    • Re: I-D file formats and internationalization, Henrik Levkowetz
  • RE: I-D file formats and internationalization, Gray, Eric
  • RE: I-D file formats and internationalization, Yaakov Stein
    • Re: I-D file formats and internationalization, Masataka Ohta
• Re: Last Call: 'Kerberized Internet Negotiation of Keys (KINK)' to Proposed Standard (fwd), Nicolas Williams
  • Re: Last Call: 'Kerberized Internet Negotiation of Keys (KINK)' to Proposed Standard (fwd), Sam Hartman
    • Re: Last Call: 'Kerberized Internet Negotiation of Keys (KINK)' to Proposed Standard (fwd), Nicolas Williams
• RE: EARLY submission deadline - Fact or Fiction?, Gray, Eric
  • Re: EARLY submission deadline - Fact or Fiction?, Dave Crocker
    • Re: EARLY submission deadline - Fact or Fiction?, Marshall Eubanks
    • Re: EARLY submission deadline - Fact or Fiction?, kent crispin
      • Re: EARLY submission deadline - Fact or Fiction?, Dave Crocker
    • Re: EARLY submission deadline - Fact or Fiction?, Joel M. Halpern
      • Re: EARLY submission deadline - Fact or Fiction?, Scott W Brim
      • Re: EARLY submission deadline - Fact or Fiction?, Brian E Carpenter
  • <Possible follow-ups>
  • RE: EARLY submission deadline - Fact or Fiction?, Gray, Eric
    • Re: EARLY submission deadline - Fact or Fiction?, Marshall Eubanks
  • RE: EARLY submission deadline - Fact or Fiction?, Gray, Eric
    • Re: EARLY submission deadline - Fact or Fiction?, Dave Crocker
  • RE: EARLY submission deadline - Fact or Fiction?, Gray, Eric
  • RE: EARLY submission deadline - Fact or Fiction?, Gray, Eric
  • RE: EARLY submission deadline - Fact or Fiction?, Gray, Eric
  • RE: EARLY submission deadline - Fact or Fiction?, Gray, Eric
  • RE: EARLY submission deadline - Fact or Fiction?, Gray, Eric
    • Re: EARLY submission deadline - Fact or Fiction?, 'Scott W Brim'
  • RE: EARLY submission deadline - Fact or Fiction?, Gray, Eric
• Re: DHCID and the use of MD5, Russ Housley
  • Re: DHCID and the use of MD5, Sam Hartman
    • Re: DHCID and the use of MD5, Russ Housley
      • Re: DHCID and the use of MD5, Sam Hartman
      • Re: DHCID and the use of MD5, Bill Fenner
      • Re: DHCID and the use of MD5, Russ Housley
  • <Possible follow-ups>
  • RE: DHCID and the use of MD5, Gray, Eric
• RE: Printing IDs and RFCs (Was: Re: ASCII art), Yaakov Stein
  • Message not available
    • RE: Printing IDs and RFCs (Was: Re: ASCII art), Geoff Huston
      • Re: Printing IDs and RFCs (Was: Re: ASCII art), Henrik Levkowetz
      • Re: Printing IDs and RFCs (Was: Re: ASCII art), Geoff Huston
  • Re: Printing IDs and RFCs (Was: Re: ASCII art), Henrik Levkowetz
  • <Possible follow-ups>
  • RE: Printing IDs and RFCs (Was: Re: ASCII art), Yaakov Stein
  • RE: Printing IDs and RFCs (Was: Re: ASCII art), Yaakov Stein
• RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution ofFQDN Conflicts among DHCP Clients' to ProposedStandard], Hallam-Baker, Phillip
  • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution ofFQDN Conflicts among DHCP Clients' to ProposedStandard], Mark Andrews
  • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution ofFQDN Conflicts among DHCP Clients' to ProposedStandard], Ted Lemon
    • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution ofFQDN Conflicts among DHCP Clients' to ProposedStandard], Sam Hartman
      • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution ofFQDN Conflicts among DHCP Clients' to ProposedStandard], David W. Hankins
  • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution ofFQDN Conflicts among DHCP Clients' to ProposedStandard], Mark Stapp
  • <Possible follow-ups>
  • RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution ofFQDN Conflicts among DHCP Clients' to ProposedStandard], Hallam-Baker, Phillip
    • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution ofFQDN Conflicts among DHCP Clients' to ProposedStandard], Douglas Otis
    • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution ofFQDN Conflicts among DHCP Clients' to ProposedStandard], Ted Lemon
  • RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution ofFQDN Conflicts among DHCP Clients' to ProposedStandard], Hallam-Baker, Phillip
    • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call:'Resolution ofFQDN Conflicts among DHCP Clients' to ProposedStandard], Mark Andrews
• RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution ofFQDN Conflicts among DHCP Clients' to Proposed Standard], Bernie Volz \(volz\)
  • RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution ofFQDN Conflicts among DHCP Clients' to Proposed Standard], Harald Tveit Alvestrand
    • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution ofFQDN Conflicts among DHCP Clients' to Proposed Standard], Ted Lemon
      • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution ofFQDN Conflicts among DHCP Clients' to Proposed Standard], Harald Tveit Alvestrand
  • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution ofFQDN Conflicts among DHCP Clients' to Proposed Standard], David W. Hankins
    • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution ofFQDN Conflicts among DHCP Clients' to Proposed Standard], Ted Lemon
• RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution ofFQDN Conflicts among DHCP Clients' to Proposed Standard], Bernie Volz \(volz\)
  • RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution ofFQDN Conflicts among DHCP Clients' to Proposed Standard], Harald Tveit Alvestrand
  • <Possible follow-ups>
  • RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution ofFQDN Conflicts among DHCP Clients' to Proposed Standard], Bernie Volz \(volz\)
  • RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution ofFQDN Conflicts among DHCP Clients' to Proposed Standard], Bernie Volz \(volz\)
• Choice of crypto, was resolution etc,, Hallam-Baker, Phillip
• Re: Reviewing the IPR Trust aggreement, Bernard Aboba
  • Re: Reviewing the IPR Trust aggreement, John C Klensin
  • Re: Reviewing the IPR Trust aggreement, Brian E Carpenter
• RE: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Bernie Volz \(volz\)
  • RE: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Pekka Savola
  • <Possible follow-ups>
  • RE: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Bernie Volz \(volz\)
    • Re: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Sam Hartman
      • Re: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], David W. Hankins
• RE: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Bernie Volz \(volz\)
• Re: grow: Last Call: 'Classless Inter-Domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan' to Proposed Standard, Pekka Savola
  • Re: grow: Last Call: 'Classless Inter-Domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan' to Proposed Standard, Joe Abley
• DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Pekka Savola
  • Re: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], David W. Hankins
    • Re: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Pekka Savola
      • Re: [dhcwg] DHCP and FQDN conflicts [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], David W. Hankins
• DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Pekka Savola
  • Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Steven M. Bellovin
    • Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Sam Hartman
      • Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Ted Lemon
      • Re: DHCID and the use of MD5, Russ Housley
      • Re: DHCID and the use of MD5, Sam Hartman
      • Re: DHCID and the use of MD5, Russ Housley
      • Re: DHCID and the use of MD5, Paul Hoffman
    • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Ted Lemon
      • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Steven M. Bellovin
      • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Mark Stapp
      • Re: [dhcwg] Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Sam Hartman
  • Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Ted Lemon
    • Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Pekka Savola
    • Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Steven M. Bellovin
      • Re: DHCID and the use of MD5 [Re: Last Call: 'Resolution of FQDN Conflicts among DHCP Clients' to Proposed Standard], Ted Lemon
• Security Area Response to Hash Function "Breaks", Russ Housley
• RE: XML2RFC submission (was Re: ASCII art), Wijnen, Bert (Bert)
  • Re: XML2RFC submission (was Re: ASCII art), Steven M. Bellovin
    • Re: XML2RFC submission (was Re: ASCII art), Bill Fenner
      • Re: XML2RFC submission (was Re: ASCII art), Steven M. Bellovin
      • Re: XML2RFC submission (was Re: ASCII art), Doug Ewell
  • <Possible follow-ups>
  • RE: XML2RFC submission (was Re: ASCII art), Wijnen, Bert (Bert)
    • Re: XML2RFC submission (was Re: ASCII art), Dave Crocker
  • RE: XML2RFC submission (was Re: ASCII art), Wijnen, Bert (Bert)
    • Re: XML2RFC submission (was Re: ASCII art), Henning Schulzrinne
    • Re: XML2RFC submission (was Re: ASCII art), Dave Crocker
      • Re: XML2RFC submission (was Re: ASCII art), Eliot Lear
      • Re: XML2RFC submission (was Re: ASCII art), Dave Crocker
      • Re: XML2RFC submission (was Re: ASCII art), Eliot Lear
      • Re: XML2RFC submission (was Re: ASCII art), Ned Freed
      • EARLY submission deadline (Re: XML2RFC submission (was Re: ASCII art)), Dave Crocker
      • Re: EARLY submission deadline (Re: XML2RFC submission (was Re: ASCII art)), Doug Royer
      • Re: EARLY submission deadline (Re: XML2RFC submission (was Re: ASCII art)), Brian E Carpenter
      • Re: EARLY submission deadline (Re: XML2RFC submission (was Re: ASCII art)), Doug Royer
      • Re: EARLY submission deadline (Re: XML2RFC submission (was Re: ASCII art)), Brian E Carpenter
      • Re: EARLY submission deadline (Re: XML2RFC submission (was Re: ASCII art)), Eliot Lear
      • Re: EARLY submission deadline (Re: XML2RFC submission (was Re: ASCII art)), Harald Tveit Alvestrand
      • Re: EARLY submission deadline (Re: XML2RFC submission (was Re: ASCII art)), Dave Crocker
      • Re: EARLY submission deadline (Re: XML2RFC submission (was Re: ASCII art)), Harald Tveit Alvestrand
      • Re: EARLY submission deadline (Re: XML2RFC submission (was Re: ASCII art)), Dave Crocker
  • RE: XML2RFC submission (was Re: ASCII art), Christian Huitema
    • Re: XML2RFC submission (was Re: ASCII art), Dave Crocker
    • Message not available
      • RE: XML2RFC submission (was Re: ASCII art), JFC (Jefsey) Morfin
  • RE: XML2RFC submission (was Re: ASCII art), Paul Hoffman
    • RE: XML2RFC submission (was Re: ASCII art), John C Klensin
      • RE: XML2RFC submission (was Re: ASCII art), Paul Hoffman
      • RE: XML2RFC submission (was Re: ASCII art), Harald Tveit Alvestrand
      • Re: XML2RFC submission (was Re: ASCII art), Brian E Carpenter
  • RE: XML2RFC submission (was Re: ASCII art), Hallam-Baker, Phillip
  • Re: XML2RFC submission (was Re: ASCII art), Bob Braden
    • Re: XML2RFC submission (was Re: ASCII art), Dave Crocker
      • Re: XML2RFC submission (was Re: ASCII art), Brian E Carpenter
      • Re: XML2RFC submission (was Re: ASCII art), John C Klensin
    • Re: XML2RFC submission (was Re: ASCII art), Marshall Rose
    • Re: XML2RFC submission (was Re: ASCII art), Ted Faber
  • RE: XML2RFC submission (was Re: ASCII art), Christian Huitema
    • Re: XML2RFC submission (was Re: ASCII art), Dave Crocker
    • Re: XML2RFC submission (was Re: ASCII art), Joe Abley
    • Re: XML2RFC submission (was Re: ASCII art), Julian Reschke
  • Re: XML2RFC submission (was Re: ASCII art), Bob Braden
    • Re: XML2RFC submission (was Re: ASCII art), Dave Crocker
    • Re: XML2RFC submission (was Re: ASCII art), Julian Reschke
    • Re: XML2RFC submission (was Re: ASCII art), Geoff Huston
    • Re: XML2RFC submission (was Re: ASCII art), Tony Hansen
      • Re: XML2RFC submission (was Re: ASCII art), Henning Schulzrinne
    • Re: XML2RFC submission (was Re: ASCII art), Jeffrey Hutzelman
      • Re: XML2RFC submission, Frank Ellermann
      • Re: XML2RFC submission, Jeffrey Hutzelman
  • RE: XML2RFC submission (was Re: ASCII art), Hallam-Baker, Phillip
    • RE: XML2RFC submission (was Re: ASCII art), Jeffrey Hutzelman
  • RE: XML2RFC submission (was Re: ASCII art), Randy Presuhn
  • Re: XML2RFC submission (was Re: ASCII art), Bob Braden
    • Re: XML2RFC submission (was Re: ASCII art), Dave Crocker
  • RE: XML2RFC submission (was Re: ASCII art), Gray, Eric
    • Re: XML2RFC submission (was Re: ASCII art), Douglas Otis
  • Re: XML2RFC submission (was Re: ASCII art), Bob Braden
• Community review requested of SOW for Secretariat and Meeting Services, Ray Pelletier
  • Re: Community review requested of SOW for Secretariat and Meeting Services, Dave Crocker
• Update: IETF Trust Consensus Call, Lucy E. Lynch
  • <Possible follow-ups>
  • Re: Update: IETF Trust Consensus Call, Scott Bradner
    • Re: Update: IETF Trust Consensus Call, Dave Crocker
      • Re: Update: IETF Trust Consensus Call, Lucy E. Lynch
  • Re: Update: IETF Trust Consensus Call, Geoff Huston
    • Re: Update: IETF Trust Consensus Call, John C Klensin
      • Re: Update: IETF Trust Consensus Call, Stephane Bortzmeyer
      • Re: Update: IETF Trust Consensus Call, John C Klensin
      • Re: Update: IETF Trust Consensus Call, Geoff Huston
      • Re: Update: IETF Trust Consensus Call, Harald Tveit Alvestrand
  • Update: IETF Trust Consensus Call, Lucy E. Lynch
• RE: Henning's proposal (Re: ASCII art), Hallam-Baker, Phillip
• Re: Last Call: 'Classless Inter-Domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan' to Proposed Standard, Tim Chown
  • <Possible follow-ups>
  • Last Call: 'Classless Inter-Domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan' to Proposed Standard, Frank Ellermann
• RE: ASCII art, Hallam-Baker, Phillip
  • <Possible follow-ups>
  • RE: ASCII art, Yaakov Stein
    • Printing IDs and RFCs (Was: Re: ASCII art), Henrik Levkowetz
  • Re: ASCII art, Dave Aronson (re IETF)
  • RE: ASCII art, Hallam-Baker, Phillip
    • Re: ASCII art, Eliot Lear
      • Re: ASCII art, Henning Schulzrinne
      • Henning's proposal (Re: ASCII art), Harald Tveit Alvestrand
      • Re: Henning's proposal (Re: ASCII art), Henning Schulzrinne
      • Re: Henning's proposal (Re: ASCII art), Ted Faber
      • Re: Henning's proposal (Re: ASCII art), Joe Touch
      • Re: Henning's proposal (Re: ASCII art), Henning Schulzrinne
      • Re: Henning's proposal (Re: ASCII art), John C Klensin
      • Re: Henning's proposal (Re: ASCII art), Tony Hansen
      • Re: Henning's proposal (Re: ASCII art), John C Klensin
      • Re: Henning's proposal (Re: ASCII art), Joe Touch
      • Re: Henning's proposal (Re: ASCII art), Harald Tveit Alvestrand
      • Re: Henning's proposal (Re: ASCII art), Bill Fenner
      • Re: ASCII art, Masataka Ohta
    • Re: ASCII art, Ted Faber
  • RE: ASCII art, Hallam-Baker, Phillip
  • RE: ASCII art, Hallam-Baker, Phillip
    • Re: ASCII art, Ted Faber
    • RE: ASCII art, Dassa
  • RE: ASCII art, Gray, Eric
    • XML2RFC submission (was Re: ASCII art), Spencer Dawkins
      • Re: XML2RFC submission (was Re: ASCII art), Dave Crocker
      • Re: XML2RFC submission (was Re: ASCII art), Henning Schulzrinne
      • Re: XML2RFC submission (was Re: ASCII art), Tony Hansen
      • Re: XML2RFC submission (was Re: ASCII art), Dave Crocker
      • Re: XML2RFC submission (was Re: ASCII art), Spencer Dawkins
      • Re: XML2RFC submission (was Re: ASCII art), Henrik Levkowetz
      • Re: XML2RFC submission (was Re: ASCII art), Spencer Dawkins
      • Re: XML2RFC submission (was Re: ASCII art), Eliot Lear
      • Re: XML2RFC submission (was Re: ASCII art), Marshall Rose
      • Re: XML2RFC submission (was Re: ASCII art), Henning Schulzrinne
      • Re: XML2RFC submission (was Re: ASCII art), Dave Crocker
      • Re: XML2RFC submission (was Re: ASCII art), John C Klensin
      • Re: XML2RFC submission (was Re: ASCII art), Douglas Otis
  • RE: ASCII art, Johnny Eriksson
  • Re: ASCII art, Yaakov Stein
    • Re: ASCII art, Stewart Bryant
• Reviewing the IPR Trust agreement (was: Re: [IAOC] Re: A couple of questions about the IETF trust outbound licensing.), John C Klensin
  • Re: Reviewing the IPR Trust agreement (was: Re: [IAOC] Re: A couple of questions about the IETF trust outbound licensing.), Lucy E. Lynch
• RE: Translations of standards (was: RE: ASCII art), Hallam-Baker, Phillip
  • RE: Translations of standards (was: RE: ASCII art), John C Klensin
    • Why are we so exceptional [was: Translations of standards (was: RE: ASCII art)], JFC (Jefsey) Morfin
• Re: [Fwd: Requirements for Open IESG Positions], Alexey Melnikov
• Last time we went to Dallas, Ole Jacobsen
  • Re: Last time we went to Dallas, Eliot Lear
  • Re: Last time we went to Dallas, Bill Sommerfeld
  • Re: Last time we went to Dallas, Theodore Ts'o
  • <Possible follow-ups>
  • RE: Last time we went to Dallas, Hallam-Baker, Phillip
• RE: RFCs should be distributed in XML (Was: Faux Pas --web public ation in proprietary formats at ietf.org, Gray, Eric
• RE: RFCs should be distributed in XML (Was: Faux Pas --web publication in proprietary formats at ietf.org, Hallam-Baker, Phillip
  • Message not available
    • RE: RFCs should be distributed in XML (Was: Faux Pas --web publication in proprietary formats at ietf.org, Lakshminath Dondeti
      • Re: RFCs should be distributed in XML (Was: Faux Pas --web publication in proprietary formats at ietf.org, Masataka Ohta
• RE: Process for Process Change (Was Diagrams ((Was RFCs should bedistributed in XML)), Hallam-Baker, Phillip
  • Re: Process for Process Change (Was Diagrams ((Was RFCs should bedistributed in XML)), Sam Hartman
    • ASCII art (was: lots of other threads), Paul Hoffman
      • Re: ASCII art, Lee Mahan
      • Re: ASCII art, Jeffrey Hutzelman
      • Re: ASCII art, Jeffrey Hutzelman
      • Re: ASCII art, Julien . Maisonneuve
      • Re: ASCII art, Paul Hoffman
      • Re: ASCII art, JFC (Jefsey) Morfin
      • Re: ASCII art, Ole Jacobsen
      • Re: ASCII art, codewarrior
      • RE: ASCII art, Thomas Gal
      • Translations of standards (was: RE: ASCII art), John C Klensin
      • Re: ASCII art, Masataka Ohta
      • RE: ASCII art, Thomas Gal
      • Language philosophy (RE: ASCII art), Harald Tveit Alvestrand
      • Re: ASCII art, Tim Bray
      • Re: ASCII art, Douglas Otis
      • Re: ASCII art, Spencer Dawkins
      • Re: ASCII art, Ted Faber
      • Re: ASCII art, Julien . Maisonneuve
      • Re: ASCII art, Stephane Bortzmeyer
      • Re: ASCII art, JFC (Jefsey) Morfin
      • Re: ASCII art, william(at)elan.net
  • <Possible follow-ups>
  • RE: Process for Process Change (Was Diagrams ((Was RFCs should bedistributed in XML)), Lars-Erik Jonsson (LU/EAB)
• RE: Diagrams, Hallam-Baker, Phillip
• Process for Process Change (Was Diagrams ((Was RFCs should be distributed in XML)), Ash, Gerald R \(Jerry\), ALABS
  • Re: Process for Process Change, Sam Hartman
    • Re: Process for Process Change, Spencer Dawkins
  • <Possible follow-ups>
  • Re: Process for Process Change (Was Diagrams ((Was RFCs should be distributed in XML)), Bob Braden
  • RE: Process for Process Change (Was Diagrams ((Was RFCs should be distributed in XML)), Gray, Eric
• RE: RFCs should be distributed in XML (Was: Faux Pas -- web publi cation in proprietary formats at ietf.org, Wijnen, Bert (Bert)
  • Re: RFCs should be distributed in XML (Was: Faux Pas -- web publi cation in proprietary formats at ietf.org, Juergen Schoenwaelder
    • Re: RFCs should be distributed in XML (Was: Faux Pas -- web publi cation in proprietary formats at ietf.org, Bill Fenner
    • Re: RFCs should be distributed in XML (Was: Faux Pas -- web publi cation in proprietary formats at ietf.org, Carsten Bormann
    • Re: RFCs should be distributed in XML (Was: Faux Pas -- web publi cation in proprietary formats at ietf.org, Julian Reschke
    • Re: RFCs should be distributed in XML (Was: Faux Pas -- web publi cation in proprietary formats at ietf.org, Anthony G. Atkielski
  • Re: RFCs should be distributed in XML (Was: Faux Pas -- web publi cation in proprietary formats at ietf.org, Henrik Levkowetz
    • Re: RFCs should be distributed in XML (Was: Faux Pas -- web publi cation in proprietary formats at ietf.org, Spencer Dawkins
      • Re: RFCs should be distributed in XML (Was: Faux Pas -- web publi cation in proprietary formats at ietf.org, Alia Atlas
      • Re: RFCs should be distributed in XML (Was: Faux Pas -- web publi cation in proprietary formats at ietf.org, Henrik Levkowetz
    • Re: RFCs should be distributed in XML (Was: Faux Pas -- web publi cation in proprietary formats at ietf.org, Cullen Jennings
• LAST Call for Nominations, NomCom05, Ralph Droms
• On revising 3777 as in draft-klensin-recall-rev-00, Lakshminath Dondeti
  • Re: On revising 3777 as in draft-klensin-recall-rev-00, Eliot Lear
    • RE: On revising 3777 as in draft-klensin-recall-rev-00, Dondeti, Lakshminath
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Eliot Lear
      • RE: On revising 3777 as in draft-klensin-recall-rev-00, Dondeti, Lakshminath
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Eliot Lear
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Scott W Brim
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Eric Rescorla
      • RE: On revising 3777 as in draft-klensin-recall-rev-00, Joel Jaeggli
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Avri Doria
    • Re: On revising 3777 as in draft-klensin-recall-rev-00, Harald Tveit Alvestrand
  • Re: On revising 3777 as in draft-klensin-recall-rev-00, John C Klensin
    • Re: On revising 3777 as in draft-klensin-recall-rev-00, Lakshminath Dondeti
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Brian E Carpenter
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Lakshminath Dondeti
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Harald Tveit Alvestrand
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Lakshminath Dondeti
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Jari Arkko
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Lakshminath Dondeti
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, John C Klensin
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Jari Arkko
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Lakshminath Dondeti
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Jari Arkko
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, John C Klensin
      • Re: On revising 3777 as in draft-klensin-recall-rev-00, Jari Arkko
  • <Possible follow-ups>
  • RE: On revising 3777 as in draft-klensin-recall-rev-00, Wijnen, Bert (Bert)
  • RE: On revising 3777 as in draft-klensin-recall-rev-00, Gray, Eric
    • Re: On revising 3777 as in draft-klensin-recall-rev-00, Randy Presuhn
  • RE: On revising 3777 as in draft-klensin-recall-rev-00, Wijnen, Bert (Bert)
• RE: Diagrams (Was RFCs should be distributed in XML), Yaakov Stein
  • Re: Diagrams (Was RFCs should be distributed in XML), Stewart Bryant
    • Re: Diagrams (Was RFCs should be distributed in XML), Dave Crocker
  • <Possible follow-ups>
  • RE: Diagrams (Was RFCs should be distributed in XML), Gray, Eric
  • RE: Diagrams (Was RFCs should be distributed in XML), Bob Braden
    • Re: Diagrams (Was RFCs should be distributed in XML), Stewart Bryant
  • Re: Diagrams (Was RFCs should be distributed in XML), Bob Braden
    • Re: Diagrams (Was RFCs should be distributed in XML), Stewart Bryant
      • Re: Diagrams (Was RFCs should be distributed in XML), kent crispin
      • Re: Diagrams (Was RFCs should be distributed in XML), Randy.Dunlap
      • Re: Diagrams (Was RFCs should be distributed in XML), Anthony G. Atkielski
      • Re: Diagrams (Was RFCs should be distributed in XML), Joe Touch
      • Re: Diagrams (Was RFCs should be distributed in XML), Gary E. Miller
      • Re: Diagrams (Was RFCs should be distributed in XML), Bill Fenner
      • Re: Diagrams (Was RFCs should be distributed in XML), Anthony G. Atkielski
    • Re: Diagrams, Frank Ellermann
  • RE: Diagrams (Was RFCs should be distributed in XML), Yaakov Stein
  • RE: Diagrams (Was RFCs should be distributed in XML), Lars-Erik Jonsson (LU/EAB)
    • Re: Diagrams (Was RFCs should be distributed in XML), Stewart Bryant