From rfc-editor at rfc-editor.org Thu Mar 6 13:57:27 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 6 Mar 2008 13:57:27 -0800 (PST) Subject: [rfc-dist] RFC 5158 on 6to4 Reverse DNS Delegation Specification Message-ID: <20080306215727.87DA11186AB@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5158 Title: 6to4 Reverse DNS Delegation Specification Author: G. Huston Status: Informational Date: March 2008 Mailbox: gih at apnic.net Pages: 12 Characters: 25536 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-huston-6to4-reverse-dns-07.txt URL: http://www.rfc-editor.org/rfc/rfc5158.txt This memo describes the service mechanism for entering a delegation of DNS servers that provide reverse lookup of 6to4 IPv6 addresses into the 6to4 reverse zone file. The mechanism is based on a conventional DNS delegation service interface, allowing the service client to enter the details of a number of DNS servers for the delegated domain. In the context of a 6to4 reverse delegation, the client is primarily authenticated by its source address used in the delegation request, and is authorized to use the function if its IPv6 address prefix corresponds to an address from within the requested 6to4 delegation address block. 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 Mar 6 13:57:29 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 6 Mar 2008 13:57:29 -0800 (PST) Subject: [rfc-dist] RFC 5155 on DNS Security (DNSSEC) Hashed Authenticated Denial of Existence Message-ID: <20080306215729.CBE991186AD@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5155 Title: DNS Security (DNSSEC) Hashed Authenticated Denial of Existence Author: B. Laurie, G. Sisson, R. Arends, D. Blacka Status: Standards Track Date: March 2008 Mailbox: ben at links.org, geoff-s at panix.com, roy at nominet.org.uk, davidb at verisign.com Pages: 52 Characters: 112338 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dnsext-nsec3-13.txt URL: http://www.rfc-editor.org/rfc/rfc5155.txt The Domain Name System Security (DNSSEC) Extensions introduced the NSEC resource record (RR) for authenticated denial of existence. This document introduces an alternative resource record, NSEC3, which similarly provides authenticated denial of existence. However, it also provides measures against zone enumeration and permits gradual expansion of delegation-centric zones. [STANDARDS TRACK] This document is a product of the DNS Extensions 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 Mar 6 13:57:23 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 6 Mar 2008 13:57:23 -0800 (PST) Subject: [rfc-dist] RFC 5126 on CMS Advanced Electronic Signatures (CAdES) Message-ID: <20080306215723.719161186A9@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5126 Title: CMS Advanced Electronic Signatures (CAdES) Author: D. Pinkas, N. Pope, J. Ross Status: Informational Date: March 2008 Mailbox: Denis.Pinkas at bull.net, nick.pope at thales-esecurity.com, ross at secstan.com Pages: 141 Characters: 309173 Obsoletes: RFC3126 I-D Tag: draft-ietf-smime-cades-07.txt URL: http://www.rfc-editor.org/rfc/rfc5126.txt This document defines the format of an electronic signature that can remain valid over long periods. This includes evidence as to its validity even if the signer or verifying party later attempts to deny (i.e., repudiates) the validity of the signature. The format can be considered as an extension to RFC 3852 and RFC 2634, where, when appropriate, additional signed and unsigned attributes have been defined. The contents of this Informational RFC amount to a transposition of the ETSI Technical Specification (TS) 101 733 V.1.7.4 (CMS Advanced Electronic Signatures -- CAdES) and is technically equivalent to it. The technical contents of this specification are maintained by ETSI. The ETSI TS and further updates are available free of charge at: http://www.etsi.org/WebSite/Standards/StandardsDownload.aspx This memo provides information for the Internet community. This document is a product of the S/MIME Mail Security 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 Fri Mar 7 16:00:12 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 7 Mar 2008 16:00:12 -0800 (PST) Subject: [rfc-dist] RFC 5140 on A Telephony Gateway REgistration Protocol (TGREP) Message-ID: <20080308000012.D886D1188DB@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5140 Title: A Telephony Gateway REgistration Protocol (TGREP) Author: M. Bangalore, R. Kumar, J. Rosenberg, H. Salama, D.N. Shah Status: Standards Track Date: March 2008 Mailbox: manjax at cisco.com, rajneesh at cisco.com, jdrosen at cisco.com, hsalama at citexsoftware.com, dhaval at moowee.tv Pages: 28 Characters: 59511 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-iptel-tgrep-09.txt URL: http://www.rfc-editor.org/rfc/rfc5140.txt This document describes the Telephony Gateway Registration Protocol (TGREP) for registration of telephony prefixes supported by telephony gateways and soft switches. The registration mechanism can also be used to export resource information. The prefix and resource information can then be passed on to a Telephony Routing over IP (TRIP) Location Server, which in turn can propagate that routing information within and between Internet Telephony Administrative Domains (ITADs). TGREP shares a lot of similarities with the TRIP protocol. It has similar procedures and finite state machine for session establishment. It also shares the same format for messages and a subset of attributes with TRIP. [STANDARDS TRACK] This document is a product of the IP Telephony 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 Mar 7 16:01:17 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 7 Mar 2008 16:01:17 -0800 (PST) Subject: [rfc-dist] RFC 5175 on IPv6 Router Advertisement Flags Option Message-ID: <20080308000117.ABD011188DD@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5175 Title: IPv6 Router Advertisement Flags Option Author: B. Haberman, Ed., R. Hinden Status: Standards Track Date: March 2008 Mailbox: brian at innovationslab.net, bob.hinden at nokia.com Pages: 7 Characters: 12463 Obsoletes: RFC5075 URL: http://www.rfc-editor.org/rfc/rfc5175.txt The IPv6 Neighbor Discovery's Router Advertisement message contains an 8-bit field reserved for single-bit flags. Several protocols have reserved flags in this field and others are preparing to reserve a sufficient number of flags to exhaust the field. This document defines an option to the Router Advertisement message that expands the number of flag bits available. [STANDARDS TRACK] This document is a product of the IP Version 6 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 Mar 10 07:08:42 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 10 Mar 2008 07:08:42 -0700 (PDT) Subject: [rfc-dist] RFC 5161 on The IMAP ENABLE Extension Message-ID: <20080310140842.001C9118E17@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5161 Title: The IMAP ENABLE Extension Author: A. Gulbrandsen, Ed., A. Melnikov, Ed. Status: Standards Track Date: March 2008 Mailbox: arnt at oryx.com, Alexey.Melnikov at isode.com Pages: 7 Characters: 12220 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-gulbrandsen-imap-enable-05.txt URL: http://www.rfc-editor.org/rfc/rfc5161.txt Most IMAP extensions are used by the client when it wants to and the server supports it. However, a few extensions require the server to know whether a client supports that extension. The ENABLE extension allows an IMAP client to say which extensions it supports. [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 Mon Mar 10 07:09:11 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 10 Mar 2008 07:09:11 -0700 (PDT) Subject: [rfc-dist] RFC 5162 on IMAP4 Extensions for Quick Mailbox Resynchronization Message-ID: <20080310140911.43CC7118E19@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5162 Title: IMAP4 Extensions for Quick Mailbox Resynchronization Author: A. Melnikov, D. Cridland, C. Wilson Status: Standards Track Date: March 2008 Mailbox: Alexey.Melnikov at isode.com, dave.cridland at isode.com, corby at computer.org Pages: 23 Characters: 51620 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lemonade-reconnect-client-06.txt URL: http://www.rfc-editor.org/rfc/rfc5162.txt This document defines an IMAP4 extension, which gives an IMAP client the ability to quickly resynchronize any previously opened mailbox as part of the SELECT command, without the need for server-side state or additional client round-trips. This extension also introduces a new response that allows for a more compact representation of a list of expunged messages (and always includes the Unique Identifiers (UIDs) expunged). [STANDARDS TRACK] This document is a product of the Enhancements to Internet email to support diverse service environments 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 Tue Mar 18 15:11:52 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 18 Mar 2008 15:11:52 -0700 (PDT) Subject: [rfc-dist] RFC 5159 on Session Description Protocol (SDP) Attributes for Open Mobile Alliance (OMA) Broadcast (BCAST) Service and Content Protection Message-ID: <20080318221152.7956311AA32@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5159 Title: Session Description Protocol (SDP) Attributes for Open Mobile Alliance (OMA) Broadcast (BCAST) Service and Content Protection Author: L. Dondeti, Ed., A. Jerichow Status: Informational Date: March 2008 Mailbox: ldondeti at qualcomm.com, anja.jerichow at nsn.com Pages: 8 Characters: 13921 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-dondeti-oma-mmusic-sdp-attrs-00.txt URL: http://www.rfc-editor.org/rfc/rfc5159.txt This document provides descriptions of Session Description Protocol (SDP) attributes used by the Open Mobile Alliance's Broadcast Service and Content Protection specification. 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 Tue Mar 18 15:11:39 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 18 Mar 2008 15:11:39 -0700 (PDT) Subject: [rfc-dist] RFC 5160 on Considerations of Provider-to-Provider Agreements for Internet-Scale Quality of Service (QoS) Message-ID: <20080318221139.C655A11AA30@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5160 Title: Considerations of Provider-to-Provider Agreements for Internet-Scale Quality of Service (QoS) Author: P. Levis, M. Boucadair Status: Informational Date: March 2008 Mailbox: pierre.levis at orange-ftgroup.com, mohamed.boucadair at orange-ftgroup.com Pages: 19 Characters: 44317 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-levis-provider-qos-agreement-04.txt URL: http://www.rfc-editor.org/rfc/rfc5160.txt This memo analyzes provider-to-provider Quality of Service (QoS) agreements suitable for a global QoS-enabled Internet. It defines terminology relevant to inter-domain QoS models. It proposes a new concept denoted by Meta-QoS-Class (MQC). This concept could potentially drive and federate the way QoS inter-domain relationships are built between providers. It opens up new perspectives for a QoS- enabled Internet that retains, as much as possible, the openness of the existing best-effort Internet. 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 Tue Mar 18 15:12:16 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 18 Mar 2008 15:12:16 -0700 (PDT) Subject: [rfc-dist] RFC 5164 on Mobility Services Transport: Problem Statement Message-ID: <20080318221216.8D4BA11AA36@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5164 Title: Mobility Services Transport: Problem Statement Author: T. Melia, Ed. Status: Informational Date: March 2008 Mailbox: tmelia at cisco.com Pages: 16 Characters: 33726 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mipshop-mis-ps-05.txt URL: http://www.rfc-editor.org/rfc/rfc5164.txt There are ongoing activities in the networking community to develop solutions that aid in IP handover mechanisms between heterogeneous wired and wireless access systems including, but not limited to, IEEE 802.21. Intelligent access selection, taking into account link-layer attributes, requires the delivery of a variety of different information types to the terminal from different sources within the network and vice-versa. The protocol requirements for this signalling have both transport and security issues that must be considered. The signalling must not be constrained to specific link types, so there is at least a common component to the signalling problem, which is within the scope of the IETF. This document presents a problem statement for this core problem. This memo provides information for the Internet community. This document is a product of the Mobility for IP: Performance, Signaling and Handoff Optimization 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 Fri Mar 21 16:32:41 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Mar 2008 16:32:41 -0700 (PDT) Subject: [rfc-dist] RFC 5141 on A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO) Message-ID: <20080321233241.BEE87120684@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5141 Title: A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO) Author: J. Goodwin, H. Apel Status: Informational Date: March 2008 Mailbox: goodwin at iso.org, apel at iso.org Pages: 28 Characters: 57820 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-goodwin-iso-urn-03.txt URL: http://www.rfc-editor.org/rfc/rfc5141.txt This document describes a Uniform Resource Name Namespace Identification (URN NID) for the International Organization for Standardization (ISO). This URN NID is intended for use for the identification of persistent resources published by the ISO standards body (including documents, document metadata, extracted resources such as standard schemata and standard value sets, and other resources). 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 Fri Mar 21 16:33:00 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Mar 2008 16:33:00 -0700 (PDT) Subject: [rfc-dist] RFC 5145 on Framework for MPLS-TE to GMPLS Migration Message-ID: <20080321233300.155F8120686@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5145 Title: Framework for MPLS-TE to GMPLS Migration Author: K. Shiomoto, Ed. Status: Informational Date: March 2008 Mailbox: shiomoto.kohei at lab.ntt.co.jp Pages: 19 Characters: 44646 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-mpls-gmpls-interwork-fmwk-05.txt URL: http://www.rfc-editor.org/rfc/rfc5145.txt The migration from Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) to Generalized MPLS (GMPLS) is the process of evolving an MPLS-TE control plane to a GMPLS control plane. An appropriate migration strategy will be selected based on various factors including the service provider's network deployment plan, customer demand, and operational policy. This document presents several migration models and strategies for migrating from MPLS-TE to GMPLS. In the course of migration, MPLS-TE and GMPLS devices, or networks, may coexist that may require interworking between MPLS-TE and GMPLS protocols. Aspects of the required interworking are discussed as it will influence the choice of a migration strategy. This framework document provides a migration toolkit to aid the operator in selection of an appropriate strategy. This framework document also lists a set of solutions that may aid in interworking, and highlights a set of potential issues. This memo provides information for the Internet community. This document is a product of the Common Control and Measurement Plane 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 Fri Mar 21 16:33:25 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Mar 2008 16:33:25 -0700 (PDT) Subject: [rfc-dist] RFC 5146 on Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks Message-ID: <20080321233325.AD37A120688@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5146 Title: Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks Author: K. Kumaki, Ed. Status: Informational Date: March 2008 Mailbox: ke-kumaki at kddi.com Pages: 15 Characters: 31624 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-mpls-gmpls-interwork-reqts-04.txt URL: http://www.rfc-editor.org/rfc/rfc5146.txt Operation of a Multiprotocol Label Switching (MPLS) traffic engineering (TE) network as a client network to a Generalized MPLS (GMPLS) network has enhanced operational capabilities compared to those provided by a coexistent protocol model (i.e., operation of MPLS-TE over an independently managed transport layer). The GMPLS network may be a packet or a non-packet network, and may itself be a multi-layer network supporting both packet and non-packet technologies. An MPLS-TE Label Switched Path (LSP) originates and terminates on an MPLS Label Switching Router (LSR). The GMPLS network provides transparent transport for the end-to-end MPLS-TE LSP. This document describes a framework and Service Provider requirements for operating MPLS-TE networks over GMPLS networks. This memo provides information for the Internet community. This document is a product of the Common Control and Measurement Plane 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 Fri Mar 21 16:33:41 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Mar 2008 16:33:41 -0700 (PDT) Subject: [rfc-dist] RFC 5166 on Metrics for the Evaluation of Congestion Control Mechanisms Message-ID: <20080321233341.D169E12068A@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5166 Title: Metrics for the Evaluation of Congestion Control Mechanisms Author: S. Floyd, Ed. Status: Informational Date: March 2008 Mailbox: floyd at icir.org Pages: 23 Characters: 53609 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-tmrg-metrics-11.txt URL: http://www.rfc-editor.org/rfc/rfc5166.txt This document discusses the metrics to be considered in an evaluation of new or modified congestion control mechanisms for the Internet. These include metrics for the evaluation of new transport protocols, of proposed modifications to TCP, of application-level congestion control, and of Active Queue Management (AQM) mechanisms in the router. This document is the first in a series of documents aimed at improving the models that we use in the evaluation of transport protocols. This document is a product of the Transport Modeling Research Group (TMRG), and has received detailed feedback from many members of the Research Group (RG). As the document tries to make clear, there is not necessarily a consensus within the research community (or the IETF community, the vendor community, the operations community, or any other community) about the metrics that congestion control mechanisms should be designed to optimize, in terms of trade-offs between throughput and delay, fairness between competing flows, and the like. However, we believe that there is a clear consensus that congestion control mechanisms should be evaluated in terms of trade-offs between a range of metrics, rather than in terms of optimizing for a single metric. This memo provides information for the Internet community. This document is a product of the IRTF 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 Fri Mar 21 16:34:28 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Mar 2008 16:34:28 -0700 (PDT) Subject: [rfc-dist] RFC 5214 on Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) Message-ID: <20080321233428.C993112068E@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5214 Title: Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) Author: F. Templin, T. Gleeson, D. Thaler Status: Informational Date: March 2008 Mailbox: fred.l.templin at boeing.com, tgleeson at cisco.com, dthaler at microsoft.com Pages: 15 Characters: 30126 Obsoletes: RFC4214 I-D Tag: draft-templin-rfc4214bis-05.txt URL: http://www.rfc-editor.org/rfc/rfc5214.txt The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) connects dual-stack (IPv6/IPv4) nodes over IPv4 networks. ISATAP views the IPv4 network as a link layer for IPv6 and supports an automatic tunneling abstraction similar to the Non-Broadcast Multiple Access (NBMA) model. 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 Fri Mar 21 16:34:04 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Mar 2008 16:34:04 -0700 (PDT) Subject: [rfc-dist] RFC 5182 on IMAP Extension for Referencing the Last SEARCH Result Message-ID: <20080321233404.A5FFA12068C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5182 Title: IMAP Extension for Referencing the Last SEARCH Result Author: A. Melnikov Status: Standards Track Date: March 2008 Mailbox: Alexey.Melnikov at isode.com Pages: 13 Characters: 24520 Updates: RFC3501 I-D Tag: draft-melnikov-imap-search-res-07.txt URL: http://www.rfc-editor.org/rfc/rfc5182.txt Many IMAP clients use the result of a SEARCH command as the input to perform another operation, for example, fetching the found messages, deleting them, or copying them to another mailbox. This can be achieved using standard IMAP operations described in RFC 3501; however, this would be suboptimal. The server will send the list of found messages to the client; after that, the client will have to parse the list, reformat it, and send it back to the server. The client can't pipeline the SEARCH command with the subsequent command, and, as a result, the server might not be able to perform some optimizations. This document proposes an IMAP extension that allows a client to tell a server to use the result of a SEARCH (or Unique Identifier (UID) SEARCH) command as an input to any subsequent command. [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 Fri Mar 21 16:34:43 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Mar 2008 16:34:43 -0700 (PDT) Subject: [rfc-dist] RFC 5216 on The EAP-TLS Authentication Protocol Message-ID: <20080321233443.F0736120690@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5216 Title: The EAP-TLS Authentication Protocol Author: D. Simon, B. Aboba, R. Hurst Status: Standards Track Date: March 2008 Mailbox: dansimon at microsoft.com, bernarda at microsoft.com, rmh at microsoft.com Pages: 34 Characters: 71599 Obsoletes: RFC2716 I-D Tag: draft-simon-emu-rfc2716bis-13.txt URL: http://www.rfc-editor.org/rfc/rfc5216.txt The Extensible Authentication Protocol (EAP), defined in RFC 3748, provides support for multiple authentication methods. Transport Layer Security (TLS) provides for mutual authentication, integrity-protected ciphersuite negotiation, and key exchange between two endpoints. This document defines EAP-TLS, which includes support for certificate-based mutual authentication and key derivation. This document obsoletes RFC 2716. A summary of the changes between this document and RFC 2716 is available in Appendix A. [STANDARDS TRACK] This document is a product of the EAP Method Update 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 Tue Mar 25 14:47:31 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 25 Mar 2008 14:47:31 -0700 (PDT) Subject: [rfc-dist] RFC 5190 on Definitions of Managed Objects for Middlebox Communication Message-ID: <20080325214731.E5D1212105D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5190 Title: Definitions of Managed Objects for Middlebox Communication Author: J. Quittek, M. Stiemerling, P. Srisuresh Status: Standards Track Date: March 2008 Mailbox: quittek at nw.neclab.eu, stiemerling at nw.neclab.eu, srisuresh at yahoo.com Pages: 92 Characters: 204929 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-midcom-mib-11.txt URL: http://www.rfc-editor.org/rfc/rfc5190.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 a set of managed objects that allow configuring middleboxes, such as firewalls and network address translators, in order to enable communication across these devices. The definitions of managed objects in this documents follow closely the MIDCOM semantics defined in RFC 5189. [STANDARDS TRACK] This document is a product of the Middlebox Communication 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 Tue Mar 25 14:47:29 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 25 Mar 2008 14:47:29 -0700 (PDT) Subject: [rfc-dist] RFC 5189 on Middlebox Communication (MIDCOM) Protocol Semantics Message-ID: <20080325214729.3D58C12105B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5189 Title: Middlebox Communication (MIDCOM) Protocol Semantics Author: M. Stiemerling, J. Quittek, T. Taylor Status: Standards Track Date: March 2008 Mailbox: stiemerling at nw.neclab.eu, quittek at nw.neclab.eu, tom.taylor at rogers.com Pages: 70 Characters: 161167 Obsoletes: RFC3989 I-D Tag: draft-ietf-midcom-rfc3989-bis-02.txt URL: http://www.rfc-editor.org/rfc/rfc5189.txt This document specifies semantics for a Middlebox Communication (MIDCOM) protocol to be used by MIDCOM agents for interacting with middleboxes such as firewalls and Network Address Translators (NATs). The semantics discussion does not include any specification of a concrete syntax or a transport protocol. However, a concrete protocol is expected to implement the specified semantics or, more likely, a superset of it. The MIDCOM protocol semantics is derived from the MIDCOM requirements, from the MIDCOM framework, and from working group decisions. This document obsoletes RFC 3989. [STANDARDS TRACK] This document is a product of the Middlebox Communication 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 Mar 27 14:49:56 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 27 Mar 2008 14:49:56 -0700 (PDT) Subject: [rfc-dist] RFC 5198 on Unicode Format for Network Interchange Message-ID: <20080327214956.EBDD91214A7@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5198 Title: Unicode Format for Network Interchange Author: J. Klensin, M. Padlipsky Status: Standards Track Date: March 2008 Mailbox: john-ietf at jck.com, the.map at alum.mit.edu Pages: 19 Characters: 45708 Obsoletes: RFC0698 Updates: RFC0854 I-D Tag: draft-klensin-net-utf8-09.txt URL: http://www.rfc-editor.org/rfc/rfc5198.txt The Internet today is in need of a standardized form for the transmission of internationalized "text" information, paralleling the specifications for the use of ASCII that date from the early days of the ARPANET. This document specifies that format, using UTF-8 with normalization and specific line-ending sequences. [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 Fri Mar 28 14:10:43 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 28 Mar 2008 14:10:43 -0700 (PDT) Subject: [rfc-dist] RFC 5128 on State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) Message-ID: <20080328211043.04480121729@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5128 Title: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) Author: P. Srisuresh, B. Ford, D. Kegel Status: Informational Date: March 2008 Mailbox: srisuresh at yahoo.com, baford at mit.edu, dank06 at kegel.com Pages: 32 Characters: 81008 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-behave-p2p-state-06.txt URL: http://www.rfc-editor.org/rfc/rfc5128.txt This memo documents the various methods known to be in use by applications to establish direct communication in the presence of Network Address Translators (NATs) at the current time. Although this memo is intended to be mainly descriptive, the Security Considerations section makes some purely advisory recommendations about how to deal with security vulnerabilities the applications could inadvertently create when using the methods described. This memo covers NAT traversal approaches used by both TCP- and UDP-based applications. This memo is not an endorsement of the methods described, but merely an attempt to capture them in a document. This memo provides information for the Internet community. This document is a product of the Behavior Engineering for Hindrance Avoidance 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 Fri Mar 28 14:10:46 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 28 Mar 2008 14:10:46 -0700 (PDT) Subject: [rfc-dist] RFC 5224 on Diameter Policy Processing Application Message-ID: <20080328211046.439F112172B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5224 Title: Diameter Policy Processing Application Author: M. Brenner Status: Informational Date: March 2008 Mailbox: mrbrenner at alcatel-lucent.com Pages: 5 Characters: 10283 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-brenner-dime-peem-01.txt URL: http://www.rfc-editor.org/rfc/rfc5224.txt This document describes the need for a new IANA Diameter Command Code to be used in a vendor-specific new application for invocation of Policy Processing (Policy Evaluation, or Evaluation and Enforcement). This application is needed as one of the implementations of the Open Mobile Alliance (OMA) Policy Evaluation, Enforcement and Management (PEEM) enabler, namely for the PEM-1 interface used to send a request/response for Policy Processing. 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 Fri Mar 28 14:10:50 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 28 Mar 2008 14:10:50 -0700 (PDT) Subject: [rfc-dist] RFC 5172 on Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol Message-ID: <20080328211050.495A012172D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5172 Title: Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol Author: S. Varada, Ed. Status: Standards Track Date: March 2008 Mailbox: varada at ieee.org Pages: 7 Characters: 14646 Obsoletes: RFC2472 I-D Tag: draft-ietf-ipv6-compression-nego-v2-02.txt URL: http://www.rfc-editor.org/rfc/rfc5172.txt The Point-to-Point Protocol (PPP) provides a standard method of encapsulating network-layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. The IPv6 Control Protocol (IPV6CP), which is an NCP for a PPP link, allows for the negotiation of desirable parameters for an IPv6 interface over PPP. This document defines the IPv6 datagram compression option that can be negotiated by a node on the link through the IPV6CP. [STANDARDS TRACK] This document is a product of the IPv6 Maintenance 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 Mar 31 15:41:28 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 31 Mar 2008 15:41:28 -0700 (PDT) Subject: [rfc-dist] RFC 5167 on Media Server Control Protocol Requirements Message-ID: <20080331224128.C633C121D98@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5167 Title: Media Server Control Protocol Requirements Author: M. Dolly, R. Even Status: Informational Date: March 2008 Mailbox: mdolly at att.com, roni.even at polycom.co.il Pages: 9 Characters: 17147 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mediactrl-requirements-04.txt URL: http://www.rfc-editor.org/rfc/rfc5167.txt This document addresses the communication between an application server and media server. The current work in IETF working groups shows these logical entities, but it does not address the physical decomposition and the protocol between the entities. This document presents the requirements for a Media Server Control Protocol (MCP) that enables an application server to use a media server. It will address the aspects of announcements, Interactive Voice Response, and conferencing media services. This memo provides information for the Internet community. This document is a product of the Media Server Control 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 Mon Mar 31 15:41:30 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 31 Mar 2008 15:41:30 -0700 (PDT) Subject: [rfc-dist] RFC 5168 on XML Schema for Media Control Message-ID: <20080331224130.F32B5121D9A@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5168 Title: XML Schema for Media Control Author: O. Levin, R. Even, P. Hagendorf Status: Informational Date: March 2008 Mailbox: oritl at microsoft.com, roni.even at polycom.co.il, pierre at radvision.com Pages: 10 Characters: 17845 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-levin-mmusic-xml-media-control-13.txt URL: http://www.rfc-editor.org/rfc/rfc5168.txt This document defines an Extensible Markup Language (XML) Schema for video fast update in a tightly controlled environment, developed by Microsoft, Polycom, Radvision and used by multiple vendors. This document describes a method that has been deployed in Session Initiation Protocol (SIP) based systems over the last three years and is being used across real-time interactive applications from different vendors in an interoperable manner. New implementations are discouraged from using the method described except for backward compatibility purposes. New implementations are required to use the new Full Intra Request command in the RTP Control Protocol (RTCP) channel. 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 Mon Mar 31 15:41:23 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 31 Mar 2008 15:41:23 -0700 (PDT) Subject: [rfc-dist] RFC 5157 on IPv6 Implications for Network Scanning Message-ID: <20080331224123.A3DAC121D96@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5157 Title: IPv6 Implications for Network Scanning Author: T. Chown Status: Informational Date: March 2008 Mailbox: tjc at ecs.soton.ac.uk Pages: 13 Characters: 29054 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-v6ops-scanning-implications-04.txt URL: http://www.rfc-editor.org/rfc/rfc5157.txt The much larger default 64-bit subnet address space of IPv6 should in principle make traditional network (port) scanning techniques used by certain network worms or scanning tools less effective. While traditional network scanning probes (whether by individuals or automated via network worms) may become less common, administrators should be aware that attackers may use other techniques to discover IPv6 addresses on a target network, and thus they should also be aware of measures that are available to mitigate them. This informational document discusses approaches that administrators could take when planning their site address allocation and management strategies as part of a defence-in-depth approach to network security. This memo provides information for the Internet community. This document is a product of the IPv6 Operations 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 Mon Mar 31 15:41:33 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 31 Mar 2008 15:41:33 -0700 (PDT) Subject: [rfc-dist] RFC 5169 on Handover Key Management and Re-Authentication Problem Statement Message-ID: <20080331224133.35BA7121D9C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5169 Title: Handover Key Management and Re-Authentication Problem Statement Author: T. Clancy, M. Nakhjiri, V. Narayanan, L. Dondeti Status: Informational Date: March 2008 Mailbox: clancy at LTSnet.net, madjid.nakhjiri at motorola.com, vidyan at qualcomm.com, ldondeti at qualcomm.com Pages: 15 Characters: 34082 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hokey-reauth-ps-09.txt URL: http://www.rfc-editor.org/rfc/rfc5169.txt This document describes the Handover Keying (HOKEY) re-authentication problem statement. The current Extensible Authentication Protocol (EAP) keying framework is not designed to support re-authentication and handovers without re-executing an EAP method. This often causes unacceptable latency in various mobile wireless environments. This document details the problem and defines design goals for a generic mechanism to reuse derived EAP keying material for handover. This memo provides information for the Internet community. This document is a product of the Handover Keying 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 ...