IETF Discussion

• Thread Index

• Re: [IETF] The death John McCarthy - LISP, HIP & GSE
  • From: Nathaniel Borenstein
• Gen-ART LC review of draft-ietf-csi-dhcpv6-cga-ps-07
  • From: Roni Even
• Gen-ART LC review of draft-ietf-appsawg-rfc3462bis-02
  • From: Roni Even
• Re: LISP is not a Loc-ID Separation protocol
  • From: Noel Chiappa
• Re: The death John McCarthy - LISP, HIP & GSE
  • From: Robin Whittle
• Re: The death John McCarthy - LISP, HIP & GSE
  • From: Jari Arkko
• Re: LISP is not a Loc-ID Separation protocol
  • From: Robin Whittle
• Re: [rfc-i] From Pandoc To RFC
  • From: John C Klensin
• Re: Last Calls: [SOME RFCs] to HISTORIC RFCs
  • From: Michael StJohns
• Re: LISP is not a Loc-ID Separation protocol
  • From: Masataka Ohta
• Re: [rfc-i] From Pandoc To RFC
  • From: Marshall Eubanks
• Re: LISP is not a Loc-ID Separation protocol
  • From: Robin Whittle
• Re: [rfc-i] From Pandoc To RFC
  • From: Russ Housley
• RE: LISP is not a Loc-ID Separation protocol
  • From: John E Drake
• Gen-ART review of draft-ietf-vcarddav-kind-app-00
  • From: Roni Even
• Gen-ART LC review of draft-ietf-mip4-nemo-haaro-06
  • From: Roni Even
• Re: From Pandoc To RFC
  • From: Carsten Bormann
• Re: Last Calls: [SOME RFCs] to HISTORIC RFCs
  • From: t.petch
• From Pandoc To RFC
  • From: Olaf Kolkman
• Re: LISP is not a Loc-ID Separation protocol
  • From: Robin Whittle
• Re: LISP is not a Loc-ID Separation protocol
  • From: Masataka Ohta
• LISP is not a Loc-ID Separation protocol
  • From: Robin Whittle
• Re: [IETF] The death John McCarthy - LISP, HIP & GSE
  • From: Doug Barton
• Re: [IETF] The death John McCarthy - LISP, HIP & GSE
  • From: Robin Whittle
• Re: Last Call: <draft-salter-rfc5430bis-01.txt> (Suite B Profile for Transport Layer Security (TLS)) to Informational RFC
  • From: Nikos Mavrogiannopoulos
• Re: Virtual Water Coolers
  • From: Brian E Carpenter
• Re: The death John McCarthy
  • From: Randy Bush
• Re: Last Calls: [SOME RFCs] to HISTORIC RFCs
  • From: Andrew G. Malis
• Re: [IETF] Re: Last Call: RFC 802 (ARPANET 1822L Host Access Protocol) to HISTORIC RFC
  • From: Andrew G. Malis
• RE: Last Calls: [SOME RFCs] to HISTORIC RFCs
  • From: Ronald Bonica
• Re: Last Calls: [SOME RFCs] to HISTORIC RFCs
  • From: Randy Bush
• Re: Nomcom
  • From: Suresh Krishnan
• Re: What? This thread is talking about *voting* now?
  • From: Suresh Krishnan
• Re: The death John McCarthy
  • From: John C Klensin
• Re: The death John McCarthy
  • From: Bob Hinden
• Re: The death John McCarthy
  • From: Bob Hinden
• Re: Virtual Water Coolers
  • From: Dave Cridland
• Re: The death John McCarthy
  • From: Paul Hoffman
• Re: The death John McCarthy
  • From: ned+ietf
• Re: Last Calls: [SOME RFCs] to HISTORIC RFCs
  • From: Frank Ellermann
• Re: Virtual Water Coolers
  • From: Richard L. Barnes
• Re: Last Calls: [SOME RFCs] to HISTORIC RFCs
  • From: Randy Bush
• Re: Last Calls: [SOME RFCs] to HISTORIC RFCs
  • From: Russ Housley
• Re: [IETF] The death John McCarthy - LISP, HIP & GSE
  • From: Luigi Iannone
• Re: TICC restrictions on food/beverage
  • From: John C Klensin
• Re: [IETF] The death John McCarthy - LISP, HIP & GSE
  • From: Robin Whittle
• Acronyms for Locator/ID Separation Protocol
  • From: Hector
• Re: Requirement to go to meetings
  • From: Donald Eastlake
• Re: The death John McCarthy - LISP, HIP & GSE
  • From: Luigi Iannone
• Re: Requirement to go to meetings
  • From: Ray Bellis
• Re: The death John McCarthy - LISP, HIP & GSE
  • From: Robin Whittle
• Re: The death John McCarthy
  • From: Luigi Iannone
• Re: Virtual Water Coolers
  • From: Dave Cridland
• Re: The death John McCarthy
  • From: Hector
• Re: The death John McCarthy
  • From: Jari Arkko
• Re: Last Calls: [SOME RFCs] to HISTORIC RFCs
  • From: Michael StJohns
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Misnamed WGs, e.g. LISP != Loc/ID Split
  • From: Robin Whittle
• Last Calls: [SOME RFCs] to HISTORIC RFCs
  • From: Mykyta Yevstifeyev
• Re: The death John McCarthy
  • From: Joel jaeggli
• Re: The death John McCarthy
  • From: Benson Schliesser
• Re: TICC restrictions on food/beverage
  • From: Pete Resnick
• Re: Last Call: RFC 802 (ARPANET 1822L Host Access Protocol) to HISTORIC RFC
  • From: Scott Brim
• Re: The death John McCarthy
  • From: Dave CROCKER
• Re: The death John McCarthy
  • From: John C Klensin
• Re: The death John McCarthy
  • From: Melinda Shore
• Re: The death John McCarthy
  • From: Terry Manderson
• Re: The death John McCarthy
  • From: Margaret Wasserman
• Re: The death John McCarthy
  • From: Hector
• Re: Requirement to go to meetings
  • From: Richard Kulawiec
• Re: Requirement to go to meetings
  • From: John C Klensin
• Re: The death John McCarthy
  • From: Noel Chiappa
• Re: The death John McCarthy
  • From: Noel Chiappa
• Re: The death John McCarthy
  • From: Brian E Carpenter
• Re: The death John McCarthy
  • From: John C Klensin
• Re: Last Call: RFC 802 (ARPANET 1822L Host Access Protocol) to HISTORIC RFC
  • From: Ole Jacobsen
• Re: The death John McCarthy
  • From: Eliot Lear
• The death John McCarthy
  • From: Bob Hinden
• Re: Last Call: RFC 802 (ARPANET 1822L Host Access Protocol) to HISTORIC RFC
  • From: Andrew G. Malis
• Re: Last Call: RFC 802 (ARPANET 1822L Host Access Protocol) to HISTORIC RFC
  • From: Ole Jacobsen
• Re: Last Call: <draft-salter-rfc5430bis-01.txt> (Suite B Profile for
  • From: Martin Rex
• Re: TICC restrictions on food/beverage
  • From: Brian E Carpenter
• TICC restrictions on food/beverage
  • From: John C Klensin
• Further off topic - providing Nomcom feedback and TICC restrictions on food/beverage (was "this thread is talking about *voting* now?"
  • From: Mary Barnes
• Re: Last Call: <draft-salter-rfc5430bis-01.txt> (Suite B Profile for Transport Layer Security (TLS)) to Informational RFC
  • From: Russ Housley
• Re: What? This thread is talking about *voting* now?
  • From: SM
• Re: Last Call: <draft-salter-rfc5430bis-01.txt> (Suite B Profile for Transport Layer Security (TLS)) to Informational RFC
  • From: Nikos Mavrogiannopoulos
• Re: Last Call: <draft-salter-rfc5430bis-01.txt> (Suite B Profile for Transport Layer Security (TLS)) to Informational RFC
  • From: Russ Housley
• Re: Last Call: <draft-salter-rfc5430bis-01.txt> (Suite B Profile for Transport Layer Security (TLS)) to Informational RFC
  • From: Nikos Mavrogiannopoulos
• Re: Gen-ART Last Call review of draft-ietf-cuss-sip-uui-reqs-06
  • From: Alan Johnston
• Re: What? This thread is talking about *voting* now?
  • From: Randy Bush
• RE: Requirement to go to meetings
  • From: Ross Callon
• Re: Requirement to go to meetings
  • From: Fred Baker
• Nomcom (was: Re: Requirement to go to meetings)
  • From: John C Klensin
• Re: Requirement to go to meetings
  • From: Paul Hoffman
• Re: Requirement to go to meetings
  • From: Dave CROCKER
• Re: Requirement to go to meetings
  • From: Margaret Wasserman
• Re: Requirement to go to meetings
  • From: Fred Baker
• Re: Requirement to go to meetings
  • From: Mary Barnes
• Re: Requirement to go to meetings
  • From: SM
• Re: What? This thread is talking about *voting* now?
  • From: Bob Hinden
• Re: Requirement to go to meetings
  • From: Martin Sustrik
• Re: Requirement to go to meetings
  • From: Melinda Shore
• What? This thread is talking about *voting* now?
  • From: Brian E Carpenter
• Re: Requirement to go to meetings
  • From: Dave CROCKER
• RE: Requirement to go to meetings
  • From: Ross Callon
• Re: Requirement to go to meetings
  • From: Mary Barnes
• Re: Requirement to go to meetings
  • From: John Leslie
• Re: Requirement to go to meetings
  • From: Peter Saint-Andre
• Re: Requirement to go to meetings
  • From: Fred Baker
• Re: Requirement to go to meetings
  • From: t.petch
• RE: Requirement to go to meetings
  • From: Christer Holmberg
• Re: Requirement to go to meetings
  • From: Peter Saint-Andre
• Re: Requirement to go to meetings
  • From: Donald Eastlake
• Re: Requirement to go to meetings
  • From: Peter Saint-Andre
• Re: Requirement to go to meetings
  • From: Dave Cridland
• Re: Requirement to go to meetings
  • From: John C Klensin
• Re: [Fecframe] Last Call: <draft-ietf-fecframe-rtp-raptor-05.txt> (RTP Payload Format for Raptor FEC) to Proposed Standard
  • From: Vincent Roca
• Re: TSVDIR review of draft-ietf-pim-port-08.txt
  • From: Stig Venaas
• Gen-ART review of draft-ietf-6man-rpl-routing-header-04.txt
  • From: Miguel A. Garcia
• Re: Requirement to go to meetings
  • From: Fred Baker
• Re: Requirement to go to meetings
  • From: Ping Pan
• RE: Anotherj RFP without IETF community input
  • From: Dearlove, Christopher (UK)
• Re: Requirement to go to meetings
  • From: John Leslie
• Re: Requirement to go to meetings
  • From: t.petch
• Re: Requirement to go to meetings
  • From: t.petch
• Re: DKIM delays
  • From: t.petch
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Yoshinori Koike
• RE: Requirement to go to meetings
  • From: Robin Uyeshiro
• Re: DKIM delays
  • From: Russ Housley
• Re: Requirement to go to meetings
  • From: Melinda Shore
• Re: Requirement to go to meetings
  • From: Michael Richardson
• Re: [pim] Last Call: <draft-ietf-pim-port-08.txt> (A Reliable TransportMechanism for PIM) to Experimental RFC
  • From: Stig Venaas
• Re: Requirement to go to meetings
  • From: Thomas Nadeau
• Re: Requirement to go to meetings
  • From: SM
• Re: Anotherj RFP without IETF community input
  • From: Mikael Abrahamsson
• Re: DKIM delays
  • From: Alessandro Vesely
• Re: Requirement to go to meetings
  • From: Peter Saint-Andre
• Re: Requirement to go to meetings
  • From: Spencer Dawkins
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• Re: Requirement to go to meetings
  • From: Peter Saint-Andre
• Re: Requirement to go to meetings
  • From: Spencer Dawkins
• Re: Requirement to go to meetings
  • From: Peter Saint-Andre
• Re: Anotherj RFP without IETF community input
  • From: Marshall Eubanks
• Re: Anotherj RFP without IETF community input
  • From: John Leslie
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: JP Vasseur
• RE: Gen-ART review of draft-ietf-geopriv-policy-uri-02
  • From: david.black
• Gen-ART review of draft-ietf-geopriv-policy-uri-02
  • From: david.black
• Gen-ART LC Review of draft-ietf-avtcore-srtp-vbr-audio-03
  • From: Ben Campbell
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (TheReasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: Ersue, Mehmet (NSN - DE/Munich)
• Re: Requirement to go to meetings
  • From: Michael Richardson
• Re: Requirement to go to meetings
  • From: Dave CROCKER
• Re: Anotherj RFP without IETF community input
  • From: Marshall Eubanks
• Re: Anotherj RFP without IETF community input
  • From: Mikael Abrahamsson
• Re: Anotherj RFP without IETF community input
  • From: John Leslie
• RE: Requirement to go to meetings
  • From: Christer Holmberg
• Re: Requirement to go to meetings
  • From: Joel jaeggli
• Re: Requirement to go to meetings
  • From: Marshall Eubanks
• Re: Requirement to go to meetings
  • From: Thomas Nadeau
• Re: Requirement to go to meetings
  • From: Marshall Eubanks
• Re: Requirement to go to meetings
  • From: John Leslie
• Re: Requirement to go to meetings
  • From: Kevin Smith
• Re: Requirement to go to meetings
  • From: Dave CROCKER
• Re: Anotherj RFP without IETF community input
  • From: Henk Uijterwaal
• RE: Requirement to go to meetings
  • From: Murray S. Kucherawy
• Re: Requirement to go to meetings
  • From: Joel jaeggli
• Re: Requirement to go to meetings
  • From: Robert Raszuk
• Re: Requirement to go to meetings
  • From: Randy Bush
• Re: Requirement to go to meetings
  • From: Mikael Abrahamsson
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Shane Amante
• Re: Requirement to go to meetings
  • From: Peter Saint-Andre
• Re: Requirement to go to meetings
  • From: Henning Schulzrinne
• Re: Requirement to go to meetings
  • From: Joel jaeggli
• Re: Requirement to go to meetings
  • From: Andrew Allen
• Re: Requirement to go to meetings
  • From: Sam Hartman
• Re: Requirement to go to meetings
  • From: Yoav Nir
• Re: Requirement to go to meetings
  • From: Donald Eastlake
• Re: Requirement to go to meetings
  • From: Tim Chown
• Re: Requirement to go to meetings
  • From: Cullen Jennings
• Re: Requirement to go to meetings
  • From: Michal Krsek
• Re: Requirement to go to meetings
  • From: Loa Andersson
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Loa Andersson
• Re: Requirement to go to meetings
  • From: Melinda Shore
• Re: Requirement to go to meetings
  • From: Randy Bush
• Re: Requirement to go to meetings
  • From: Randy Bush
• Re: Requirement to go to meetings
  • From: Stephen Farrell
• RE: Requirement to go to meetings
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• Re: Requirement to go to meetings
  • From: Loa Andersson
• Re: Requirement to go to meetings
  • From: Cullen Jennings
• Re: Gen-ART review of draft-ietf-eai-rfc5335bis-12
  • From: ned+ietf
• Re: Requirement to go to meetings
  • From: Stephen Farrell
• Re: Requirement to go to meetings
  • From: Cullen Jennings
• Re: Requirement to go to meetings
  • From: Marshall Eubanks
• Re: Requirement to go to meetings
  • From: Marc Petit-Huguenin
• Re: Gen-ART review of draft-ietf-eai-rfc5335bis-12
  • From: John C Klensin
• RE: Requirement to go to meetings
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• Re: Requirement to go to meetings
  • From: Melinda Shore
• Re: Requirement to go to meetings
  • From: Scott Brim
• Re: Requirement to go to meetings
  • From: Dave CROCKER
• RE: Requirement to go to meetings (was: Re: Anotherj RFP without IETF community input)
  • From: John C Klensin
• Re: Requirement to go to meetings
  • From: John C Klensin
• Re: Requirement to go to meetings (was: Re: Anotherj RFP without IETF community input)
  • From: Marshall Eubanks
• Re: Requirement to go to meetings
  • From: Eric Burger
• RE: Requirement to go to meetings (was: Re: Anotherj RFP without IETF community input)
  • From: Murray S. Kucherawy
• Re: Requirement to go to meetings
  • From: Ping Pan
• Re: Requirement to go to meetings
  • From: Eric Burger
• Requirement to go to meetings (was: Re: Anotherj RFP without IETF community input)
  • From: Dave CROCKER
• Re: Gen-ART review of draft-ietf-eai-rfc5335bis-12
  • From: Dave CROCKER
• Re: Gen-ART review of draft-ietf-geopriv-policy-uri-02
  • From: Richard L. Barnes
• Re: Gen-ART review of draft-ietf-geopriv-policy-uri-02
  • From: Richard L. Barnes
• Re: Anotherj RFP without IETF community input
  • From: Eric Burger
• Review comments on draft-sprecher-mpls-tp-oam-considerations
  • From: Adrian Farrel
• Re: Anotherj RFP without IETF community input
  • From: Nick Hilliard
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (TheReasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: Ersue, Mehmet (NSN - DE/Munich)
• Re: Anotherj RFP without IETF community input
  • From: Melinda Shore
• RE: IPv6 support in hotel contract?
  • From: Ross Callon
• Re: Anotherj RFP without IETF community input
  • From: Marshall Eubanks
• Re: Anotherj RFP without IETF community input
  • From: Kevin P. Fleming
• RE: Gen-ART review for draft-irtf-hiprg-dht-04
  • From: Ahrenholz, Jeffrey M
• Re: [IAOC] Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: SM
• Re: Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: Acee Lindem
• Re: Gen-ART review of draft-ietf-eai-rfc5335bis-12
  • From: Abel
• Re: Anotherj RFP without IETF community input
  • From: Eric Burger
• Re: Anotherj RFP without IETF community input
  • From: Simon Pietro Romano
• RE: IPv6 support in hotel contract?
  • From: Cameron Byrne
• Re: IPv6 support in hotel contract?
  • From: Andrew Allen
• Re: [IAOC] Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: Bob Hinden
• RE: IPv6 support in hotel contract?
  • From: George, Wes
• Re: IPv6 support in hotel contract?
  • From: Andrew Allen
• Re: [IAOC] Anotherj RFP without IETF community input
  • From: Dave CROCKER
• Re: DKIM delays
  • From: Hector
• DKIM delays
  • From: t.petch
• Re: IPv6 support in hotel contract?
  • From: Cullen Jennings
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Re: IPv6 support in hotel contract?
  • From: Robinson Tryon
• Re: IPv6 support in hotel contract?
  • From: Alejandro Acosta
• Re: Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: edj . etc
• Re: Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: Randy Bush
• Re: Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: John C Klensin
• Re: Anotherj RFP without IETF community input
  • From: Kevin P. Fleming
• Re: [IAOC] Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: John C Klensin
• Re: Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: Phillip Hallam-Baker
• RE: Anotherj RFP without IETF community input
  • From: Worley, Dale R (Dale)
• RE: IPv6 support in hotel contract?
  • From: David Morris
• RE: IPv6 support in hotel contract?
  • From: George, Wes
• Re: [IAOC] Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: Randy Bush
• Re: IPv6 support in hotel contract?
  • From: Joel jaeggli
• Re: [IAOC] Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: Bob Hinden
• Re: Anotherj RFP without IETF community input
  • From: John C Klensin
• Re: Anotherj RFP without IETF community input
  • From: SM
• Re: Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: Randy Bush
• Re: Anotherj RFP without IETF community input
  • From: Simon Pietro Romano
• Re: Anotherj RFP without IETF community input
  • From: Simon Pietro Romano
• RE: RFP for Remote Participation Services Specifications Development
  • From: Worley, Dale R (Dale)
• RE: IPv6 support in hotel contract?
  • From: Worley, Dale R (Dale)
• Re: Anotherj RFP without IETF community input
  • From: Henk Uijterwaal
• Gen-ART Telechat Review of draft-ietf-dnsext-rfc2672bis-dname-24
  • From: Ben Campbell
• Gen-ART review for draft-irtf-hiprg-dht-04
  • From: kathleen.moriarty
• Re: Gen-ART review of draft-ietf-eai-rfc5335bis-12
  • From: Miguel A. Garcia
• Re: Gen-ART review of draft-ietf-eai-rfc5335bis-12
  • From: Miguel A. Garcia
• Re: Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: SM
• R: Re: [mpls] unresolved technical concerns
  • From: erminio.ottone_69@xxxxxxxxx
• R: Re: [mpls] 答复: 回复： R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: erminio.ottone_69@xxxxxxxxx
• R: [mpls] FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: erminio.ottone_69@xxxxxxxxx
• R: [mpls] R: Re: 答复: 回复： R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: D'Alessandro Alessandro Gerardo
• Re: Gen-ART review of draft-ietf-eai-rfc5335bis-12
  • From: Pete Resnick
• Re: Anotherj RFP without IETF community input
  • From: Dave Cridland
• Re: Anotherj RFP without IETF community input
  • From: Joel jaeggli
• Re: Anotherj RFP without IETF community input
  • From: Simon Perreault
• Re: Gen-ART review of draft-ietf-eai-rfc5335bis-12
  • From: Pete Resnick
• Re: IPv6 support in hotel contract?
  • From: TJ
• IPv6 support in hotel contract?
  • From: George, Wes
• Re: Gen-ART review of draft-ietf-eai-rfc5335bis-12
  • From: Russ Housley
• RE: Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: George, Wes
• secdir review of draft-ietf-vcarddav-kind-app-00.txt
  • From: Stephen Hanna
• Re: Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: John C Klensin
• Re: Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: Frank Ellermann
• Anotherj RFP without IETF community input (was: Re: RFP for Remote Participation Services Specifications Development)
  • From: John C Klensin
• Re: [payload] [Payload] Last Call: <draft-ietf-payload-rfc3189bis-02.txt> (RTP Payload Format for DV (IEC 61834) Video)) to Proposed Standard
  • From: Kazuhiro Mishima
• RE: [mpls] R: Re: 答复: 回复： R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: John E Drake
• RE: Re: [mpls] unresolved technical concerns
  • From: John E Drake
• Gen-ART review of draft-ietf-eai-rfc5335bis-12
  • From: Miguel A. Garcia
• Re: TSVDIR review of draft-ietf-pim-port-08.txt
  • From: Gorry Fairhurst
• RFP for Remote Participation Services Specifications Development
  • From: IETF Administrative Director
• Re: [www.ietf.org/rt #42182] Re: Mipshop WG draft
  • From: Behcet Sarikaya
• Re: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: t.petch
• Re: Mipshop WG draft
  • From: Randy Bush
• Re: Mipshop WG draft
  • From: Joel jaeggli
• Re: Mipshop WG draft
  • From: Randy Bush
• Mipshop WG draft
  • From: Behcet Sarikaya
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: neil.2.harrison
• RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Yaakov Stein
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Yaakov Stein
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Yaakov Stein
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Yaakov Stein
• Re: Last Call: <draft-salter-rfc5430bis-01.txt> (Suite B Profile for Transport Layer Security (TLS)) to Informational RFC
  • From: Nikos Mavrogiannopoulos
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC - comment 2
  • From: Loa Andersson
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC - comment 2
  • From: Malcolm . BETTS
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Frank Ellermann
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: John Levine
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Barry Leiba
• Raking over the ashes [Was: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC - comment 2]
  • From: Adrian Farrel
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Frank Ellermann
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: J.D. Falk
• [mpls] Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Azhar Sayeed
• Re: Last Call: <draft-weil-shared-transition-space-request-09.txt> (IANA Reserved IPv4 Prefix for Shared CGN Space) to BCP
  • From: SM
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC - comment 2
  • From: Loa Andersson
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC - comment 2
  • From: Huub van Helvoort
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC - comment 2
  • From: Malcolm . BETTS
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Barry Leiba
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Pete Resnick
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Loa Andersson
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• Re: Last Call: <draft-salter-rfc5430bis-01.txt> (Suite B Profile for Transport Layer Security (TLS)) to Informational RFC
  • From: Russ Housley
• Re: [IETF] Re: watersprings.org archive of expired Internet Drafts
  • From: Warren Kumari
• Re: size of the XML of IANA ports
  • From: Joe Touch
• Re: size of the XML of IANA ports
  • From: Joel jaeggli
• Re: meeting slots
  • From: Robert Sparks
• Gen-ART Last Call review of draft-ietf-cuss-sip-uui-reqs-06
  • From: Ben Campbell
• Re: size of the XML of IANA ports
  • From: t.petch
• RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Rolf Winter
• Re: size of the XML of IANA ports
  • From: John Levine
• Re: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: John C Klensin
• Re: meeting slots
  • From: John C Klensin
• Re: meeting slots
  • From: Michael Richardson
• Re: meeting slots
  • From: Dave CROCKER
• Re: size of the XML of IANA ports
  • From: Joe Touch
• Re: size of the XML of IANA ports
  • From: Simon Perreault
• Re: size of the XML of IANA ports
  • From: Joe Touch
• Re: size of the XML of IANA ports
  • From: Simon Perreault
• Re: meeting slots
  • From: Margaret Wasserman
• Re: meeting slots
  • From: Dave CROCKER
• size of the XML of IANA ports
  • From: Joe Touch
• Nomcom 2011-2012: Call for community feedback
  • From: NomCom Chair
• Re: TSVDIR review of draft-ietf-pim-port-08.txt
  • From: Stig Venaas
• Re: TSVDIR review of draft-ietf-pim-port-08.txt
  • From: Gorry Fairhurst
• Re: meeting slots
  • From: Margaret Wasserman
• RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: John E Drake
• Re: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Patrik Fältström
• meeting slots
  • From: Mark Andrews
• RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Ross Callon
• RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Rolf Winter
• Re: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Randy Bush
• RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Ross Callon
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: neil.2.harrison
• Re: TSVDIR review of draft-ietf-pim-port-08.txt
  • From: Stig Venaas
• Re: [Gen-art] Gen-ART Last Call Review of draft-ietf-pwe3-static-pw-status-08
  • From: Ben Campbell
• Re: [apps-discuss] Last Call: <draft-ietf-appsawg-rfc3462bis-01.txt> (The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages) to Draft Standard
  • From: Mykyta Yevstifeyev
• Re: RFC 6302: "Internet-Facing Server Logging": No Word about Privacy?
  • From: Hannes Tschofenig
• Re: RFC 6302: "Internet-Facing Server Logging": No Word about Privacy?
  • From: Martin Rex
• Re: RFC 6302: "Internet-Facing Server Logging": No Word about Privacy?
  • From: Stephane Bortzmeyer
• RE: [mpls] R: FW:LastCall: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(TheReasons for Selecting a Single Solution for MPLS-TP OAM)toInformational RFC
  • From: Weingarten, Yaacov (NSN - IL/Hod HaSharon)
• Re: RFC 6302: "Internet-Facing Server Logging": No Word about Privacy?
  • From: Hannes Tschofenig
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Loa Andersson
• RE: [mpls] R: FW: Last Call:<draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons forSelecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Margaria, Cyril (NSN - DE/Munich)
• RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Rolf Winter
• Re: watersprings.org archive of expired Internet Drafts
  • From: Joel jaeggli
• Re: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Brian E Carpenter
• Re: watersprings.org archive of expired Internet Drafts
  • From: Jean-Michel Combes
• Re: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Stephen Farrell
• Re: watersprings.org archive of expired Internet Drafts
  • From: Elwyn Davies
• RE: ITU-T Beijing meeting [Was: Re: Last Call:<draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC]
  • From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
• Re: ITU-T Beijing meeting [Was: Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC]
  • From: Huub van Helvoort
• Re: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Stephen Kent
• Re: watersprings.org archive of expired Internet Drafts
  • From: Andrew G. Malis
• Re: watersprings.org archive of expired Internet Drafts
  • From: Doug Barton
• RE: ITU-T Beijing meeting [Was: Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC]
  • From: Adrian Farrel
• XML-based registry format, Re: Re: watersprings.org archive of expired Internet Drafts
  • From: Julian Reschke
• Gen-ART review of draft-ietf-nfsv4-federated-fs-dns-srv-namespace-09
  • From: david.black
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM)
  • From: Russ Housley
• Re: watersprings.org archive of expired Internet Drafts
  • From: Elwyn Davies
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: John E Drake
• Re: ITU-T Beijing meeting [Was: Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC]
  • From: Malcolm . BETTS
• Re: Re: watersprings.org archive of expired Internet Drafts
  • From: t.petch
• ITU-T Beijing meeting [Was: Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC]
  • From: Adrian Farrel
• OAM Interworking [Was: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC]
  • From: Adrian Farrel
• two small points, RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Ross Callon
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Ross Callon
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM)to Informational RFC
  • From: HUANG Feng F
• Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
  • From: Chris Donley
• Re: how to make Apple Mail comply to email standards: or vv?
  • From: ned+ietf
• Re: watersprings.org archive of expired Internet Drafts
  • From: Michael Richardson
• how to make Apple Mail comply to email standards: or vv?
  • From: Michael Richardson
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Huub van Helvoort
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Huub van Helvoort
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Huub van Helvoort
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM)to Informational RFC
  • From: HUANG Feng F
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Russ Housley
• Re: [apps-discuss] Last Call: <draft-ietf-appsawg-rfc3462bis-01.txt> (The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages) to Draft Standard
  • From: Mykyta Yevstifeyev
• Re: watersprings.org archive of expired Internet Drafts
  • From: Julian Reschke
• Re: watersprings.org archive of expired Internet Drafts
  • From: Fred Baker
• Re: watersprings.org archive of expired Internet Drafts
  • From: t.petch
• Re: Gen-ART Last Call Review of draft-ietf-pwe3-static-pw-status-08
  • From: Luca Martini
• Re: watersprings.org archive of expired Internet Drafts
  • From: Joel jaeggli
• Re: watersprings.org archive of expired Internet Drafts
  • From: Frank Ellermann
• Re: watersprings.org archive of expired Internet Drafts
  • From: Joel jaeggli
• Re: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Randy Bush
• RE: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: David Allan I
• TSVDIR review of draft-ietf-pim-port-08.txt
  • From: Gorry Fairhurst
• RE: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Alexander Vainshtein
• Re: [IETF] Re: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Warren Kumari
• Software Defined Networks (SDN) BoF in Taipei
  • From: Thomas Nadeau
• RE: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Rolf Winter
• Re: watersprings.org archive of expired Internet Drafts
  • From: t.petch
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: t.petch
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• RE: FW: Last Call:<draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons forSelecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: GT RAMIREZ, Medel G.
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Brian E Carpenter
• Re: Discussion of closure of the MEAD Team
  • From: Brian E Carpenter
• Re: [mpls] FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Dan Frost
• RE: [mpls] R: FW: LastCall: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (TheReasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: Luyuan Fang (lufang)
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Gregory Mirsky
• RE: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Jeff Tantsura
• Re: [codec] Last Call: <draft-ietf-codec-guidelines-05.txt> (Guidelines for the Codec Development Within the IETF) to Informational RFC
  • From: Ralph Giles
• RE: [codec] Last Call: <draft-ietf-codec-guidelines-05.txt> (Guidelines for the Codec Development Within the IETF) to Informational RFC
  • From: Christian Hoene
• RE: [mpls] unresolved technical concerns
  • From: Luyuan Fang (lufang)
• RE: [mpls] 答复: 回复： R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Luyuan Fang (lufang)
• RE: unresolved technical concerns
  • From: Alexander Vainshtein
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: J.D. Falk
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Alessandro Vesely
• Discussion of closure of the MEAD Team
  • From: Adrian Farrel
• Re: [mpls] FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Randy Bush
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: HUANG Feng F
• RE: [mpls] FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• Re: 答复: [mpls] 回复： R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: Loa Andersson
• RE: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: John E Drake
• Re: Last Call: <draft-ietf-codec-guidelines-05.txt> (Guidelines for the Codec Development Within the IETF) to Informational RFC
  • From: SM
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Huub van Helvoort
• Re: SORBS blacklist
  • From: David Morris
• Re: SORBS blacklist
  • From: Joel jaeggli
• Re: SORBS blacklist
  • From: Marshall Eubanks
• RE: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Murray S. Kucherawy
• RE: [mpls] FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Rui Costa
• RE: [mpls] FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Rui Costa
• Re: [codec] Last Call: <draft-ietf-codec-guidelines-05.txt> (Guidelines for the Codec Development Within the IETF) to Informational RFC
  • From: Phillip Hallam-Baker
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: SM
• Re: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: David Sinicrope
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Douglas Otis
• Re: [codec] Last Call: <draft-ietf-codec-guidelines-05.txt> (Guidelines for the Codec Development Within the IETF) to Informational RFC
  • From: Stephan Wenger
• Re: Expiring a publication - especially standards track documents which are abandoned
  • From: Fred Baker
• RE: [mpls] unresolved technical concerns
  • From: John E Drake
• Re: Last Call: <draft-ietf-codec-guidelines-05.txt> (Guidelines for the Codec Development Within the IETF) to Informational RFC
  • From: Phillip Hallam-Baker
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: John Levine
• Re: 答复: [mpls] 回复： R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Brian E Carpenter
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Rolf Winter
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Frank Ellermann
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: SM
• unresolved technical concerns
  • From: D'Alessandro Alessandro Gerardo
• R: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: D'Alessandro Alessandro Gerardo
• Gen-ART review of draft-oreirdan-mody-bot-remediation-16
  • From: Miguel A. Garcia
• 回复： [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Larry
• RE: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Alexander Vainshtein
• R: [mpls] FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: D'Alessandro Alessandro Gerardo
• FW: [mpls] FW: Last Call:<draft-sprecher-mpls-tp-oam-considerations-01.txt> (TheReasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: Larry
• Gen-ART Last Call Review of draft-ietf-pwe3-static-pw-status-08
  • From: Ben Campbell
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Alessandro Vesely
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• 答复: [mpls] 回复： R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: yang . jian90
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Rolf Winter
• Re: [Gen-art] Gen-ART review of draft-oreirdan-mody-bot-remediation-16
  • From: Elwyn Davies
• Re: [mpls] R: FW: LastCall: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM
  • From: Stewart Bryant
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(TheReasons for Selecting a Single Solution for MPLS-TP OAM)toInformational RFC
  • From: t.petch
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (TheReasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: t.petch
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (TheReasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: Stewart Bryant
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: HUANG Feng F
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: Loa Andersson
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Loa Andersson
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (TheReasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: Loa Andersson
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Rolf Winter
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: HUANG Feng F
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Loa Andersson
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (TheReasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: t.petch
• Re: [mpls] R: FW: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Stewart Bryant
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Hector
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Hector
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Hector
• FW: [mpls] FW: Last Call:<draft-sprecher-mpls-tp-oam-considerations-01.txt> (TheReasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: ma . yuxia
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Eliot Lear
• RE: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Murray S. Kucherawy
• Re: Expiring a publication - especially standards track documents which are abandoned
  • From: Douglas Otis
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Douglas Otis
• RE: [mpls] FW: Last Call:<draft-sprecher-mpls-tp-oam-considerations-01.txt> (TheReasons for Selecting a Single Solution for MPLS-TP OAM) toInformational RFC
  • From: HUANG Feng F
• Re: Expiring a publication - especially standards track documents which are abandoned
  • From: Gellens, Randall
• Re: Expiring a publication - especially standards track documents which are abandoned
  • From: John C Klensin
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Barry Leiba
• Gen-ART review of draft-ietf-lisp-multicast-08
  • From: kathleen.moriarty
• Comments to draft-sprecher-mpls-tp-oam-considerations
  • From: Greg Mirsky
• Re: [Gen-art] Gen-ART Telechat review of draft-ietf-vrrp-unified-mib-10
  • From: Ben Campbell
• Gen-ART Telechat review of draft-ietf-vrrp-unified-mib-10
  • From: Ben Campbell
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: J.D. Falk
• Re: Expiring a publication - especially standards track documents which are abandoned
  • From: Dean Willis
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt>(The Reasons for Selecting a Single Solution for MPLS-TP OAM)to Informational RFC
  • From: t.petch
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Frank Ellermann
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Barry Leiba
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Rolf Winter
• RE: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: Murray S. Kucherawy
• Re: Last Call: <draft-salter-rfc5430bis-01.txt> (Suite B Profile for Transport Layer Security (TLS)) to Informational RFC
  • From: Nikos Mavrogiannopoulos
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• RE: Gen-ART Telechat review of draft-ietf-vrrp-unified-mib-10
  • From: Adrian Farrel
• RE: GenART LC review of draft-ietf-appsawg-rfc3462bis-01
  • From: Roni Even
• Re: Last Call: <draft-jdfalk-maawg-cfblbcp-02.txt> (Complaint Feedback Loop Operational Recommendations) to Informational RFC
  • From: SM
• Re: Last Call: <draft-oreirdan-mody-bot-remediation-16.txt> (Recommendations for the Remediation of Bots in ISP Networks) to Informational RFC
  • From: SM
• RE: GenART LC review of draft-ietf-appsawg-rfc3462bis-01
  • From: Murray S. Kucherawy
• RE: GenART LC review of draft-ietf-appsawg-rfc3462bis-01
  • From: Roni Even
• RE: GenART LC review of draft-ietf-appsawg-rfc3462bis-01
  • From: Murray S. Kucherawy
• Re: [IETF] Re: Another reason not to return :-)
  • From: Warren Kumari
• Re: Another reason not to return :-)
  • From: Ole Jacobsen
• Re: Another reason not to return :-)
  • From: Huub van Helvoort
• GenART LC review of draft-ietf-appsawg-rfc3462bis-01
  • From: Roni Even
• Re: Last Call: <draft-ietf-grow-no-more-unallocated-slash8s-03.txt> (Time to Remove Filters for Previously Unallocated IPv4 /8s) to BCP
  • From: SM
• Another reason not to return :-)
  • From: Ole Jacobsen
• Last Call: <draft-ietf-grow-no-more-unallocated-slash8s-03.txt>
  • From: Frank Ellermann
• Call for Participation: Using IP Overlays to provide L2 Virtualization
  • From: Thomas Narten
• Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
  • From: Thomas Narten
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Brian E Carpenter
• RE: watersprings.org archive of expired Internet Drafts
  • From: Dan Wing
• RE: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Dan Wing
• Re: watersprings.org archive of expired Internet Drafts
  • From: Sean Turner
• RE: watersprings.org archive of expired Internet Drafts
  • From: Adrian Farrel
• watersprings.org archive of expired Internet Drafts
  • From: Tony Finch
• Re: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: GangChen
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Huub van Helvoort
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Huub van Helvoort
• Re: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Hui Deng
• Re: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Hui Deng
• Weekly posting summary for ietf@xxxxxxxx
  • From: Thomas Narten
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Thomas Nadeau
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Brian E Carpenter
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Scott O Bradner
• RE: [BEHAVE] [Softwires] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Rajiv Asati (rajiva)
• Gen-ART LC review of draft-ietf-drinks-usecases-requirements-06
  • From: Roni Even
• Re: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Rémi Després
• Re: [Softwires] [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Mark Townsley
• RE: [BEHAVE] [Softwires] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Rajiv Asati (rajiva)
• Re: [BEHAVE] [Softwires] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Cameron Byrne
• RE: [Softwires] [BEHAVE] ... Dual Stack Hosts Using "Bump-in-the-Host" (BIH))
  • From: Dan Wing
• RE: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Dan Wing
• RE: [BEHAVE] ... Dual Stack Hosts Using "Bump-in-the-Host" (BIH))
  • From: Dan Wing
• Re: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: GangChen
• RE: [BEHAVE] ... Dual Stack Hosts Using "Bump-in-the-Host" (BIH))
  • From: Dan Wing
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Varma, Eve L (Eve)
• RE: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: andy.bd.reid
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Malcolm . BETTS
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Andrew Feren
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Thomas Nadeau
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Thomas Nadeau
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: SM
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Huub van Helvoort
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Huub van Helvoort
• Re: IAOC: delegating ex-officio responsibility
  • From: Doug Barton
• Re: IAOC: delegating ex-officio responsibility
  • From: John Levine
• Re: IAOC: delegating ex-officio responsibility
  • From: Brian E Carpenter
• Re: [BEHAVE] [Softwires] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Cameron Byrne
• Re: [Softwires] [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Keith Moore
• Re: [Softwires] [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Cameron Byrne
• Re: [Softwires] [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Mark Townsley
• RE: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Dan Wing
• RE: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Dan Wing
• Re: IAOC: delegating ex-officio responsibility
  • From: Russ Housley
• Re: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Cameron Byrne
• Re: IAOC: delegating ex-officio responsibility
  • From: Leslie Daigle
• Re: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Hui Deng
• Re: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Hui Deng
• Re: [payload] [Payload] Last Call: <draft-ietf-payload-rfc3189bis-02.txt> (RTP Payload Format for DV (IEC 61834) Video)) to Proposed Standard
  • From: Kazuhiro Mishima
• Re: Need help tracking down problem accessing IETF Subversion repository on Mac OS X
  • From: Stuart Cheshire
• Re: Last Call: <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC
  • From: Brian E Carpenter
• Re: Last Call: <draft-ietf-pim-port-08.txt> (A Reliable TransportMechanism for PIM) to Experimental RFC
  • From: Joe Touch
• Re: IAOC: delegating ex-officio responsibility
  • From: Brian E Carpenter
• Re: IAOC: delegating ex-officio responsibility
  • From: John C Klensin
• RE: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: teemu.savolainen
• RE: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: teemu.savolainen
• Re: Gen-ART review of draft-ietf-avtext-client-to-mixer-audio-level-05.txt
  • From: Emil Ivov
• Re: [payload] [Payload] Last Call: <draft-ietf-payload-rfc3189bis-02.txt> (RTP Payload Format for DV (IEC 61834) Video)) to Proposed Standard
  • From: Qin Wu
• RE: Gen-ART review of draft-ietf-avtext-client-to-mixer-audio-level-05.txt
  • From: Jonathan Lennox
• RE: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Dan Wing
• Re: Need help tracking down problem accessing IETF Subversion repository on Mac OS X
  • From: Henrik Levkowetz
• RE: 240/4 unreservation (was RE: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC)
  • From: George, Wes
• Re: Need help tracking down problem accessing IETF Subversion
  • From: Yoav Nir
• RE: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Dan Wing
• RE: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Dan Wing
• Re: Last Call: <draft-ietf-pim-port-08.txt> (A Reliable TransportMechanism for PIM) to Experimental RFC
  • From: t.petch
• Re: 240/4 unreservation (was RE: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC)
  • From: Iljitsch van Beijnum
• Re: Need help tracking down problem accessing IETF Subversion
  • From: Yoav Nir
• Re: Need help tracking down problem accessing IETF Subversionrepository on Mac OS X
  • From: t.petch
• Re: Gen-ART review of draft-ietf-avtext-client-to-mixer-audio-level-05.txt
  • From: Alexey Melnikov
• Re: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Hui Deng
• Re: [BEHAVE] [Softwires] Last Call:<draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using"Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Hui Deng
• RE: 240/4 unreservation (was RE: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC)
  • From: Christian Huitema
• Re: 240/4 unreservation (was RE: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC)
  • From: Keith Moore
• RE: [BEHAVE] Last Call: <draft-ietf-behave-v4v6-bih-06.txt> (Dual Stack Hosts Using "Bump-in-the-Host" (BIH)) to Proposed Standard
  • From: Dan Wing
• Re: 240/4 unreservation (was RE: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC)
  • From: Masataka Ohta
• Re: 240/4 unreservation (was RE: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC)
  • From: Masataka Ohta
• Re: Gen-ART review of draft-ietf-avtext-client-to-mixer-audio-level-05.txt
  • From: Alexey Melnikov
• RE: 240/4 unreservation (was RE: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC)
  • From: Christian Huitema
• Re: 240/4 unreservation (was RE: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC)
  • From: Frank Ellermann
• Re: Need help tracking down problem accessing IETF Subversion
  • From: Martin Rex
• Re: Need help tracking down problem accessing IETF Subversion repository on Mac OS X
  • From: Yoav Nir
• Re: 240/4 unreservation (was RE: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC)
  • From: Keith Moore
• Re: IAOC: delegating ex-officio responsibility
  • From: Bob Hinden