IETF Discussion

• Thread Index

• Re: As Promised, an attempt at 2026bis
  • From: Eliot Lear
• Re: As Promised, an attempt at 2026bis
  • From: Eliot Lear
• Re: As Promised, an attempt at 2026bis
  • From: Frank Ellermann
• Re: IETF-related spam from JFC Morfin
  • From: David Kessens
• Re: As Promised, an attempt at 2026bis
  • From: Sam Hartman
• Re: As Promised, an attempt at 2026bis
  • From: C. M. Heard
• Re: "zone" is not a DNS name semantic
  • From: David W. Hankins
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Ralph Droms
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: John C Klensin
• Re: As Promised, an attempt at 2026bis
  • From: John Leslie
• Re: As Promised, an attempt at 2026bis
  • From: Keith Moore
• Re: As Promised, an attempt at 2026bis
  • From: Eliot Lear
• Re: As Promised, an attempt at 2026bis
  • From: John C Klensin
• Re: As Promised, an attempt at 2026bis
  • From: Keith Moore
• Re: IETF-related spam from JFC Morfin
  • From: Tony Finch
• Re: As Promised, an attempt at 2026bis
  • From: Eliot Lear
• Re: IETF-related spam from JFC Morfin
  • From: Theodore Tso
• Re: As Promised, an attempt at 2026bis
  • From: Keith Moore
• Re: IETF-related spam from JFC Morfin
  • From: Jefsey_Morfin
• Re: As Promised, an attempt at 2026bis
  • From: Ned Freed
• Re: As Promised, an attempt at 2026bis
  • From: John C Klensin
• IETF-related spam from JFC Morfin
  • From: Tony Finch
• Re: As Promised, an attempt at 2026bis
  • From: Frank Ellermann
• Re: As Promised, an attempt at 2026bis
  • From: Sam Hartman
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Jeffrey Hutzelman
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Mark Andrews
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Jeffrey Hutzelman
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: John C Klensin
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Keith Moore
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: John C Klensin
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Matt Larson
• Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14
  • From: bmanning
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Harald Alvestrand
• "zone" is not a DNS name semantic
  • From: Dave Crocker
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Matt Larson
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: David W. Hankins
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Dave Crocker
• Re: Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Bill Fenner
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Dave Crocker
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: John C Klensin
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Dave Crocker
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Jefsey_Morfin
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: John C Klensin
• As Promised, an attempt at 2026bis
  • From: Eliot Lear
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Frank Ellermann
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Stig Venaas
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: John C Klensin
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Stig Venaas
• Re: 25th Anniversary!
  • From: Dave Crocker
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Frank Ellermann
• IDN effort has ballooned in scope without involving relevant additional review
  • From: Sam Hartman
• Re: 25th Anniversary!
  • From: Andrew G. Malis
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Fred Baker
• Re: Last Call: 'Domain Suffix Option for DHCPv6' to Proposed Standard (draft-ietf-dhc-dhcpv6-opt-dnsdomain)
  • From: Frank Ellermann
• Re: 25th Anniversary!
  • From: Ole Jacobsen
• Re: 25th Anniversary!
  • From: Andrew G. Malis
• Re: 25th Anniversary!
  • From: stephen wolff
• RE: 25th Anniversary!
  • From: Bob Braden
• RE: 25th Anniversary!
  • From: Hallam-Baker, Phillip
• Re: 25th Anniversary!
  • From: Dave Crocker
• Re: 25th Anniversary!
  • From: Jeffrey I. Schiller
• Re: 25th Anniversary!
  • From: Bob Braden
• Re: 25th Anniversary!
  • From: Noel Chiappa
• RE: Comments on draft-dusseault-caldav-15 anddraft-newman-i18n-comparator-14
  • From: Hallam-Baker, Phillip
• Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14
  • From: Harald Alvestrand
• 25th Anniversary!
  • From: rpelletier
• Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14
  • From: John C Klensin
• Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14
  • From: Frank Ellermann
• Re: Siemens to Host IETF 67
  • From: Fred Baker
• Siemens to Host IETF 67
  • From: rpelletier
• Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14
  • From: Arnt Gulbrandsen
• Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14
  • From: Lisa Dusseault
• Re: the pattern on this list (was: Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683))
  • From: Jefsey_Morfin
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: Steven M. Bellovin
• the pattern on this list (was: Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683))
  • From: Keith Moore
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: Dave Crocker
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: Harald Alvestrand
• Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14
  • From: Sam Hartman
• Re: Newtrk and ISDs
  • From: Frank Ellermann
• Out-of-Office AutoReply: I-D was expired
  • From: Ted Hardie
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: John Leslie
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: John C Klensin
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: Dave Crocker
• Re: Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14
  • From: Arnt Gulbrandsen
• Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14
  • From: Julian Reschke
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: Sam Hartman
• Re: Looking forward not back
  • From: John C Klensin
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: David Kessens
• Looking forward not back
  • From: Sam Hartman
• Re: RFC/Protocol Quantification
  • From: Frank Ellermann
• RFC/Protocol Quantification
  • From: Sreevathsa
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: Jefsey_Morfin
• RFC/Protocol Quantification
  • From: Sreevathsa
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: Theodore Tso
• Re: Newtrk and ISDs (was: Re: Facts, please not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Jefsey_Morfin
• Re: Newtrk and ISDs (was: Re: Facts, please not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Fred Baker
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: Margaret Wasserman
• Re: Last Call: 'Progressive Posting Rights Supsensions' to BCP (draft-carpenter-rescind-3683)
  • From: Sam Hartman
• Re: [Ltru] IANA XML registries
  • From: JFC Morfin
• Re: IANA XML registries
  • From: Jefsey_Morfin
• Newtrk and ISDs (was: Re: Facts, please not handwaving ...
  • From: Scott Bradner
• Newtrk and ISDs (was: Re: Facts, please not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: John C Klensin
• Re: IANA XML registries
  • From: Peter Dambier
• BCCed messages, was Re: IANA XML registries
  • From: Tony Finch
• IANA XML registries
  • From: JFC Morfin
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Sam Hartman
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Sam Hartman
• Re: The BOF wiki
  • From: Dave Crocker
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Bernard Desruisseaux
• Re: [Ltru] IANA XML registries
  • From: JFC Morfin
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Scott Bradner
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Jefsey_Morfin
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Eliot Lear
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Brian E Carpenter
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Spencer Dawkins
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Eliot Lear
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Eliot Lear
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Dave Cridland
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Brian E Carpenter
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Dave Crocker
• Re: security features.... (Re: Facts, please)
  • From: Russ Allbery
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Sam Hartman
• Re: security features.... (Re: Facts, please)
  • From: Sam Hartman
• Re: security features.... (Re: Facts, please)
  • From: Dave Cridland
• RE: security features.... (Re: Facts, please)
  • From: Gray, Eric
• Re: security features.... (Re: Facts, please)
  • From: Jeffrey Altman
• Re: security features.... (Re: Facts, please)
  • From: Harald Alvestrand
• RE: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Hallam-Baker, Phillip
• RE: security features.... (Re: Facts, please)
  • From: Hallam-Baker, Phillip
• RE: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Gray, Eric
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Dave Crocker
• Re: security features.... (Re: Facts, please)
  • From: Robert Sayre
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Brian E Carpenter
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Henning Schulzrinne
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Eliot Lear
• Re: Facts, please, not handwaving
  • From: Jefsey_Morfin
• Re: security features.... (Re: Facts, please)
  • From: Tony Finch
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Brian E Carpenter
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Julian Reschke
• security features.... (Re: Facts, please)
  • From: Harald Alvestrand
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Robert Sayre
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Russ Allbery
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Robert Sayre
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: grenville armitage
• Re: Facts, please, not handwaving
  • From: Frank Ellermann
• RE: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Hallam-Baker, Phillip
• Re: Its about mandate RE: Why cant the IETF embrace an open Election Process
  • From: Theodore Tso
• Re: Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Bill Fenner
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Jefsey_Morfin
• Re: Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Eliot Lear
• Facts, please, not handwaving [Re: Its about mandate RE: Why cant the IETF embrace an open Election Process]
  • From: Brian E Carpenter
• Re: Why cant the IETF embrace an open Election Process ratherthansome
  • From: Randy Presuhn
• Re: Flaw in the design of NoteWell makes Notewell Not Well.
  • From: Dave Crocker
• RE: Flaw in the design of NoteWell makes Notewell Not Well.
  • From: Hallam-Baker, Phillip
• Re: Flaw in the design of NoteWell makes Notewell Not Well.
  • From: Bill Strahm
• Re: Its about mandate RE: Why cant the IETF embrace an openElection Process
  • From: todd glassey
• Re: Why cant the IETF embrace an open Election Processratherthansome
  • From: todd glassey
• Re: Its about mandate RE: Why cant the IETF embrace an open Election Process
  • From: todd glassey
• Re: Its about mandate RE: Why cant the IETF embrace an open Election Process
  • From: Andy Bierman
• Re: Why cant the IETF embrace an open Election Process
  • From: todd glassey
• Flaw in the design of NoteWell makes Notewell Not Well.
  • From: todd glassey
• Re: Why cant the IETF embrace an open Election Process ratherthansome
  • From: todd glassey
• Re: Why cant the IETF embrace an open Election Process ratherthansome
  • From: todd glassey
• Its about mandate RE: Why cant the IETF embrace an open Election Process
  • From: Hallam-Baker, Phillip
• RE: Why cant the IETF embrace an open Election Process ratherthansome
  • From: Hallam-Baker, Phillip
• RE: Why cant the IETF embrace an open Election Process
  • From: Jefsey_Morfin
• RE: Why cant the IETF embrace an open Election Process
  • From: Nelson, David
• RE: Why cant the IETF embrace an open Election Process
  • From: Noel Chiappa
• Re: Specifying a state machine: ASCII-based languages
  • From: Stewart Bryant
• Re: Why cant the IETF embrace an open Election Process ratherthansome
  • From: Eliot Lear
• RE: Why cant the IETF embrace an open Election Process
  • From: Yaakov Stein
• RE: Why cant the IETF embrace an open Election Process ratherthansome
  • From: Dave Cridland
• Re: Specifying a state machine: ASCII-based languages
  • From: Stephane Bortzmeyer
• RE: Why cant the IETF embrace an open Election Process ratherthansome
  • From: Noel Chiappa
• RE: Why cant the IETF embrace an open Election Process ratherthansome
  • From: Joel M. Halpern
• RE: Why cant the IETF embrace an open Election Process ratherthansome
  • From: Hallam-Baker, Phillip
• RE: Why cant the IETF embrace an open Election Process ratherthansome
  • From: Joel M. Halpern
• RE: Why cant the IETF embrace an open Election Process ratherthansome
  • From: Hallam-Baker, Phillip
• Re: Why cant the IETF embrace an open Election Process rather thansome
  • From: Randy Presuhn
• Re: Why cant the IETF embrace an open Election Process rather than some
  • From: bmanning
• Re: Why cant the IETF embrace an open Election Process rather than some
  • From: bmanning
• Re: Specifying a state machine: ASCII-based languages
  • From: Frank Ellermann
• Re: Fw: Why cant the IETF embrace an open Election Process rather than some
  • From: Jeffrey Hutzelman
• Re: Fw: Why cant the IETF embrace an open Election Process ratherthan some
  • From: todd glassey
• Re: Specifying a state machine: ASCII-based languages
  • From: Stewart Bryant
• Re: Crisis of Faith - was Re: Adjusting the Nomcom process
  • From: todd glassey
• Re: Crisis of Faith - was Re: Adjusting the Nomcom process
  • From: todd glassey
• Re: Fw: Why cant the IETF embrace an open Election Process rather than some
  • From: Brian E Carpenter
• Re: Fw: Why cant the IETF embrace an open Election Process rather than some
  • From: Tim Chown
• Fw: Why cant the IETF embrace an open Election Process rather than some
  • From: todd glassey
• Re: Crisis of Faith - was Re: Adjusting the Nomcom process
  • From: Theodore Tso
• Re: what happened to newtrk?
  • From: Brian E Carpenter
• Re: Crisis of Faith - was Re: Adjusting the Nomcom process
  • From: Brian E Carpenter
• Re: what happened to newtrk?
  • From: Eliot Lear
• RE: what happened to newtrk?
  • From: Jeffrey Hutzelman
• RE: what happened to newtrk?
  • From: John C Klensin
• help
  • From: Sheikh, Usman Fakhar (UMKC-Student)
• Re: Specifying a state machine: ASCII-based languages
  • From: Stephane Bortzmeyer
• Re: what happened to newtrk?
  • From: Steven M. Bellovin
• RE: what happened to newtrk?
  • From: Hallam-Baker, Phillip
• Re: what happened to newtrk?
  • From: Eliot Lear
• Re: Crisis of Faith - was Re: Adjusting the Nomcom process
  • From: Fred Baker
• Re: what happened to newtrk?
  • From: John C Klensin
• Re: Please make the madness stop (was: a whole bunch of flames)
  • From: Ted Faber
• Re: Please make the madness stop (was: a whole bunch of flames)
  • From: todd glassey
• RE: Crisis of Faith - was Re: Adjusting the Nomcom process
  • From: Hallam-Baker, Phillip
• IPv6 communication
  • From: thekkayil.joy
• Please make the madness stop (was: a whole bunch of flames)
  • From: Spencer Dawkins
• Re: Todd Glassey ban -- pretty please?
  • From: Theodore Tso
• Re: Todd Glassey ban -- pretty please?
  • From: Jefsey_Morfin
• Re: Todd Glassey ban -- pretty please?
  • From: Brian E Carpenter
• Re: Todd Glassey ban -- pretty please?
  • From: Carl Malamud
• Re: Crisis of Faith - was Re: Adjusting the Nomcom process
  • From: Carl Malamud
• Re: Todd Glassey ban -- pretty please?
  • From: Jefsey_Morfin
• Re: Todd Glassey ban -- pretty please?
  • From: Sam Hartman
• Re: Constant flux (was: Why cant the IETF embrace an open ElectionProcess [...])
  • From: todd glassey
• Re: Todd Glassey ban -- pretty please?
  • From: todd glassey
• Todd Glassey ban -- pretty please?
  • From: Pekka Savola
• Re: Why cant the IETF embrace an open Election Process rather than some
  • From: todd glassey
• Constant flux (was: Why cant the IETF embrace an open Election Process [...])
  • From: Frank Ellermann
• Re: Why cant the IETF embrace an open Election Process rather than some
  • From: todd glassey
• Re: Why cant the IETF embrace an open Election Process rather than some
  • From: Rob Evans
• Re: Why cant the IETF embrace an open Election Process rather than some
  • From: todd glassey
• Re: Why cant the IETF embrace an open Election Process rather than some
  • From: todd glassey
• Re: Why cant the IETF embrace an open Election Process rather than some
  • From: Noel Chiappa
• Re: Crisis of Faith - was Re: Adjusting the Nomcom process
  • From: todd glassey
• Re: Adjusting the Nomcom process
  • From: todd glassey
• Why cant the IETF embrace an open Election Process rather than some
  • From: todd glassey
• Re: Adjusting the Nomcom process
  • From: Brian E Carpenter
• Re: Crisis of Faith - was Re: Adjusting the Nomcom process
  • From: Theodore Tso
• appeals
  • From: JFC Morfin
• Re: Crisis of Faith - was Re: Adjusting the Nomcom process
  • From: Randy Presuhn
• Re: what happened to newtrk?
  • From: Frank Ellermann
• Crisis of Faith - was Re: Adjusting the Nomcom process
  • From: todd glassey
• Re: what happened to newtrk?
  • From: John C Klensin
• Re: what happened to newtrk?
  • From: C. M. Heard
• RE: RFC 2195 (Was: what happened to newtrk?)
  • From: Hallam-Baker, Phillip
• RE: RFC 2195 (Was: what happened to newtrk?)
  • From: Ned Freed
• Re: RFC 2195 (Was: what happened to newtrk?)
  • From: Frank Ellermann
• Re: what happened to newtrk?
  • From: John C Klensin
• RE: RFC 2195 (Was: what happened to newtrk?)
  • From: Christian Huitema
• Re: Adjusting the Nomcom process
  • From: Dave Crocker
• Re: Adjusting the Nomcom process
  • From: Brian E Carpenter
• RE: RFC 2195 (Was: what happened to newtrk?)
  • From: Hallam-Baker, Phillip
• Re: Adjusting the Nomcom process
  • From: Dave Crocker
• RE: RFC 2195 (Was: what happened to newtrk?)
  • From: Jeffrey Hutzelman
• RE: RFC 2195 (Was: what happened to newtrk?)
  • From: Ned Freed
• RE: RFC 2195 (Was: what happened to newtrk?)
  • From: Hallam-Baker, Phillip
• Re: Adjusting the Nomcom process
  • From: Brian E Carpenter
• Re: RFC 2195 (Was: what happened to newtrk?)
  • From: Frank Ellermann
• Re: RFC 2195 (Was: what happened to newtrk?)
  • From: Frank Ellermann
• RE: RFC 2195 (Was: what happened to newtrk?)
  • From: Christian Huitema
• RE: RFC 2195 (Was: what happened to newtrk?)
  • From: Jeffrey Hutzelman
• Re: RFC 2195 (Was: what happened to newtrk?)
  • From: Jeffrey Hutzelman
• RE: RFC 2195 (Was: what happened to newtrk?)
  • From: Hallam-Baker, Phillip
• Re: RFC 2195 (Was: what happened to newtrk?)
  • From: Frank Ellermann
• Re: RFC 2195 (Was: what happened to newtrk?)
  • From: Frank Ellermann
• RE: RFC 2195 (Was: what happened to newtrk?)
  • From: Christian Huitema
• Re: RFC 2195 (Was: what happened to newtrk?)
  • From: Kurt D. Zeilenga
• Re: RFC 2195 (Was: what happened to newtrk?)
  • From: Jeffrey Hutzelman
• Re: what happened to newtrk?
  • From: Sam Hartman
• Re: RFC 2195 (Was: what happened to newtrk?)
  • From: Jeffrey Hutzelman
• Re: RFC 2195
  • From: Frank Ellermann
• Re: RFC 2195 (Was: what happened to newtrk?)
  • From: John C Klensin
• Re: what happened to newtrk?
  • From: Frank Ellermann
• RFC 2195 (Was: what happened to newtrk?)
  • From: Kurt D. Zeilenga
• Re: what happened to newtrk?
  • From: John C Klensin
• Re: RFC Editor RFP Responses
  • From: Marshall Eubanks
• Re: Adjusting the Nomcom process
  • From: bmanning
• Re: Adjusting the Nomcom process
  • From: bmanning
• Re: Adjusting the Nomcom process
  • From: bmanning
• Re: [mpls] Re: Last Call: 'Label Switching Router Self-Test' to Proposed Standard (draft-ietf-mpls-lsr-self-test) (2)
  • From: George Swallow
• Re: Adjusting the Nomcom process
  • From: todd glassey
• Re: Last Call: 'Label Switching Router Self-Test' to Proposed Standard (draft-ietf-mpls-lsr-self-test) (2)
  • From: Romascanu, Dan (Dan)
• RE: Adjusting the Nomcom process
  • From: Eastlake III Donald-LDE008
• Re: RFC Editor RFP Responses
  • From: Stephane Bortzmeyer
• Re: Last Call: 'Label Switching Router Self-Test' to Proposed Standard (draft-ietf-mpls-lsr-self-test)
  • From: Romascanu, Dan (Dan)
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Pekka Savola
• Re: Adjusting the Nomcom process
  • From: Pekka Savola
• Re: Adjusting the Nomcom process
  • From: Stewart Bryant
• Re: Adjusting the Nomcom process
  • From: Eliot Lear
• Re: Adjusting the Nomcom process
  • From: Ralph Droms
• RE: Adjusting the Nomcom process
  • From: Jeffrey Hutzelman
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Jefsey_Morfin
• RFC Editor RFP Responses
  • From: rpelletier
• RE: Adjusting the Nomcom process
  • From: Hallam-Baker, Phillip
• Re: Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Robert Sayre
• Re: Adjusting the Nomcom process
  • From: Ned Freed
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Robert Sayre
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Robert Sayre
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Sam Hartman
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Robert Sayre
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Sam Hartman
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Sam Hartman
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Robert Sayre
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Keith Moore
• Re: Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Robert Sayre
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Keith Moore
• Volunteer needed to serve as IANA charset reviewer
  • From: Ted Hardie
• Re: Adjusting the Nomcom process
  • From: Dave Crocker
• Re: Adjusting the Nomcom process
  • From: Eliot Lear
• RE: Adjusting the Nomcom process
  • From: Hallam-Baker, Phillip
• RE: Adjusting the Nomcom process
  • From: Hallam-Baker, Phillip
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Jefsey_Morfin
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Jefsey_Morfin
• Re: Adjusting the Nomcom process
  • From: Dave Crocker
• Re: Adjusting the Nomcom process
  • From: Ned Freed
• Re: Adjusting the Nomcom process
  • From: todd glassey
• Re: Adjusting the Nomcom process
  • From: Dave Crocker
• RE: Adjusting the Nomcom process
  • From: Hallam-Baker, Phillip
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Robert Sayre
• Re: Adjusting the Nomcom process
  • From: Brian E Carpenter
• RE: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Hallam-Baker, Phillip
• Re: Adjusting the Nomcom process
  • From: Dave Crocker
• Re: Adjusting the Nomcom process
  • From: Lars Eggert
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Keith Moore
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Robert Sayre
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Sam Hartman
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Sam Hartman
• Re: what happened to newtrk?
  • From: Frank Ellermann
• RFC 2195 (was Re: what happened to newtrk?)
  • From: Alexey Melnikov
• Re: Adjusting the Nomcom process
  • From: Brian E Carpenter
• Re: what happened to newtrk?
  • From: Eliot Lear
• Re: what happened to newtrk?
  • From: Brian E Carpenter
• Re: NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: Brian E Carpenter
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Jefsey_Morfin
• RE: what happened to newtrk?
  • From: Pasi.Eronen
• Re: Adjusting the Nomcom process
  • From: Edward Lewis
• Re: what happened to newtrk?
  • From: Brian E Carpenter
• Re: Adjusting the Nomcom process
  • From: Lars Eggert
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Brian E Carpenter
• Re: what happened to newtrk?
  • From: Frank Ellermann
• Re: Adjusting the Nomcom process
  • From: Stewart Bryant
• Decision to Reset the NomCom Process
  • From: Andrew Lange
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Robert Sayre
• Re: Last Call: 'Procedures for protocol extensions and variations'to BCP (draft-carpenter-protocol-extensions)
  • From: Randy Presuhn
• Re: what happened to newtrk?
  • From: C. M. Heard
• Re: Adjusting the Nomcom process
  • From: Sam Hartman
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Sam Hartman
• RE: NOMCOM term limits... Re: Now there seems to be lackofcommunicaiton here...
  • From: Richard Shockey
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Frank Ellermann
• Re: feed-license-08
  • From: James M Snell
• Re: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: Theodore Tso
• feed-license-08 (was: Last Call: 'Atom License Extension' to Experimental RFC (draft-snell-atompub-feed-license))
  • From: Frank Ellermann
• Re: Adjusting the Nomcom process
  • From: John C Klensin
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Jefsey_Morfin
• RE: NOMCOM term limits... Re: Now there seems to belackofcommunicaiton here...
  • From: Al Arsenault
• Re: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: Lakshminath Dondeti
• RE: Last Call: 'Procedures for protocol extensions and variations'to BCP (draft-carpenter-protocol-extensions)
  • From: Hallam-Baker, Phillip
• RE: NOMCOM term limits... Re: Now there seems to be lackofcommunicaiton here...
  • From: Hallam-Baker, Phillip
• Re: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: Sandy Wills
• Re: Adjusting the Nomcom process
  • From: Jari Arkko
• Re: Adjusting the Nomcom process
  • From: Lakshminath Dondeti
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Sam Hartman
• RE: Adjusting the Nomcom process
  • From: Hallam-Baker, Phillip
• Re: Adjusting the Nomcom process
  • From: Dave Crocker
• Re: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: Keith Moore
• Re: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: Jari Arkko
• Re: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: todd glassey
• RE: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: Hallam-Baker, Phillip
• Re: Adjusting the Nomcom process
  • From: John C Klensin
• Re: Adjusting the Nomcom process
  • From: Keith Moore
• Re: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: Keith Moore
• Re: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: Keith Moore
• Re: NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: John C Klensin
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Robert Sayre
• Re: NOMCOM term limits... Re: Now there seems to be lack of communication here...
  • From: todd glassey
• Adjusting the Nomcom process
  • From: Dave Crocker
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Jefsey_Morfin
• RE: NOMCOM term limits... Re: Now there seems to be lack of communication here...
  • From: Fleischman, Eric
• Re: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: todd glassey
• Re: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: Stewart Bryant
• Re: Last Call: 'Procedures for protocol extensions and variations' to BCP (draft-carpenter-protocol-extensions)
  • From: Sam Hartman
• Re: Now there seems to be lack of communicaiton here...
  • From: Stewart Bryant
• Re: what happened to newtrk?
  • From: Keith Moore
• RE: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: Hallam-Baker, Phillip
• Re: what happened to newtrk?
  • From: todd glassey
• Re: what happened to newtrk?
  • From: Keith Moore
• Re: NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: todd glassey
• Re: NOMCOM term limits... Re: Now there seems to be lackof communicaiton here...
  • From: todd glassey
• RE: NOMCOM term limits... Re: Now there seems to be lackofcommunicaiton here...
  • From: Hallam-Baker, Phillip
• RE: NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: Noel Chiappa
• RE: Now there seems to be lack of communicaiton here...
  • From: Eastlake III Donald-LDE008
• Re: NOMCOM term limits... Re: Now there seems to be lack ofcommunicaiton here...
  • From: Noel Chiappa
• Re: NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: Michael Thomas
• RE: NOMCOM term limits... Re: Now there seems to be lack ofcommunicaiton here...
  • From: Noel Chiappa
• Re: what happened to newtrk?
  • From: todd glassey
• Re: NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: todd glassey
• Re: NOMCOM term limits... Re: Now there seems to be lack ofcommunicaiton here...
  • From: todd glassey
• RE: NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: Hallam-Baker, Phillip
• what happened to newtrk?
  • From: Eliot Lear
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Eliot Lear
• Re: NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: John C Klensin
• RE: NOMCOM term limits... Re: Now there seems to be lack ofcommunicaiton here...
  • From: Hallam-Baker, Phillip
• Re: NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: Andrew Newton
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Thomas Narten
• Re: www.ietf.org unresponsive over IPv6?
  • From: YOSHIFUJI Hideaki / 吉藤英明
• IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Brian Carpenter
• Re: Size of pool (Was: Now there seems to be lack of communicaiton here...)
  • From: bmanning
• Re: NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: todd glassey
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Sam Hartman
• Re: NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: Bill Fenner
• NOMCOM term limits... Re: Now there seems to be lack of communicaiton here...
  • From: todd glassey
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Jefsey_Morfin
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Pekka Savola
• Re: Now there seems to be lack of communicaiton here...
  • From: Brian E Carpenter
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Brian E Carpenter
• RE: Now there seems to be lack of communicaiton here...
  • From: Hallam-Baker, Phillip
• 3797 details (was: Now there seems to be lack of communicaiton here...)
  • From: Frank Ellermann
• RE: Now there seems to be lack of communicaiton here...
  • From: Eastlake III Donald-LDE008
• Re: Now there seems to be lack of communicaiton here...
  • From: Avri Doria
• Why was the trust setup as a Va. Entity? & no FTC linkage.
  • From: todd glassey
• Re: Now there seems to be lack of communicaiton here...
  • From: Theodore Tso
• RE: Now there seems to be lack of communicaiton here...
  • From: Hallam-Baker, Phillip
• RE: Now there seems to be lack of communicaiton here...
  • From: John C Klensin
• RE: NomCom 2006/07: Selection Process Reset
  • From: Richard Shockey
• Re: Now there seems to be lack of communicaiton here...
  • From: Jeffrey Hutzelman
• RE: Now there seems to be lack of communicaiton here...
  • From: Ned Freed
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: todd glassey
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Sam Hartman
• RE: Now there seems to be lack of communicaiton here...
  • From: Eastlake III Donald-LDE008
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Pekka Savola
• IETF Meetings 68 & 69
  • From: rpelletier
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Thomas Narten
• RE: Now there seems to be lack of communicaiton here...
  • From: John C Klensin
• Re: www.ietf.org unresponsive over IPv6?
  • From: Tim Chown
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Frank Ellermann
• RE: Fixing the algorithm
  • From: Hallam-Baker, Phillip
• Re: Fixing the algorithm
  • From: todd glassey
• Re: Now there seems to be lack of communicaiton here...
  • From: Marshall Eubanks
• Re: Now there seems to be lack of communicaiton here...
  • From: Jari Arkko
• Re: www.ietf.org unresponsive over IPv6?
  • From: Jeroen Massar
• Re: www.ietf.org unresponsive over IPv6?
  • From: Tim Chown
• Re: IESG response and questions to the normative reference experiment (draft-klensin-norm-ref-01.txt)
  • From: Jefsey_Morfin
• RE: Fixing the algorithm
  • From: Yaakov Stein
• Re: www.ietf.org unresponsive over IPv6?
  • From: Jeroen Massar
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Julian Reschke
• Re: Now there seems to be lack of communicaiton here...
  • From: Brian E Carpenter
• www.ietf.org unresponsive over IPv6?
  • From: Tim Chown
• RE: Now there seems to be lack of communicaiton here...
  • From: Yaakov Stein
• Re: Now there seems to be lack of communicaiton here...
  • From: Brian E Carpenter
• Re: Now there seems to be lack of communicaiton here...
  • From: Brian E Carpenter
• Re: NomCom 2006/07: Selection Process Reset
  • From: Brian E Carpenter
• Re: NomCom 2006/07: Selection Process Reset
  • From: Harald Alvestrand
• Re: NomCom 2006/07: Selection Process Reset
  • From: Marshall Eubanks
• RE: Now there seems to be lack of communicaiton here...
  • From: Richard Shockey
• Size of pool (Was: Now there seems to be lack of communicaiton here...)
  • From: Ole Jacobsen
• Re: Now there seems to be lack of communicaiton here...
  • From: Scott Bradner
• Re: Now there seems to be lack of communicaiton here...
  • From: Dave Crocker
• RE: Now there seems to be lack of communicaiton here...
  • From: Richard Shockey
• Re: Now there seems to be lack of communicaiton here...
  • From: Scott Bradner
• Re: Now there seems to be lack of communicaiton here...
  • From: Joel M. Halpern
• Fixing the algorithm
  • From: Hallam-Baker, Phillip
• Re: Now there seems to be lack of communicaiton here...
  • From: Theodore Tso
• RE: Now there seems to be lack of communicaiton here...
  • From: Jefsey_Morfin
• Re: Now there seems to be lack of communicaiton here...
  • From: todd glassey
• Re: Now there seems to be lack of communicaiton here...
  • From: todd glassey
• Re: Now there seems to be lack of communicaiton here...
  • From: todd glassey
• Re: Now there seems to be lack of communicaiton here...
  • From: Pete Resnick
• RE: Now there seems to be lack of communicaiton here...
  • From: Hallam-Baker, Phillip
• RE: Now there seems to be lack of communicaiton here...
  • From: Eastlake III Donald-LDE008
• Re: Now there seems to be lack of communicaiton here...
  • From: Jeffrey Hutzelman
• Re: Now there seems to be lack of communicaiton here...
  • From: John C Klensin
• Re: Now there seems to be lack of communicaiton here...
  • From: Eliot Lear
• RE: Now there seems to be lack of communicaiton here...
  • From: Michael StJohns
• Re: Now there seems to be lack of communicaiton here...
  • From: Michael StJohns
• Re: NomCom 2006/07: Selection Process Reset
  • From: John Leslie
• RE: Now there seems to be lack of communicaiton here...
  • From: Eastlake III Donald-LDE008
• RE: Now there seems to be lack of communicaiton here...
  • From: Cimbala, Matthew
• Re: Now there seems to be lack of communicaiton here...
  • From: Randy Presuhn
• Re: Now there seems to be lack of communicaiton here...
  • From: Eliot Lear
• Re: Now there seems to be lack of communicaiton here...
  • From: todd glassey
• Re: Now there seems to be lack of communicaiton here...
  • From: James Galvin
• Re: Now there seems to be lack of communicaiton here...
  • From: Dave Crocker
• Re: Now there seems to be lack of communicaiton here...
  • From: Stewart Bryant
• Re: Now there seems to be lack of communicaiton here...
  • From: James Galvin
• Re: Now there seems to be lack of communicaiton here...
  • From: Dave Crocker
• Re: Now there seems to be lack of communicaiton here...
  • From: todd glassey
• Re: Now there seems to be lack of communicaiton here...
  • From: Henrik Levkowetz
• Re: Now there seems to be lack of communicaiton here...
  • From: James Galvin
• RE: Now there seems to be lack of communicaiton here...
  • From: Richard Shockey
• Re: Now there seems to be lack of communicaiton here...
  • From: Dave Crocker
• Re: Now there seems to be lack of communicaiton here...
  • From: Leslie Daigle
• Re: Last call comment on 'XML Pipelining with Chunks for the
  • From: Andrew Newton
• Re: Now there seems to be lack of communicaiton here...
  • From: Jeffrey Hutzelman
• RE: Now there seems to be lack of communicaiton here...
  • From: Eastlake III Donald-LDE008
• Re: Now there seems to be lack of communicaiton here...
  • From: todd glassey
• Re: Now there seems to be lack of communicaiton here...
  • From: Michael StJohns
• Re: Now there seems to be lack of communicaiton here...
  • From: Ted Hardie
• Re: Now there seems to be lack of communicaiton here...
  • From: Ned Freed
• RE: Now there seems to be lack of communicaiton here...
  • From: Hallam-Baker, Phillip
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Cyrus Daboo
• Last call comment on 'XML Pipelining with Chunks for the
  • From: Rick Jelliffe
• RE: Now there seems to be lack of communicaiton here...
  • From: Richard Shockey
• RE: Now there seems to be lack of communicaiton here...
  • From: Lars-Erik Jonsson (LU/EAB)
• Re: Now there seems to be lack of communicaiton here...
  • From: Hallam-Baker, Phillip
• Re: Now there seems to be lack of communicaiton here...
  • From: Hallam-Baker, Phillip
• Re: Now there seems to be lack of communicaiton here...
  • From: Eliot Lear
• Re: Now there seems to be lack of communicaiton here...
  • From: Brian E Carpenter
• Re: Now there seems to be lack of communicaiton here...
  • From: Brian E Carpenter
• Re: Now there seems to be lack of communicaiton here...
  • From: Brian E Carpenter
• RE: Now there seems to be lack of communicaiton here...
  • From: Henk Uijterwaal
• RE: Now there seems to be lack of communicaiton here...
  • From: Michael StJohns
• RE: Now there seems to be lack of communicaiton here...
  • From: Hallam-Baker, Phillip
• Re: Now there seems to be lack of communicaiton here...
  • From: Michael StJohns
• What is going on with the NOMCOM
  • From: Richard Shockey
• Now there seems to be lack of communicaiton here...
  • From: Richard Shockey
• Resend: RE: What is going on with the NOMCOM
  • From: Richard Shockey
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Robert Sayre
• Last Call: 'Procedures for protocol extensions and, variations' to BCP
  • From: Elwyn Davies
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Julian Reschke
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Lisa Dusseault
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Julian Reschke
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Bernard Desruisseaux
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Julian Reschke
• Re: Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Robert Sayre
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Bernard Desruisseaux
• Re: Measurements at IETF65.
  • From: Joel Jaeggli
• Re: Measurements at IETF65.
  • From: Andrea G Forte
• I'm looking for Pacific Islanders on the IETF
  • From: Franck Martin
• Measurements at IETF65.
  • From: Andrea G Forte
• Re: Last Call: 'Calendaring Extensions to WebDAV (CalDAV)' to Proposed Standard (draft-dusseault-caldav)
  • From: Julian Reschke
• Re: One Mistake and One Question of RFC2812.
  • From: Brian E Carpenter
• RE: Last Call: 'Requirements for Multicast in L3 Provider-Provisioned VPNs' to Informational RFC (draft-ietf-l3vpn-ppvpn-mcast-reqts)
  • From: benjamin.niven-jenkins
• One Mistake and One Question of RFC2812.
  • From: huangxiangkui
• Re: [midcom] RE: Last Call: 'Definitions of Managed Objects for Middlebox Communication' to Proposed Standard (draft-ietf-midcom-mib)
  • From: Pyda Srisuresh
• Re: [Fwd: IETF Process discussions - next steps]
  • From: Frank Ellermann
• Re: [Fwd: IETF Process discussions - next steps]
  • From: Eliot Lear
• Re: [Fwd: IETF Process discussions - next steps]
  • From: Frank Ellermann
• Re: [Fwd: IETF Process discussions - next steps]
  • From: Eliot Lear
• Re: [Fwd: IETF Process discussions - next steps]
  • From: Frank Ellermann
• Re: [Fwd: IETF Process discussions - next steps]
  • From: Andy Bierman
• RE: [Fwd: IETF Process discussions - next steps]
  • From: Hallam-Baker, Phillip
• [Fwd: IETF Process discussions - next steps]
  • From: Brian E Carpenter
• Re: [Ltru] Re: WG Review: Recharter of Language Tag Registry Update (ltru)
  • From: Harald Alvestrand
• Two other RFCs to be published as Historic (was Re: Expedited Handling Request for draft-ietf-ltru-registry, draft-ietf-ltru-matching, and draft-ietf-ltru-initial)
  • From: Jefsey_Morfin
• Re: WG Review: Recharter of Language Tag Registry Update (ltru)
  • From: Doug Ewell
• Re: Last Call: 'Atom License Extension' to Experimental RFC (draft-snell-atompub-feed-license)
  • From: James M Snell
• Re: Last Call: 'Atom License Extension' to Experimental RFC (draft-snell-atompub-feed-license)
  • From: Frank Ellermann
• Train to San Diego (was 'Meetings in other regions')
  • From: Randall Gellens
• Re: L2VPNs must not be IP(v4)-only
  • From: Keith Moore
• Re: L2VPNs must not be IP(v4)-only
  • From: Hallam-Baker, Phillip
• Re: L2VPNs must not be IP(v4)-only
  • From: Keith Moore
• Re: L2VPNs must not be IP(v4)-only
  • From: Hallam-Baker, Phillip
• Deploying v6 was: L2VPNs must not be IP(v4)-only
  • From: Hallam-Baker, Phillip
• Re: Last Call: 'Atom License Extension' to Experimental RFC (draft-snell-atompub-feed-license)
  • From: James M Snell
• RE: L2VPNs must not be IP(v4)-only
  • From: Shah, Himanshu
• knowing the technical background (was: Re: L2VPNs must not be IP(v4)-only)
  • From: JFC Morfin
• Re: L2VPNs must not be IP(v4)-only
  • From: Keith Moore
• Re: Meetings in other regions
  • From: Marshall Eubanks
• Taxi LAX-SAN (was 'Meetings in other regions')
  • From: Randall Gellens
• Re: Meetings in other regions
  • From: Randall Gellens
• RE: RFC 4612 - historic status
  • From: Paul E. Jones
• Re: Meetings in other regions
  • From: Randall Gellens
• Re: L2VPNs must not be IP(v4)-only
  • From: Elwyn Davies
• Re: L2VPNs must not be IP(v4)-only
  • From: Keith Moore
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the I nternet Registry Information Service' to Proposed Standard (draft-ietf-cr isp-iris-lwz)
  • From: Andrew Newton
• Announcement of mailing list for pre-congestion notification (PCN)
  • From: Bruce Davie
• Re: L2VPNs must not be IP(v4)-only
  • From: Noel Chiappa
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the I nternet Registry Information Service' to Proposed Standard (draft-ietf-cr isp-iris-lwz)
  • From: Sam Hartman
• Re: L2VPNs must not be IP(v4)-only
  • From: Keith Moore
• RE: Last Call: 'A Lightweight UDP Transfer Protocol for the the I nternet Registry Information Service' to Proposed Standard (draft-ietf-cr isp-iris-lwz)
  • From: Gray, Eric
• Re: L2VPNs must not be IP(v4)-only
  • From: Shane Amante
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Sam Hartman
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Mark Townsley
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Harald Alvestrand
• L2VPNs must not be IP(v4)-only
  • From: Pekka Savola
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Ned Freed
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Andrew Newton
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Randy Presuhn
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Ted Faber
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Ted Faber
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Todd Glassey
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: william(at)elan.net
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Harald Alvestrand
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Andrew Newton
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Lars Eggert
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: kent crispin
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Sam Hartman
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Andrew Newton
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Andrew Newton
• Re: Last Call: 'Atom License Extension' to Experimental RFC (draft-snell-atompub-feed-license)
  • From: James M Snell
• Re: RFP Question for you Jorge... did anyone put a notice of "Responsibility for Copyright Violations" to the Publisher RFP Candidates?
  • From: Todd Glassey
• Re: Last Call: 'Atom License Extension' to Experimental RFC (draft-snell-atompub-feed-license)
  • From: Frank Ellermann
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Frank Ellermann
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Frank Ellermann
• Re: RFC 4612 - historic status
  • From: Dave Crocker
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Sam Hartman
• RFP and BCP addition - receipt needs to be generated & RFC's that revise IETF process.
  • From: todd glassey
• Re: draft-jennings-impp-vcard-07
  • From: Julian Reschke
• Re: ID Tracker State Update Notice: draft-laganier-ipv6-khi
  • From: julien . laganier
• re: administrative question on RFC publications
  • From: Joyce Reynolds
• Re: New Version Notification - draft-laganier-ipv6-khi-04.txt
  • From: julien . laganier
• draft-jennings-impp-vcard-07
  • From: Brian Suda
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Ted Hardie
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Marcos Sanz/Denic
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Andrew Newton
• Re: Last Call: 'Atom License Extension' to Experimental RFC (draft-snell-atompub-feed-license)
  • From: James M Snell
• Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
  • From: Frank Ellermann
• Re: Last Call: 'Atom License Extension' to Experimental RFC (draft-snell-atompub-feed-license)
  • From: Frank Ellermann
• Re: RFC 4612 - historic status
  • From: Brian E Carpenter
• Re: RFC 4612 - historic status
  • From: Frank Ellermann
• Autoreply: away from desk
  • From: Olaf M. Kolkman
• re: administrative question on RFC publications
  • From: JFC Morfin
• RFP Question for you Jorge... did anyone put a notice of "Responsibility for Copyright Violations" to the Publisher RFP Candidates?
  • From: todd glassey
• Re: RFC 4612 - historic status
  • From: Dave Crocker