From rfc-editor at rfc-editor.org Wed Dec 12 15:04:45 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 12 Dec 2007 15:04:45 -0800 (PST) Subject: [rfc-dist] RFC 5071 on Dynamic Host Configuration Protocol Options Used by PXELINUX Message-ID: <20071212230445.3EDC5FF1FB@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5071 Title: Dynamic Host Configuration Protocol Options Used by PXELINUX Author: D. Hankins Status: Informational Date: December 2007 Mailbox: David_Hankins at isc.org Pages: 14 Characters: 26777 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-pxelinux-03.txt URL: http://www.rfc-editor.org/rfc/rfc5071.txt This document describes the use by PXELINUX of some DHCP Option Codes numbering from 208-211. This memo provides information for the Internet community. This document is a product of the Dynamic Host Configuration 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 Dec 12 15:06:01 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 12 Dec 2007 15:06:01 -0800 (PST) Subject: [rfc-dist] RFC 5095 on Deprecation of Type 0 Routing Headers in IPv6 Message-ID: <20071212230601.8E7D8FF201@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5095 Title: Deprecation of Type 0 Routing Headers in IPv6 Author: J. Abley, P. Savola, G. Neville-Neil Status: Standards Track Date: December 2007 Mailbox: jabley at ca.afilias.info, psavola at funet.fi, gnn at neville-neil.com Pages: 7 Characters: 13423 Updates: RFC2460, RFC4294 See-Also: I-D Tag: draft-ietf-ipv6-deprecate-rh0-01.txt URL: http://www.rfc-editor.org/rfc/rfc5095.txt The functionality provided by IPv6's Type 0 Routing Header can be exploited in order to achieve traffic amplification over a remote path for the purposes of generating denial-of-service traffic. This document updates the IPv6 specification to deprecate the use of IPv6 Type 0 Routing Headers, in light of this security concern. [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 Wed Dec 12 15:05:12 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 12 Dec 2007 15:05:12 -0800 (PST) Subject: [rfc-dist] RFC 5076 on ENUM Validation Information Mapping for the Extensible Provisioning Protocol Message-ID: <20071212230512.06DBBFF1FF@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5076 Title: ENUM Validation Information Mapping for the Extensible Provisioning Protocol Author: B. Hoeneisen Status: Standards Track Date: December 2007 Mailbox: hoeneisen at switch.ch Pages: 24 Characters: 44679 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-enum-validation-epp-06.txt URL: http://www.rfc-editor.org/rfc/rfc5076.txt This document describes an Extensible Provisioning Protocol (EPP) extension framework for mapping information about the validation process that has been applied for the E.164 number (or number range) that the E.164 Number Mapping (ENUM) domain name is based on. Specified in the Extensible Markup Language (XML), this mapping extends the EPP domain name mapping to provide an additional feature required for the provisioning of ENUM Domain Names. [STANDARDS TRACK] This document is a product of the Telephone Number Mapping 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 Dec 12 15:04:39 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 12 Dec 2007 15:04:39 -0800 (PST) Subject: [rfc-dist] RFC 5055 on Server-Based Certificate Validation Protocol (SCVP) Message-ID: <20071212230439.1632DFF1F9@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5055 Title: Server-Based Certificate Validation Protocol (SCVP) Author: T. Freeman, R. Housley, A. Malpani, D. Cooper, W. Polk Status: Standards Track Date: December 2007 Mailbox: trevorf at microsoft.com, housley at vigilsec.com, ambarish at yahoo.com, david.cooper at nist.gov, wpolk at nist.gov Pages: 88 Characters: 198764 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pkix-scvp-33.txt URL: http://www.rfc-editor.org/rfc/rfc5055.txt The Server-Based Certificate Validation Protocol (SCVP) allows a client to delegate certification path construction and certification path validation to a server. The path construction or validation (e.g., making sure that none of the certificates in the path are revoked) is performed according to a validation policy, which contains one or more trust anchors. It allows simplification of client implementations and use of a set of predefined validation policies. [STANDARDS TRACK] This document is a product of the Public-Key Infrastructure (X.509) 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 Dec 12 15:04:26 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 12 Dec 2007 15:04:26 -0800 (PST) Subject: [rfc-dist] RFC 5049 on Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP) Message-ID: <20071212230426.26957FF1F7@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5049 Title: Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP) Author: C. Bormann, Z. Liu, R. Price, G. Camarillo, Ed. Status: Standards Track Date: December 2007 Mailbox: cabo at tzi.org, zhigang.c.liu at nokia.com, richard.price at eads.com, Gonzalo.Camarillo at ericsson.com Pages: 21 Characters: 47891 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rohc-sigcomp-sip-08.txt URL: http://www.rfc-editor.org/rfc/rfc5049.txt This document describes some specifics that apply when Signaling Compression (SigComp) is applied to the Session Initiation Protocol (SIP), such as default minimum values of SigComp parameters, compartment and state management, and a few issues on SigComp over TCP. Any implementation of SigComp for use with SIP must conform to this document and SigComp, and in addition, support the SIP and Session Description Protocol (SDP) static dictionary. [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 Dec 12 15:05:01 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 12 Dec 2007 15:05:01 -0800 (PST) Subject: [rfc-dist] RFC 5073 on IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities Message-ID: <20071212230501.5EE4FFF1FD@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5073 Title: IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities Author: J.P. Vasseur, Ed., J.L. Le Roux, Ed. Status: Standards Track Date: December 2007 Mailbox: jpv at cisco.com, jeanlouis.leroux at orange-ftgroup.com Pages: 13 Characters: 27004 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-te-node-cap-05.txt URL: http://www.rfc-editor.org/rfc/rfc5073.txt It is highly desired, in several cases, to take into account Traffic Engineering (TE) node capabilities during Multi Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered Label Switched Path (TE-LSP) selection, such as, for instance, the capability to act as a branch Label Switching Router (LSR) of a Point-To-MultiPoint (P2MP) LSP. This requires advertising these capabilities within the Interior Gateway Protocol (IGP). For that purpose, this document specifies Open Shortest Path First (OSPF) and Intermediate System-Intermediate System (IS-IS) traffic engineering extensions for the advertisement of control plane and data plane traffic engineering node capabilities. [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 Mon Dec 17 17:01:25 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 17 Dec 2007 17:01:25 -0800 (PST) Subject: [rfc-dist] RFC 5131 on A MIB Textual Convention for Language Tags Message-ID: <20071218010125.81EA8100322@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5131 Title: A MIB Textual Convention for Language Tags Author: D. McWalter, Ed. Status: Standards Track Date: December 2007 Mailbox: dmcw at dataconnection.com Pages: 6 Characters: 11119 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-mcwalter-langtag-mib-03.txt URL: http://www.rfc-editor.org/rfc/rfc5131.txt This MIB module defines a textual convention to represent BCP 47 language tags. The intent is that this textual convention will be imported and used in MIB modules that would otherwise define their own representation. [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 Dec 17 17:01:41 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 17 Dec 2007 17:01:41 -0800 (PST) Subject: [rfc-dist] RFC 5132 on IP Multicast MIB Message-ID: <20071218010141.912FB100324@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5132 Title: IP Multicast MIB Author: D. McWalter, D. Thaler, A. Kessler Status: Standards Track Date: December 2007 Mailbox: dmcw at dataconnection.com, dthaler at windows.microsoft.com, kessler at cisco.com Pages: 59 Characters: 120340 Obsoletes: RFC2932 See-Also: I-D Tag: draft-ietf-mboned-ip-mcast-mib-07.txt URL: http://www.rfc-editor.org/rfc/rfc5132.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 objects used for managing multicast function, independent of the specific multicast protocol(s) in use. This document obsoletes RFC 2932. [STANDARDS TRACK] This document is a product of the MBONE Deployment 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 Dec 17 17:02:32 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 17 Dec 2007 17:02:32 -0800 (PST) Subject: [rfc-dist] RFC 5070 on The Incident Object Description Exchange Format Message-ID: <20071218010232.AA3B5100328@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5070 Title: The Incident Object Description Exchange Format Author: R. Danyliw, J. Meijer, Y. Demchenko Status: Standards Track Date: December 2007 Mailbox: rdd at cert.org, jan at flyingcloggies.nl, demch at chello.nl Pages: 92 Characters: 171529 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-inch-iodef-14.txt URL: http://www.rfc-editor.org/rfc/rfc5070.txt The Incident Object Description Exchange Format (IODEF) defines a data representation that provides a framework for sharing information commonly exchanged by Computer Security Incident Response Teams (CSIRTs) about computer security incidents. This document describes the information model for the IODEF and provides an associated data model specified with XML Schema. [STANDARDS TRACK] This document is a product of the Extended Incident Handling 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 Dec 17 17:02:18 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 17 Dec 2007 17:02:18 -0800 (PST) Subject: [rfc-dist] RFC 5109 on RTP Payload Format for Generic Forward Error Correction Message-ID: <20071218010218.A6A0B100326@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5109 Title: RTP Payload Format for Generic Forward Error Correction Author: A. Li, Ed. Status: Standards Track Date: December 2007 Mailbox: adamli at hyervision.com Pages: 44 Characters: 100538 Obsoletes: RFC2733, RFC3009 See-Also: I-D Tag: draft-ietf-avt-ulp-23.txt URL: http://www.rfc-editor.org/rfc/rfc5109.txt This document specifies a payload format for generic Forward Error Correction (FEC) for media data encapsulated in RTP. It is based on the exclusive-or (parity) operation. The payload format described in this document allows end systems to apply protection using various protection lengths and levels, in addition to using various protection group sizes to adapt to different media and channel characteristics. It enables complete recovery of the protected packets or partial recovery of the critical parts of the payload depending on the packet loss situation. This scheme is completely compatible with non-FEC-capable hosts, so the receivers in a multicast group that do not implement FEC can still work by simply ignoring the protection data. This specification obsoletes RFC 2733 and RFC 3009. The FEC specified in this document is not backward compatible with RFC 2733 and RFC 3009. [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 Mon Dec 17 17:02:59 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 17 Dec 2007 17:02:59 -0800 (PST) Subject: [rfc-dist] RFC 5025 on Presence Authorization Rules Message-ID: <20071218010259.7CFDB10032E@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5025 Title: Presence Authorization Rules Author: J. Rosenberg Status: Standards Track Date: December 2007 Mailbox: jdrosen at cisco.com Pages: 28 Characters: 65880 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-simple-presence-rules-10.txt URL: http://www.rfc-editor.org/rfc/rfc5025.txt Authorization is a key function in presence systems. Authorization policies, also known as authorization rules, specify what presence information can be given to which watchers, and when. This specification defines an Extensible Markup Language (XML) document format for expressing presence authorization rules. Such a document can be manipulated by clients using the XML Configuration Access Protocol (XCAP), although other techniques are permitted. [STANDARDS TRACK] This document is a product of the SIP for Instant Messaging and Presence Leveraging 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 Mon Dec 17 17:02:49 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 17 Dec 2007 17:02:49 -0800 (PST) Subject: [rfc-dist] RFC 5080 on Common Remote Authentication Dial In User Service (RADIUS) Implementation Issues and Suggested Fixes Message-ID: <20071218010249.6BEAF10032C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5080 Title: Common Remote Authentication Dial In User Service (RADIUS) Implementation Issues and Suggested Fixes Author: D. Nelson, A. DeKok Status: Standards Track Date: December 2007 Mailbox: dnelson at elbrysnetworks.com, aland at freeradius.org Pages: 28 Characters: 64138 Updates: RFC2865, RFC2866, RFC2869, RFC3579 See-Also: I-D Tag: draft-ietf-radext-fixes-08.txt URL: http://www.rfc-editor.org/rfc/rfc5080.txt This document describes common issues seen in Remote Authentication Dial In User Service (RADIUS) implementations and suggests some fixes. Where applicable, ambiguities and errors in previous RADIUS specifications are clarified. [STANDARDS TRACK] This document is a product of the RADIUS 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 Mon Dec 17 17:03:58 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 17 Dec 2007 17:03:58 -0800 (PST) Subject: [rfc-dist] RFC 5096 on Mobile IPv6 Experimental Messages Message-ID: <20071218010358.82B2F100338@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5096 Title: Mobile IPv6 Experimental Messages Author: V. Devarapalli Status: Standards Track Date: December 2007 Mailbox: vijay.devarapalli at azairenet.com Pages: 7 Characters: 13669 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip6-experimental-messages-03.txt URL: http://www.rfc-editor.org/rfc/rfc5096.txt This document defines a new experimental Mobility Header message and a Mobility option that can be used for experimental extensions to the Mobile IPv6 protocol. [STANDARDS TRACK] This document is a product of the Mobility for IPv6 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 Dec 17 17:03:50 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 17 Dec 2007 17:03:50 -0800 (PST) Subject: [rfc-dist] RFC 5094 on Mobile IPv6 Vendor Specific Option Message-ID: <20071218010350.6B5F8100336@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5094 Title: Mobile IPv6 Vendor Specific Option Author: V. Devarapalli, A. Patel, K. Leung Status: Standards Track Date: December 2007 Mailbox: vijay.devarapalli at azairenet.com, alpesh at cisco.com, kleung at cisco.com Pages: 7 Characters: 11430 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip6-vsm-03.txt URL: http://www.rfc-editor.org/rfc/rfc5094.txt There is a need for vendor-specific extensions to Mobility Header messages so that Mobile IPv6 vendors are able to extend the protocol for research or deployment purposes. This document defines a new vendor-specific mobility option. [STANDARDS TRACK] This document is a product of the Mobility for IPv6 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 Dec 17 17:03:17 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 17 Dec 2007 17:03:17 -0800 (PST) Subject: [rfc-dist] RFC 5079 on Rejecting Anonymous Requests in the Session Initiation Protocol (SIP) Message-ID: <20071218010317.D92D0100330@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5079 Title: Rejecting Anonymous Requests in the Session Initiation Protocol (SIP) Author: J. Rosenberg Status: Standards Track Date: December 2007 Mailbox: jdrosen at cisco.com Pages: 8 Characters: 15670 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sip-acr-code-05.txt URL: http://www.rfc-editor.org/rfc/rfc5079.txt The Session Initiation Protocol (SIP) allows for users to make anonymous calls. However, users receiving such calls have the right to reject them because they are anonymous. SIP has no way to indicate to the caller that the reason for call rejection was that the call was anonymous. Such an indication is useful to allow the call to be retried without anonymity. This specification defines a new SIP response code for this purpose. [STANDARDS TRACK] This document is a product of the Session Initiation Protocol 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 Dec 17 17:03:40 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 17 Dec 2007 17:03:40 -0800 (PST) Subject: [rfc-dist] RFC 5087 on Time Division Multiplexing over IP (TDMoIP) Message-ID: <20071218010340.1BAC2100334@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5087 Title: Time Division Multiplexing over IP (TDMoIP) Author: Y(J). Stein, R. Shashoua, R. Insler, M. Anavi Status: Informational Date: December 2007 Mailbox: yaakov_s at rad.com, ronen_s at rad.com, ron_i at rad.com, motty at radusa.com Pages: 50 Characters: 113071 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pwe3-tdmoip-06.txt URL: http://www.rfc-editor.org/rfc/rfc5087.txt Time Division Multiplexing over IP (TDMoIP) is a structure-aware method for transporting Time Division Multiplexed (TDM) signals using pseudowires (PWs). Being structure-aware, TDMoIP is able to ensure TDM structure integrity, and thus withstand network degradations better than structure-agnostic transport. Structure-aware methods can distinguish individual channels, enabling packet loss concealment and bandwidth conservation. Accessibility of TDM signaling facilitates mechanisms that exploit or manipulate signaling. This memo provides information for the Internet community. This document is a product of the Pseudo Wire Emulation Edge to Edge 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 Dec 17 17:03:30 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 17 Dec 2007 17:03:30 -0800 (PST) Subject: [rfc-dist] RFC 5086 on Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN) Message-ID: <20071218010330.EE7AC100332@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5086 Title: Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN) Author: A. Vainshtein, Ed., I. Sasson, E. Metz, T. Frost, P. Pate Status: Informational Date: December 2007 Mailbox: sasha at axerra.com, israel at axerra.com, e.t.metz at telecom.tno.nl, tfrost at symmetricom.com, prayson.pate at overturenetworks.com Pages: 38 Characters: 83233 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pwe3-cesopsn-07.txt URL: http://www.rfc-editor.org/rfc/rfc5086.txt This document describes a method for encapsulating structured (NxDS0) Time Division Multiplexed (TDM) signals as pseudowires over packet-switching networks (PSNs). In this regard, it complements similar work for structure-agnostic emulation of TDM bit-streams (see RFC 4553). This memo provides information for the Internet community. This document is a product of the Pseudo Wire Emulation Edge to Edge 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 Dec 21 14:58:37 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Dec 2007 14:58:37 -0800 (PST) Subject: [rfc-dist] RFC 5064 on The Archived-At Message Header Field Message-ID: <20071221225837.422BE1052B9@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5064 Title: The Archived-At Message Header Field Author: M. Duerst Status: Standards Track Date: December 2007 Mailbox: duerst at it.aoyama.ac.jp Pages: 10 Characters: 20863 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-duerst-archived-at-09.txt URL: http://www.rfc-editor.org/rfc/rfc5064.txt This memo defines a new email header field, Archived-At:, to provide a direct link to the archived form of an individual email message. [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 Dec 21 14:58:46 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Dec 2007 14:58:46 -0800 (PST) Subject: [rfc-dist] RFC 5085 on Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires Message-ID: <20071221225846.44F981052BB@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5085 Title: Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires Author: T. Nadeau, Ed., C. Pignataro, Ed. Status: Standards Track Date: December 2007 Mailbox: tnadeau at lucidvision.com, cpignata at cisco.com Pages: 30 Characters: 67847 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pwe3-vccv-15.txt URL: http://www.rfc-editor.org/rfc/rfc5085.txt This document describes Virtual Circuit Connectivity Verification (VCCV), which provides a control channel that is associated with a pseudowire (PW), as well as the corresponding operations and management functions (such as connectivity verification) to be used over that control channel. VCCV applies to all supported access circuit and transport types currently defined for PWs. [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 Dec 21 14:58:56 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Dec 2007 14:58:56 -0800 (PST) Subject: [rfc-dist] RFC 5091 on Identity-Based Cryptography Standard (IBCS) #1: Supersingular Curve Implementations of the BF and BB1 Cryptosystems Message-ID: <20071221225856.A8B471052BD@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5091 Title: Identity-Based Cryptography Standard (IBCS) #1: Supersingular Curve Implementations of the BF and BB1 Cryptosystems Author: X. Boyen, L. Martin Status: Informational Date: December 2007 Mailbox: xavier at voltage.com, martin at voltage.com Pages: 63 Characters: 103464 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-martin-ibcs-07.txt URL: http://www.rfc-editor.org/rfc/rfc5091.txt This document describes the algorithms that implement Boneh-Franklin (BF) and Boneh-Boyen (BB1) Identity-based Encryption. This document is in part based on IBCS #1 v2 of Voltage Security's Identity-based Cryptography Standards (IBCS) documents, from which some irrelevant sections have been removed to create the content of this document. 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 Dec 21 14:59:05 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Dec 2007 14:59:05 -0800 (PST) Subject: [rfc-dist] RFC 5093 on BT's eXtended Network Quality RTP Control Protocol Extended Reports (RTCP XR XNQ) Message-ID: <20071221225905.F0E881052BF@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5093 Title: BT's eXtended Network Quality RTP Control Protocol Extended Reports (RTCP XR XNQ) Author: G. Hunt Status: Informational Date: December 2007 Mailbox: geoff.hunt at bt.com Pages: 8 Characters: 15110 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-hunt-avt-rtcpxnq-01.txt URL: http://www.rfc-editor.org/rfc/rfc5093.txt This document describes an RTCP XR report block, which reports packet transport parameters. The report block was developed by BT for pre-standards use in BT's next-generation network. This document has been produced to describe the report block in sufficient detail to register the block type with IANA in accordance with the Specification Required policy of RFC 3611. This specification does not standardise the new report block for use outside BT's network. 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 Dec 21 14:59:35 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Dec 2007 14:59:35 -0800 (PST) Subject: [rfc-dist] RFC 5105 on ENUM Validation Token Format Definition Message-ID: <20071221225935.397641052C3@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5105 Title: ENUM Validation Token Format Definition Author: O. Lendl Status: Standards Track Date: December 2007 Mailbox: otmar.lendl at enum.at Pages: 17 Characters: 33057 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-enum-validation-token-04.txt URL: http://www.rfc-editor.org/rfc/rfc5105.txt An ENUM domain name is tightly coupled with the underlying E.164 number. The process of verifying whether the Registrant of an ENUM domain name is identical to the Assignee of the corresponding E.164 number is commonly called "validation". This document describes a signed XML data format -- the Validation Token -- with which Validation Entities can convey successful completion of a validation procedure in a secure fashion. [STANDARDS TRACK] This document is a product of the Telephone Number Mapping 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 Dec 21 14:59:20 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 21 Dec 2007 14:59:20 -0800 (PST) Subject: [rfc-dist] RFC 5133 on Terminal Endpoint Identifier (TEI) Query Request Number Change Message-ID: <20071221225920.572ED1052C1@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5133 Title: Terminal Endpoint Identifier (TEI) Query Request Number Change Author: M. Tuexen, K. Morneault Status: Standards Track Date: December 2007 Mailbox: tuexen at fh-muenster.de, kmorneau at cisco.com Pages: 4 Characters: 7279 Obsoletes: RFC4233 See-Also: I-D Tag: draft-ietf-sigtran-rfc4233update-02.txt URL: http://www.rfc-editor.org/rfc/rfc5133.txt The Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer (IUA) Protocol, described in RFC 4233, defines the message type of Terminal Endpoint Identifier (TEI) Query Request messages as 5. However, this number is already being used by the Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions (DUA) to the IUA Protocol described in RFC 4129. This document updates RFC 4233 such that the message type of TEI Query Request messages is 8. [STANDARDS TRACK] This document is a product of the Signaling 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 ...