From rfc-editor at rfc-editor.org Thu Feb 1 10:51:35 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 1 Feb 2007 10:51:35 -0800 Subject: [rfc-dist] RFC 4628 on RTP Payload Format for H.263 Moving RFC 2190 to Historic Status Message-ID: <200702011851.l11IpZKj014251@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4628 Title: RTP Payload Format for H.263 Moving RFC 2190 to Historic Status Author: R. Even Status: Informational Date: January 2007 Mailbox: roni.even at polycom.co.il Pages: 5 Characters: 8084 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-rfc2190-to-historic-06.txt URL: http://www.rfc-editor.org/rfc/rfc4628.txt The first RFC that describes RTP payload format for ITU Telecommunication Standardization Sector (ITU-T) recommendation H.263 is RFC 2190. This specification discusses why to move RFC 2190 to historic status. This memo provides information for the Internet community. This document is a product of the Audio/Video Transport Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Feb 7 18:16:54 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 7 Feb 2007 18:16:54 -0800 Subject: [rfc-dist] RFC 4651 on A Taxonomy and Analysis of Enhancements to Mobile IPv6 Route Optimization Message-ID: <200702080216.l182GsUw006945@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4651 Title: A Taxonomy and Analysis of Enhancements to Mobile IPv6 Route Optimization Author: C. Vogt, J. Arkko Status: Informational Date: February 2007 Mailbox: chvogt at tm.uka.de, jari.arkko at ericsson.com Pages: 31 Characters: 79226 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-mobopts-ro-enhancements-08.txt URL: http://www.rfc-editor.org/rfc/rfc4651.txt This document describes and evaluates strategies to enhance Mobile IPv6 Route Optimization, on the basis of existing proposals, in order to motivate and guide further research in this context. This document is a product of the IP Mobility Optimizations (MobOpts) Research Group. This memo provides information for the Internet community. This document is a product of the IRTF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Feb 8 17:46:50 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 8 Feb 2007 17:46:50 -0800 Subject: [rfc-dist] RFC 4798 on Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE) Message-ID: <200702090146.l191ko80010931@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4798 Title: Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE) Author: J. De Clercq, D. Ooms, S. Prevost, F. Le Faucheur Status: Standards Track Date: February 2007 Mailbox: jeremy.de_clercq at alcatel-lucent.be, dirk at onesparrow.com, stuart.prevost at bt.com, flefauch at cisco.com Pages: 14 Characters: 31381 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ooms-v6ops-bgp-tunnel-07.txt URL: http://www.rfc-editor.org/rfc/rfc4798.txt This document explains how to interconnect IPv6 islands over a Multiprotocol Label Switching (MPLS)-enabled IPv4 cloud. This approach relies on IPv6 Provider Edge routers (6PE), which are Dual Stack in order to connect to IPv6 islands and to the MPLS core, which is only required to run IPv4 MPLS. The 6PE routers exchange the IPv6 reachability information transparently over the core using the Multiprotocol Border Gateway Protocol (MP-BGP) over IPv4. In doing so, the BGP Next Hop field is used to convey the IPv4 address of the 6PE router so that dynamically established IPv4-signaled MPLS Label Switched Paths (LSPs) can be used without explicit tunnel configuration. [STANDARDS TRACK] This document is a product of the Inter-Domain Routing Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Feb 8 17:47:17 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 8 Feb 2007 17:47:17 -0800 Subject: [rfc-dist] RFC 4796 on The Session Description Protocol (SDP) Content Attribute Message-ID: <200702090147.l191lHDk010936@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4796 Title: The Session Description Protocol (SDP) Content Attribute Author: J. Hautakorpi, G. Camarillo Status: Standards Track Date: February 2007 Mailbox: Jani.Hautakorpi at ericsson.com, Gonzalo.Camarillo at ericsson.com Pages: 11 Characters: 22886 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mmusic-sdp-media-content-06.txt URL: http://www.rfc-editor.org/rfc/rfc4796.txt This document defines a new Session Description Protocol (SDP) media- level attribute, 'content'. The 'content' attribute defines the content of the media stream to a more detailed level than the media description line. The sender of an SDP session description can attach the 'content' attribute to one or more media streams. The receiving application can then treat each media stream differently (e.g., show it on a big or small screen) based on its content. [STANDARDS TRACK] This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Feb 8 17:47:31 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 8 Feb 2007 17:47:31 -0800 Subject: [rfc-dist] RFC 4793 on The EAP Protected One-Time Password Protocol (EAP-POTP) Message-ID: <200702090147.l191lV09010944@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4793 Title: The EAP Protected One-Time Password Protocol (EAP-POTP) Author: M. Nystroem Status: Informational Date: February 2007 Mailbox: magnus at rsasecurity.com Pages: 82 Characters: 172575 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-nystrom-eap-potp-07.txt URL: http://www.rfc-editor.org/rfc/rfc4793.txt This document describes a general Extensible Authentication Protocol (EAP) method suitable for use with One-Time Password (OTP) tokens, and offers particular advantages for tokens with direct electronic interfaces to their associated clients. The method can be used to provide unilateral or mutual authentication, and key material, in protocols utilizing EAP, such as PPP, IEEE 802.1X, and Internet Key Exchange Protocol Version 2 (IKEv2). This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Thu Feb 8 17:47:43 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 8 Feb 2007 17:47:43 -0800 Subject: [rfc-dist] RFC 4728 on The Dynamic Source Routing Protocol (DSR) for Mobile Ad Hoc Networks for IPv4 Message-ID: <200702090147.l191lhaC010949@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4728 Title: The Dynamic Source Routing Protocol (DSR) for Mobile Ad Hoc Networks for IPv4 Author: D. Johnson, Y. Hu, D. Maltz Status: Experimental Date: February 2007 Mailbox: dbj at cs.rice.edu, yihchun at uiuc.edu, dmaltz at cs.cmu.edu Pages: 107 Characters: 265706 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-manet-dsr-10.txt URL: http://www.rfc-editor.org/rfc/rfc4728.txt The Dynamic Source Routing protocol (DSR) is a simple and efficient routing protocol designed specifically for use in multi-hop wireless ad hoc networks of mobile nodes. DSR allows the network to be completely self-organizing and self-configuring, without the need for any existing network infrastructure or administration. The protocol is composed of the two main mechanisms of "Route Discovery" and "Route Maintenance", which work together to allow nodes to discover and maintain routes to arbitrary destinations in the ad hoc network. All aspects of the protocol operate entirely on demand, allowing the routing packet overhead of DSR to scale automatically to only what is needed to react to changes in the routes currently in use. The protocol allows multiple routes to any destination and allows each sender to select and control the routes used in routing its packets, for example, for use in load balancing or for increased robustness. Other advantages of the DSR protocol include easily guaranteed loop-free routing, operation in networks containing unidirectional links, use of only "soft state" in routing, and very rapid recovery when routes in the network change. The DSR protocol is designed mainly for mobile ad hoc networks of up to about two hundred nodes and is designed to work well even with very high rates of mobility. This document specifies the operation of the DSR protocol for routing unicast IPv4 packets. This memo defines an Experimental Protocol for the Internet community. This document is a product of the Mobile Ad-hoc Networks Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Feb 16 09:43:38 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 16 Feb 2007 09:43:38 -0800 Subject: [rfc-dist] RFC 4745 on Common Policy: A Document Format for Expressing Privacy Preferences Message-ID: <200702161743.l1GHhcfN006167@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4745 Title: Common Policy: A Document Format for Expressing Privacy Preferences Author: H. Schulzrinne, H. Tschofenig, J. Morris, J. Cuellar, J. Polk, J. Rosenberg Status: Standards Track Date: February 2007 Mailbox: schulzrinne at cs.columbia.edu, Hannes.Tschofenig at siemens.com, jmorris at cdt.org, Jorge.Cuellar at siemens.com, jmpolk at cisco.com, jdrosen at cisco.com Pages: 32 Characters: 63602 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-geopriv-common-policy-11.txt URL: http://www.rfc-editor.org/rfc/rfc4745.txt This document defines a framework for authorization policies controlling access to application-specific data. This framework combines common location- and presence-specific authorization aspects. An XML schema specifies the language in which common policy rules are represented. The common policy framework can be extended to other application domains. [STANDARDS TRACK] This document is a product of the Geographic Location/Privacy Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Feb 16 09:44:11 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 16 Feb 2007 09:44:11 -0800 Subject: [rfc-dist] RFC 4816 on Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer Mode (ATM) Transparent Cell Transport Service Message-ID: <200702161744.l1GHiBre006177@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4816 Title: Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer Mode (ATM) Transparent Cell Transport Service Author: A. Malis, L. Martini, J. Brayley, T. Walsh Status: Standards Track Date: February 2007 Mailbox: andrew.g.malis at verizon.com, lmartini at cisco.com, jeremy.brayley at ecitele.com, twalsh at juniper.net Pages: 5 Characters: 10269 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pwe3-cell-transport-06.txt URL: http://www.rfc-editor.org/rfc/rfc4816.txt The document describes a transparent cell transport service that makes use of the "N-to-one" cell relay mode for Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer-Mode (ATM) cell encapsulation. [STANDARDS TRACK] This document is a product of the Pseudo Wire Emulation Edge to Edge Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Feb 16 09:43:58 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 16 Feb 2007 09:43:58 -0800 Subject: [rfc-dist] RFC 4815 on RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095 Message-ID: <200702161743.l1GHhwGM006172@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4815 Title: RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095 Author: L-E. Jonsson, K. Sandlund, G. Pelletier, P. Kremer Status: Standards Track Date: February 2007 Mailbox: lars-erik.jonsson at ericsson.com, kristofer.sandlund at ericsson.com, ghyslain.pelletier at ericsson.com, peter.kremer at ericsson.com Pages: 33 Characters: 74819 Updates: RFC3095, RFC3241, RFC3843, RFC4019, RFC4362 See-Also: I-D Tag: draft-ietf-rohc-rtp-impl-guide-22.txt URL: http://www.rfc-editor.org/rfc/rfc4815.txt RFC 3095 defines the RObust Header Compression (ROHC) framework and profiles for IP (Internet Protocol), UDP (User Datagram Protocol), RTP (Real-Time Transport Protocol), and ESP (Encapsulating Security Payload). Some parts of the specification are unclear or contain errors that may lead to misinterpretations that may impair interoperability between different implementations. This document provides corrections, additions, and clarifications to RFC 3095; this document thus updates RFC 3095. In addition, other clarifications related to RFC 3241 (ROHC over PPP), RFC 3843 (ROHC IP profile) and RFC 4109 (ROHC UDP-Lite profiles) are also provided. [STANDARDS TRACK] This document is a product of the Robust Header Compression Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Feb 21 18:20:17 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 21 Feb 2007 18:20:17 -0800 Subject: [rfc-dist] RFC 4804 on Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE Tunnels Message-ID: <200702220220.l1M2KHEK023935@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4804 Title: Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE Tunnels Author: F. Le Faucheur, Ed. Status: Standards Track Date: February 2007 Mailbox: flefauch at cisco.com Pages: 31 Characters: 69473 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tsvwg-rsvp-dste-05.txt URL: http://www.rfc-editor.org/rfc/rfc4804.txt RFC 3175 specifies aggregation of Resource ReSerVation Protocol (RSVP) end-to-end reservations over aggregate RSVP reservations. This document specifies aggregation of RSVP end-to-end reservations over MPLS Traffic Engineering (TE) tunnels or MPLS Diffserv-aware MPLS Traffic Engineering (DS-TE) tunnels. This approach is based on RFC 3175 and simply modifies the corresponding procedures for operations over MPLS TE tunnels instead of aggregate RSVP reservations. This approach can be used to achieve admission control of a very large number of flows in a scalable manner since the devices in the core of the network are unaware of the end-to-end RSVP reservations and are only aware of the MPLS TE tunnels. [STANDARDS TRACK] This document is a product of the Transport Area Working Group Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Mon Feb 26 16:12:17 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 26 Feb 2007 16:12:17 -0800 Subject: [rfc-dist] RFC 4806 on Online Certificate Status Protocol (OCSP) Extensions to IKEv2 Message-ID: <200702270012.l1R0CHPe002703@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4806 Title: Online Certificate Status Protocol (OCSP) Extensions to IKEv2 Author: M. Myers, H. Tschofenig Status: Standards Track Date: February 2007 Mailbox: mmyers at fastq.com, Hannes.Tschofenig at siemens.com Pages: 11 Characters: 21991 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-myers-ikev2-ocsp-05.txt URL: http://www.rfc-editor.org/rfc/rfc4806.txt While the Internet Key Exchange Protocol version 2 (IKEv2) supports public key based authentication, the corresponding use of in-band Certificate Revocation Lists (CRL) is problematic due to unbounded CRL size. The size of an Online Certificate Status Protocol (OCSP) response is however well-bounded and small. This document defines the "OCSP Content" extension to IKEv2. A CERTREQ payload with "OCSP Content" identifies zero or more trusted OCSP responders and is a request for inclusion of an OCSP response in the IKEv2 handshake. A cooperative recipient of such a request responds with a CERT payload containing the appropriate OCSP response. This content is recognizable via the same "OCSP Content" identifier. When certificates are used with IKEv2, the communicating peers need a mechanism to determine the revocation status of the peer's certificate. OCSP is one such mechanism. This document applies when OCSP is desired and security policy prevents one of the IKEv2 peers from accessing the relevant OCSP responder directly. Firewalls are often deployed in a manner that prevents such access by IKEv2 peers outside of an enterprise network. [STANDARDS TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Feb 28 21:07:06 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 28 Feb 2007 21:07:06 -0800 Subject: [rfc-dist] RFC 4809 on Requirements for an IPsec Certificate Management Profile Message-ID: <200703010507.l21576xs014298@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4809 Title: Requirements for an IPsec Certificate Management Profile Author: C. Bonatti, Ed., S. Turner, Ed., G. Lebovitz, Ed. Status: Informational Date: February 2007 Mailbox: Bonattic at ieca.com, Turners at ieca.com, gregory.ietf at gmail.com Pages: 45 Characters: 98400 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pki4ipsec-mgmt-profile-rqts-07.txt URL: http://www.rfc-editor.org/rfc/rfc4809.txt This informational document describes and identifies the requirements for transactions to handle Public Key Certificate (PKC) lifecycle transactions between Internet Protocol Security (IPsec) Virtual Private Network (VPN) Systems using Internet Key Exchange (IKE) (versions 1 and 2) and Public Key Infrastructure (PKI) Systems. These requirements are designed to meet the needs of enterprise-scale IPsec VPN deployments. It is intended that a standards track profile of a management protocol will be created to address many of these requirements. This memo provides information for the Internet community. This document is a product of the Profiling Use of PKI in IPSEC Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Feb 28 21:08:22 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 28 Feb 2007 21:08:22 -0800 Subject: [rfc-dist] RFC 4855 on Media Type Registration of RTP Payload Formats Message-ID: <200703010508.l2158MMk014310@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4855 Title: Media Type Registration of RTP Payload Formats Author: S. Casner Status: Standards Track Date: February 2007 Mailbox: casner at acm.org Pages: 11 Characters: 24404 Obsoletes: RFC3555 See-Also: I-D Tag: draft-ietf-avt-rfc3555bis-05.txt URL: http://www.rfc-editor.org/rfc/rfc4855.txt This document specifies the procedure to register RTP payload formats as audio, video, or other media subtype names. This is useful in a text-based format description or control protocol to identify the type of an RTP transmission. [STANDARDS TRACK] This document is a product of the Audio/Video Transport Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Feb 28 21:08:02 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 28 Feb 2007 21:08:02 -0800 Subject: [rfc-dist] RFC 4856 on Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences Message-ID: <200703010508.l21582bg014303@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4856 Title: Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences Author: S. Casner Status: Standards Track Date: February 2007 Mailbox: casner at acm.org Pages: 29 Characters: 45881 Obsoletes: RFC3555 See-Also: I-D Tag: draft-ietf-avt-rfc3555bis-part2-02.txt URL: http://www.rfc-editor.org/rfc/rfc4856.txt This document specifies media type registrations for the RTP payload formats defined in the RTP Profile for Audio and Video Conferences. Some of these may also be used for transfer modes other than RTP. [STANDARDS TRACK] This document is a product of the Audio/Video Transport Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Feb 28 21:08:55 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 28 Feb 2007 21:08:55 -0800 Subject: [rfc-dist] RFC 4803 on Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base Message-ID: <200703010508.l2158tJn014315@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4803 Title: Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base Author: T. Nadeau, Ed., A. Farrel, Ed. Status: Standards Track Date: February 2007 Mailbox: tnadeau at cisco.com, adrian at olddog.co.uk Pages: 42 Characters: 79925 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-gmpls-lsr-mib-15.txt URL: http://www.rfc-editor.org/rfc/rfc4803.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects to configure and/or monitor a Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR). [STANDARDS TRACK] This document is a product of the Common Control and Measurement Plane Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Feb 28 21:09:47 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 28 Feb 2007 21:09:47 -0800 Subject: [rfc-dist] RFC 4802 on Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base Message-ID: <200703010509.l2159lHs014320@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4802 Title: Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base Author: T. Nadeau, Ed., A. Farrel, Ed. Status: Standards Track Date: February 2007 Mailbox: tnadeau at cisco.com, adrian at olddog.co.uk Pages: 60 Characters: 118164 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-gmpls-te-mib-16.txt URL: http://www.rfc-editor.org/rfc/rfc4802.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for Generalized Multiprotocol Label Switching (GMPLS)-based traffic engineering. [STANDARDS TRACK] This document is a product of the Common Control and Measurement Plane Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Feb 28 21:10:07 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 28 Feb 2007 21:10:07 -0800 Subject: [rfc-dist] RFC 4801 on Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management Message-ID: <200703010510.l215A71k014332@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4801 Title: Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management Author: T. Nadeau, Ed., A. Farrel, Ed. Status: Standards Track Date: February 2007 Mailbox: tnadeau at cisco.com, adrian at olddog.co.uk Pages: 9 Characters: 16347 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-gmpls-tc-mib-11.txt URL: http://www.rfc-editor.org/rfc/rfc4801.txt This document defines a Management Information Base (MIB) module that contains textual conventions (TCs) to represent commonly used Generalized Multiprotocol Label Switching (GMPLS) management information. The intent is that these textual conventions will be imported and used in GMPLS-related MIB modules that would otherwise define their own representations. [STANDARDS TRACK] This document is a product of the Common Control and Measurement Plane Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Feb 28 21:10:32 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 28 Feb 2007 21:10:32 -0800 Subject: [rfc-dist] RFC 4822 on RIPv2 Cryptographic Authentication Message-ID: <200703010510.l215AWOi014337@nit.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4822 Title: RIPv2 Cryptographic Authentication Author: R. Atkinson, M. Fanto Status: Standards Track Date: February 2007 Mailbox: rja at extremenetworks.com, mattjf at umd.edu Pages: 22 Characters: 53828 I-D Tag: draft-rja-ripv2-auth-06.txt URL: http://www.rfc-editor.org/rfc/rfc4822.txt This note describes a revision to the RIPv2 Cryptographic Authentication mechanism originally specified in RFC 2082. This document obsoletes RFC 2082 and updates RFC 2453. This document adds details of how the SHA family of hash algorithms can be used with RIPv2 Cryptographic Authentication, whereas the original document only specified the use of Keyed-MD5. Also, this document clarifies a potential issue with an active attack on this mechanism and adds significant text to the Security Considerations section. [STANDARDS TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ...