From rfc-editor at rfc-editor.org Thu Aug 2 18:16:11 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 2 Aug 2007 18:16:11 -0700 (PDT) Subject: [rfc-dist] RFC 4950 on ICMP Extensions for Multiprotocol Label Switching Message-ID: <20070803011611.0A42EDEFB8@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4950 Title: ICMP Extensions for Multiprotocol Label Switching Author: R. Bonica, D. Gan, D. Tappan, C. Pignataro Status: Standards Track Date: August 2007 Mailbox: rbonica at juniper.net, derhwagan at yahoo.com, dan.tappan at gmail.com, cpignata at cisco.com Pages: 8 Characters: 15091 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-icmp-08.txt URL: http://www.rfc-editor.org/rfc/rfc4950.txt This memo defines an extension object that can be appended to selected multi-part ICMP messages. This extension permits Label Switching Routers to append MPLS information to ICMP messages, and has already been widely deployed. [STANDARDS TRACK] This document is a product of the Multiprotocol Label Switching 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 Aug 3 19:59:32 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 3 Aug 2007 19:59:32 -0700 (PDT) Subject: [rfc-dist] RFC 4968 on Analysis of IPv6 Link Models for 802.16 Based Networks Message-ID: <20070804025932.C5ED1DF039@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4968 Title: Analysis of IPv6 Link Models for 802.16 Based Networks Author: S. Madanapalli, Ed. Status: Informational Date: August 2007 Mailbox: smadanapalli at gmail.com Pages: 16 Characters: 34536 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-16ng-ipv6-link-model-analysis-03.txt URL: http://www.rfc-editor.org/rfc/rfc4968.txt This document provides different IPv6 link models that are suitable for IEEE 802.16 based networks and provides analysis of various considerations for each link model and the applicability of each link model under different deployment scenarios. This document is the result of a design team (DT) that was formed to analyze the IPv6 link models for IEEE 802.16 based networks. This memo provides information for the Internet community. This document is a product of the IP over IEEE 802.16 Networks 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 Aug 3 19:59:56 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 3 Aug 2007 19:59:56 -0700 (PDT) Subject: [rfc-dist] RFC 4936 on Fibre Channel Zone Server MIB Message-ID: <20070804025956.06C15DF03D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4936 Title: Fibre Channel Zone Server MIB Author: C. DeSanti, H.K. Vivek, K. McCloghrie, S. Gai Status: Standards Track Date: August 2007 Mailbox: cds at cisco.com, hvivek at cisco.com, kzm at cisco.com, sgai at nuovasystems.com Pages: 84 Characters: 170801 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-imss-fc-zs-mib-03.txt URL: http://www.rfc-editor.org/rfc/rfc4936.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for information related to a Fibre Channel Zone Server. [STANDARDS TRACK] This document is a product of the Internet and Management Support for Storage 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 Aug 3 19:59:45 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 3 Aug 2007 19:59:45 -0700 (PDT) Subject: [rfc-dist] RFC 4935 on Fibre Channel Fabric Configuration Server MIB Message-ID: <20070804025945.C75BEDF03B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4935 Title: Fibre Channel Fabric Configuration Server MIB Author: C. DeSanti, H.K. Vivek, K. McCloghrie, S. Gai Status: Standards Track Date: August 2007 Mailbox: cds at cisco.com, hvivek at cisco.com, kzm at cisco.com, sgai at nuovasystems.com Pages: 50 Characters: 97345 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-imss-fc-fcs-mib-02.txt URL: http://www.rfc-editor.org/rfc/rfc4935.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for information related to the Fabric Configuration Server function of a Fibre Channel network. [STANDARDS TRACK] This document is a product of the Internet and Management Support for Storage 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 Aug 7 17:35:24 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 7 Aug 2007 17:35:24 -0700 (PDT) Subject: [rfc-dist] RFC 4974 on Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of Calls Message-ID: <20070808003524.9BA52DF442@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4974 Title: Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of Calls Author: D. Papadimitriou, A. Farrel Status: Standards Track Date: August 2007 Mailbox: dimitri.papadimitriou at alcatel-lucent.be, adrian at olddog.co.uk Pages: 31 Characters: 72000 Updates: RFC3473 See-Also: I-D Tag: draft-ietf-ccamp-gmpls-rsvp-te-call-04.txt URL: http://www.rfc-editor.org/rfc/rfc4974.txt In certain networking topologies, it may be advantageous to maintain associations between endpoints and key transit points to support an instance of a service. Such associations are known as Calls. A Call does not provide the actual connectivity for transmitting user traffic, but only builds a relationship by which subsequent Connections may be made. In Generalized MPLS (GMPLS) such Connections are known as Label Switched Paths (LSPs). This document specifies how GMPLS Resource Reservation Protocol - Traffic Engineering (RSVP-TE) signaling may be used and extended to support Calls. These mechanisms provide full and logical Call/Connection separation. The mechanisms proposed in this document are applicable to any environment (including multi-area), and for any type of interface: packet, layer-2, time-division multiplexed, lambda, or fiber switching. [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 Tue Aug 7 17:35:34 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 7 Aug 2007 17:35:34 -0700 (PDT) Subject: [rfc-dist] RFC 4979 on IANA Registration for Enumservice 'XMPP' Message-ID: <20070808003534.D2B0FDF444@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4979 Title: IANA Registration for Enumservice 'XMPP' Author: A. Mayrhofer Status: Standards Track Date: August 2007 Mailbox: alexander.mayrhofer at enum.at Pages: 7 Characters: 11719 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-enum-xmpp-02.txt URL: http://www.rfc-editor.org/rfc/rfc4979.txt This document requests IANA registration of an Enumservice for XMPP, the Extensible Messaging and Presence Protocol. This Enumservice specifically allows the use of 'xmpp' Uniform Resource Identifiers (URIs) in the context of E.164 Number Mapping (ENUM). [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 Tue Aug 7 17:35:49 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 7 Aug 2007 17:35:49 -0700 (PDT) Subject: [rfc-dist] RFC 5052 on Forward Error Correction (FEC) Building Block Message-ID: <20070808003549.89E47DF446@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5052 Title: Forward Error Correction (FEC) Building Block Author: M. Watson, M. Luby, L. Vicisano Status: Standards Track Date: August 2007 Mailbox: mark at digitalfountain.com, luby at digitalfountain.com, lorenzo at digitalfountain.com Pages: 25 Characters: 57754 Obsoletes: RFC3452 See-Also: I-D Tag: draft-ietf-rmt-fec-bb-revised-07.txt URL: http://www.rfc-editor.org/rfc/rfc5052.txt This document describes how to use Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for bulk data transfer over IP multicast. This document defines a framework for the definition of the information that needs to be communicated in order to use an FEC code for bulk data transfer, in addition to the encoded data itself, and for definition of formats and codes for communication of that information. Both information communicated with the encoded data itself and information that needs to be communicated 'out-of-band' are considered. The procedures for specifying new FEC codes, defining the information communication requirements associated with those codes and registering them with the Internet Assigned Numbers Authority (IANA) are also described. The requirements on Content Delivery Protocols that wish to use FEC codes defined within this framework are also defined. The companion document titled "The Use of Forward Error Correction (FEC) in Reliable Multicast" describes some applications of FEC codes for delivering content. This document obsoletes RFC 3452. [STANDARDS TRACK] This document is a product of the Reliable Multicast 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 Tue Aug 7 17:36:52 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 7 Aug 2007 17:36:52 -0700 (PDT) Subject: [rfc-dist] RFC 4992 on XML Pipelining with Chunks for the Internet Registry Information Service Message-ID: <20070808003652.E72CDDF450@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4992 Title: XML Pipelining with Chunks for the Internet Registry Information Service Author: A. Newton Status: Standards Track Date: August 2007 Mailbox: andy at hxr.us Pages: 29 Characters: 55848 Updates: RFC3981 See-Also: I-D Tag: draft-ietf-crisp-iris-xpc-06.txt URL: http://www.rfc-editor.org/rfc/rfc4992.txt This document describes a simple TCP transfer protocol for the Internet Registry Information Service (IRIS). Data is transferred between clients and servers using chunks to achieve pipelining. [STANDARDS TRACK] This document is a product of the Cross Registry Information Service 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 Tue Aug 7 17:37:04 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 7 Aug 2007 17:37:04 -0700 (PDT) Subject: [rfc-dist] RFC 4993 on A Lightweight UDP Transfer Protocol for the Internet Registry Information Service Message-ID: <20070808003704.1430BDF452@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4993 Title: A Lightweight UDP Transfer Protocol for the Internet Registry Information Service Author: A. Newton Status: Standards Track Date: August 2007 Mailbox: andy at hxr.us Pages: 19 Characters: 34383 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-crisp-iris-lwz-08.txt URL: http://www.rfc-editor.org/rfc/rfc4993.txt This document describes a lightweight UDP transfer protocol for the Internet Registry Information Service (IRIS). This transfer protocol uses a single packet for every request and response, and optionally employs compression over the contents of the packet. [STANDARDS TRACK] This document is a product of the Cross Registry Information Service 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 Tue Aug 7 17:36:40 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 7 Aug 2007 17:36:40 -0700 (PDT) Subject: [rfc-dist] RFC 4991 on A Common Schema for Internet Registry Information Service Transfer Protocols Message-ID: <20070808003640.17145DF44E@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4991 Title: A Common Schema for Internet Registry Information Service Transfer Protocols Author: A. Newton Status: Standards Track Date: August 2007 Mailbox: andy at hxr.us Pages: 13 Characters: 24418 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-crisp-iris-common-transport-05.txt URL: http://www.rfc-editor.org/rfc/rfc4991.txt This document describes an XML Schema for use by Internet Registry Information Service (IRIS) application transfer protocols that share common characteristics. It describes common information about the transfer protocol, such as version, supported extensions, and supported security mechanisms. [STANDARDS TRACK] This document is a product of the Cross Registry Information Service 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 Tue Aug 7 17:36:16 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 7 Aug 2007 17:36:16 -0700 (PDT) Subject: [rfc-dist] RFC 4969 on IANA Registration for vCard Enumservice Message-ID: <20070808003616.A6125DF44A@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4969 Title: IANA Registration for vCard Enumservice Author: A. Mayrhofer Status: Standards Track Date: August 2007 Mailbox: alexander.mayrhofer at enum.at Pages: 7 Characters: 14038 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-enum-vcard-06.txt URL: http://www.rfc-editor.org/rfc/rfc4969.txt This memo registers the Enumservice "vCard" using the URI schemes "http" and "https". This Enumservice is to be used to refer from an ENUM domain name to a vCard instance describing the user of the respective E.164 number. Information gathered from those vCards could be used before, during, or after inbound or outbound communication takes place. For example, a callee might be presented with the name and association of the caller before picking up the call. [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 Tue Aug 7 17:36:26 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 7 Aug 2007 17:36:26 -0700 (PDT) Subject: [rfc-dist] RFC 4957 on Link-Layer Event Notifications for Detecting Network Attachments Message-ID: <20070808003626.32DADDF44C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4957 Title: Link-Layer Event Notifications for Detecting Network Attachments Author: S. Krishnan, Ed., N. Montavont, E. Njedjou, S. Veerepalli, A. Yegin, Ed. Status: Informational Date: August 2007 Mailbox: suresh.krishnan at ericsson.com, nicolas.montavont at enst-bretagne.fr, eric.njedjou at orange-ftgroup.com, sivav at qualcomm.com, a.yegin at partner.samsung.com Pages: 18 Characters: 41840 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dna-link-information-06.txt URL: http://www.rfc-editor.org/rfc/rfc4957.txt Certain network access technologies are capable of providing various types of link-layer status information to IP. Link-layer event notifications can help IP expeditiously detect configuration changes. This document provides a non-exhaustive catalogue of information available from well-known access technologies. This memo provides information for the Internet community. This document is a product of the Detecting Network Attachment 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 Tue Aug 7 17:36:04 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 7 Aug 2007 17:36:04 -0700 (PDT) Subject: [rfc-dist] RFC 5065 on Autonomous System Confederations for BGP Message-ID: <20070808003604.BDACFDF448@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5065 Title: Autonomous System Confederations for BGP Author: P. Traina, D. McPherson, J. Scudder Status: Standards Track Date: August 2007 Mailbox: bgp-confederations at st04.pst.org, danny at arbor.net, jgs at juniper.net Pages: 14 Characters: 28732 Obsoletes: RFC3065 See-Also: I-D Tag: draft-ietf-idr-rfc3065bis-06.txt URL: http://www.rfc-editor.org/rfc/rfc5065.txt The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for Transmission Control Protocol/Internet Protocol (TCP/IP) networks. BGP requires that all BGP speakers within a single autonomous system (AS) must be fully meshed. This represents a serious scaling problem that has been well documented in a number of proposals. This document describes an extension to BGP that may be used to create a confederation of autonomous systems that is represented as a single autonomous system to BGP peers external to the confederation, thereby removing the "full mesh" requirement. The intention of this extension is to aid in policy administration and reduce the management complexity of maintaining a large autonomous system. This document obsoletes RFC 3065. [STANDARDSD TRACK] This document is a product of the Inter-Domain Routing Working Group of the IETF. This is now a Draft 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 Aug 10 17:49:02 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 10 Aug 2007 17:49:02 -0700 (PDT) Subject: [rfc-dist] RFC 5020 on The Lightweight Directory Access Protocol (LDAP) entryDN Operational Attribute Message-ID: <20070811004902.25B79DF607@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5020 Title: The Lightweight Directory Access Protocol (LDAP) entryDN Operational Attribute Author: K. Zeilenga Status: Standards Track Date: August 2007 Mailbox: Kurt.Zeilenga at Isode.COM Pages: 5 Characters: 8607 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-zeilenga-ldap-entrydn-02.txt URL: http://www.rfc-editor.org/rfc/rfc5020.txt This document describes the Lightweight Directory Access Protocol (LDAP) / X.500 'entryDN' operational attribute. The attribute provides a copy of the entry's distinguished name for use in attribute value assertions. [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 Aug 10 17:49:14 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 10 Aug 2007 17:49:14 -0700 (PDT) Subject: [rfc-dist] RFC 4945 on The Internet IP Security PKI Profile of IKEv1/ISAKMP, IKEv2, and PKIX Message-ID: <20070811004914.6B2C2DF609@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4945 Title: The Internet IP Security PKI Profile of IKEv1/ISAKMP, IKEv2, and PKIX Author: B. Korver Status: Standards Track Date: August 2007 Mailbox: briank at networkresonance.com Pages: 43 Characters: 101495 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pki4ipsec-ikecert-profile-12.txt URL: http://www.rfc-editor.org/rfc/rfc4945.txt The Internet Key Exchange (IKE) and Public Key Infrastructure for X.509 (PKIX) certificate profile both provide frameworks that must be profiled for use in a given application. This document provides a profile of IKE and PKIX that defines the requirements for using PKI technology in the context of IKE/IPsec. The document complements protocol specifications such as IKEv1 and IKEv2, which assume the existence of public key certificates and related keying materials, but which do not address PKI issues explicitly. This document addresses those issues. The intended audience is implementers of PKI for IPsec. [STANDARDS TRACK] This document is a product of the Profiling Use of PKI in IPSEC 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 Aug 15 16:10:52 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 15 Aug 2007 16:10:52 -0700 (PDT) Subject: [rfc-dist] RFC 4919 on IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals Message-ID: <20070815231052.AC83FDFA24@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4919 Title: IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals Author: N. Kushalnagar, G. Montenegro, C. Schumacher Status: Informational Date: August 2007 Mailbox: nandakishore.kushalnagar at intel.com, gabriel.montenegro at microsoft.com, schumacher at danfoss.com Pages: 12 Characters: 27650 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-6lowpan-problem-08.txt URL: http://www.rfc-editor.org/rfc/rfc4919.txt This document describes the assumptions, problem statement, and goals for transmitting IP over IEEE 802.15.4 networks. The set of goals enumerated in this document form an initial set only. This memo provides information for the Internet community. This document is a product of the IPv6 over Low power WPAN 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 Aug 15 16:10:43 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 15 Aug 2007 16:10:43 -0700 (PDT) Subject: [rfc-dist] RFC 4923 on Quality of Service (QoS) Signaling in a Nested Virtual Private Network Message-ID: <20070815231043.DA55DDFA22@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4923 Title: Quality of Service (QoS) Signaling in a Nested Virtual Private Network Author: F. Baker, P. Bose Status: Informational Date: August 2007 Mailbox: fred at cisco.com, pratik.bose at lmco.com Pages: 38 Characters: 92632 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tsvwg-vpn-signaled-preemption-02.txt URL: http://www.rfc-editor.org/rfc/rfc4923.txt Some networks require communication between an interior and exterior portion of a Virtual Private Network (VPN) or through a concatenation of such networks resulting in a nested VPN, but have sensitivities about what information is communicated across the boundary, especially while providing quality of service to communications with different precedence. This note seeks to outline the issues and the nature of the proposed solutions based on the framework for Integrated Services operation over Diffserv networks as described in RFC 2998. This memo provides information for the Internet community. This document is a product of the Transport Area Working Group 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 Aug 15 16:10:33 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 15 Aug 2007 16:10:33 -0700 (PDT) Subject: [rfc-dist] RFC 4948 on Report from the IAB workshop on Unwanted Traffic March 9-10, 2006 Message-ID: <20070815231033.8F127DFA20@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4948 Title: Report from the IAB workshop on Unwanted Traffic March 9-10, 2006 Author: L. Andersson, E. Davies, L. Zhang Status: Informational Date: August 2007 Mailbox: loa at pi.se, elwynd at dial.pipex.com, lixia at cs.ucla.edu Pages: 43 Characters: 106199 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-iwout-report-03.txt URL: http://www.rfc-editor.org/rfc/rfc4948.txt This document reports the outcome of a workshop held by the Internet Architecture Board (IAB) on Unwanted Internet Traffic. The workshop was held on March 9-10, 2006 at USC/ISI in Marina del Rey, CA, USA. The primary goal of the workshop was to foster interchange between the operator, standards, and research communities on the topic of unwanted traffic, as manifested in, for example, Distributed Denial of Service (DDoS) attacks, spam, and phishing, to gain understandings on the ultimate sources of these unwanted traffic, and to assess their impact and the effectiveness of existing solutions. It was also a goal of the workshop to identify engineering and research topics that could be undertaken by the IAB, the IETF, the IRTF, and the network research and development community at large to develop effective countermeasures against the unwanted traffic. This memo provides information for the Internet community. This document is a product of the Internet Architecture Board. 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 Aug 17 16:41:55 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 17 Aug 2007 16:41:55 -0700 (PDT) Subject: [rfc-dist] RFC 4987 on TCP SYN Flooding Attacks and Common Mitigations Message-ID: <20070817234155.5B926DFB23@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4987 Title: TCP SYN Flooding Attacks and Common Mitigations Author: W. Eddy Status: Informational Date: August 2007 Mailbox: weddy at grc.nasa.gov Pages: 19 Characters: 48753 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tcpm-syn-flood-05.txt URL: http://www.rfc-editor.org/rfc/rfc4987.txt This document describes TCP SYN flooding attacks, which have been well-known to the community for several years. Various countermeasures against these attacks, and the trade-offs of each, are described. This document archives explanations of the attack and common defense techniques for the benefit of TCP implementers and administrators of TCP servers or networks, but does not make any standards-level recommendations. This memo provides information for the Internet community. This document is a product of the TCP Maintenance and Minor Extensions 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 Aug 17 16:42:03 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 17 Aug 2007 16:42:03 -0700 (PDT) Subject: [rfc-dist] RFC 5021 on Extended Kerberos Version 5 Key Distribution Center (KDC) Exchanges over TCP Message-ID: <20070817234203.8D615DFB27@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5021 Title: Extended Kerberos Version 5 Key Distribution Center (KDC) Exchanges over TCP Author: S. Josefsson Status: Standards Track Date: August 2007 Mailbox: simon at josefsson.org Pages: 7 Characters: 13431 Updates: RFC4120 See-Also: I-D Tag: draft-ietf-krb-wg-tcp-expansion-02.txt URL: http://www.rfc-editor.org/rfc/rfc5021.txt This document describes an extensibility mechanism for the Kerberos V5 protocol when used over TCP transports. The mechanism uses the reserved high-bit in the length field. It can be used to negotiate TCP-specific Kerberos extensions. [STANDARDS TRACK] This document is a product of the Kerberos WG 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 Aug 17 16:42:01 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 17 Aug 2007 16:42:01 -0700 (PDT) Subject: [rfc-dist] RFC 4998 on Evidence Record Syntax (ERS) Message-ID: <20070817234201.9531ADFB25@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4998 Title: Evidence Record Syntax (ERS) Author: T. Gondrom, R. Brandner, U. Pordesch Status: Standards Track Date: August 2007 Mailbox: tobias.gondrom at opentext.com, ralf.brandner at intercomponentware.com, ulrich.pordesch at zv.fraunhofer.de Pages: 32 Characters: 66888 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ltans-ers-15.txt URL: http://www.rfc-editor.org/rfc/rfc4998.txt In many scenarios, users must be able prove the existence and integrity of data, including digitally signed data, in a common and reproducible way over a long and possibly undetermined period of time. This document specifies the syntax and processing of an Evidence Record, a structure designed to support long-term non-repudiation of existence of data. [STANDARDS TRACK] This document is a product of the Long-Term Archive and Notary Services 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 Aug 20 17:09:15 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 20 Aug 2007 17:09:15 -0700 (PDT) Subject: [rfc-dist] FYI 36, RFC 4949 on Internet Security Glossary, Version 2 Message-ID: <20070821000915.34B15DFE5C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. FYI0036 RFC 4949 Title: Internet Security Glossary, Version 2 Author: R. Shirey Status: Informational Date: August 2007 Mailbox: rwshirey4949 at verizon.net Pages: 365 Characters: 867626 I-D Tag: draft-shirey-secgloss-v2-08.txt URL: http://www.rfc-editor.org/rfc/rfc4949.txt This Glossary provides definitions, abbreviations, and explanations of terminology for information system security. The 334 pages of entries offer recommendations to improve the comprehensibility of written material that is generated in the Internet Standards Process (RFC 2026). The recommendations follow the principles that such writing should (a) use the same term or definition whenever the same concept is mentioned; (b) use terms in their plainest, dictionary sense; (c) use terms that are already well-established in open publications; and (d) avoid terms that either favor a particular vendor or favor a particular technology or mechanism over other, competing techniques that already exist or could be developed. 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 Aug 20 17:09:26 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 20 Aug 2007 17:09:26 -0700 (PDT) Subject: [rfc-dist] RFC 5001 on DNS Name Server Identifier (NSID) Option Message-ID: <20070821000926.CC520DFE5E@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5001 Title: DNS Name Server Identifier (NSID) Option Author: R. Austein Status: Standards Track Date: August 2007 Mailbox: sra at isc.org Pages: 11 Characters: 23754 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dnsext-nsid-02.txt URL: http://www.rfc-editor.org/rfc/rfc5001.txt With the increased use of DNS anycast, load balancing, and other mechanisms allowing more than one DNS name server to share a single IP address, it is sometimes difficult to tell which of a pool of name servers has answered a particular query. While existing ad-hoc mechanisms allow an operator to send follow-up queries when it is necessary to debug such a configuration, the only completely reliable way to obtain the identity of the name server that responded is to have the name server include this information in the response itself. This note defines a protocol extension to support this functionality. [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 Mon Aug 20 17:09:39 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 20 Aug 2007 17:09:39 -0700 (PDT) Subject: [rfc-dist] RFC 4951 on Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover" Message-ID: <20070821000939.189F5DFE60@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4951 Title: Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover" Author: V. Jain, Ed. Status: Standards Track Date: August 2007 Mailbox: vipinietf at yahoo.com Pages: 26 Characters: 53659 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l2tpext-failover-12.txt URL: http://www.rfc-editor.org/rfc/rfc4951.txt Layer 2 Tunneling Protocol (L2TP) is a connection-oriented protocol that has a shared state between active endpoints. Some of this shared state is vital for operation, but may be volatile in nature, such as packet sequence numbers used on the L2TP Control Connection. When failure of one side of a control connection occurs, a new control connection is created and associated with the old connection by exchanging information about the old connection. Such a mechanism is not intended as a replacement for an active fail over with some mirrored connection states, but as an aid for those parameters that are particularly difficult to have immediately available. Protocol extensions to L2TP defined in this document are intended to facilitate state recovery, providing additional resiliency in an L2TP network, and improving a remote system's layer 2 connectivity. [STANDARDS TRACK] This document is a product of the Layer Two Tunneling Protocol 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 Wed Aug 22 17:22:21 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 22 Aug 2007 17:22:21 -0700 (PDT) Subject: [rfc-dist] RFC 5013 on The Dublin Core Metadata Element Set Message-ID: <20070823002221.45273DFF52@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5013 Title: The Dublin Core Metadata Element Set Author: J. Kunze, T. Baker Status: Informational Date: August 2007 Mailbox: jak at ucop.edu, tbaker at tbaker.de Pages: 9 Characters: 17776 Obsoletes: RFC2413 See-Also: I-D Tag: draft-kunze-rfc2413bis-07.txt URL: http://www.rfc-editor.org/rfc/rfc5013.txt This document defines fifteen metadata elements for resource description in a cross-disciplinary information environment. 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 Wed Aug 22 17:22:23 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 22 Aug 2007 17:22:23 -0700 (PDT) Subject: [rfc-dist] BCP 133, RFC 5033 on Specifying New Congestion Control Algorithms Message-ID: <20070823002223.24391DFF54@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. BCP 133 RFC 5033 Title: Specifying New Congestion Control Algorithms Author: S. Floyd, M. Allman Status: Best Current Practice Date: August 2007 Mailbox: floyd at icir.org, mallman at icir.org Pages: 10 Characters: 23469 Updates: See-Also: BCP0133 I-D Tag: draft-ietf-tsvwg-cc-alt-04.txt URL: http://www.rfc-editor.org/rfc/rfc5033.txt The IETF's standard congestion control schemes have been widely shown to be inadequate for various environments (e.g., high-speed networks). Recent research has yielded many alternate congestion control schemes that significantly differ from the IETF's congestion control principles. Using these new congestion control schemes in the global Internet has possible ramifications to both the traffic using the new congestion control and to traffic using the currently standardized congestion control. Therefore, the IETF must proceed with caution when dealing with alternate congestion control proposals. The goal of this document is to provide guidance for considering alternate congestion control algorithms within the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document is a product of the Transport Area Working Group Working Group of the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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 Aug 24 15:55:35 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 24 Aug 2007 15:55:35 -0700 (PDT) Subject: [rfc-dist] RFC 5035 on Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility Message-ID: <20070824225535.2C332E0087@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5035 Title: Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility Author: J. Schaad Status: Standards Track Date: August 2007 Mailbox: jimsch at exmsft.com Pages: 17 Characters: 32674 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-smime-escertid-06.txt URL: http://www.rfc-editor.org/rfc/rfc5035.txt In the original Enhanced Security Services for S/MIME document (RFC 2634), a structure for cryptographically linking the certificate to be used in validation with the signature was introduced; this structure was hardwired to use SHA-1. This document allows for the structure to have algorithm agility and defines a new attribute for this purpose. [STANDARDS TRACK] This document is a product of the S/MIME Mail Security 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 Aug 24 15:55:20 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 24 Aug 2007 15:55:20 -0700 (PDT) Subject: [rfc-dist] RFC 4983 on Fibre Channel Registered State Change Notification (RSCN) MIB Message-ID: <20070824225520.A17F3E0085@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4983 Title: Fibre Channel Registered State Change Notification (RSCN) MIB Author: C. DeSanti, H.K. Vivek, K. McCloghrie, S. Gai Status: Standards Track Date: August 2007 Mailbox: cds at cisco.com, hvivek at cisco.com, kzm at cisco.com, sgai at nuovasystems.com Pages: 28 Characters: 56049 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-imss-fc-rscn-mib-02.txt URL: http://www.rfc-editor.org/rfc/rfc4983.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for information related to the management of Fibre Channel's Registered State Change Notifications (RSCNs). [STANDARDS TRACK] This document is a product of the Internet and Management Support for Storage 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 Aug 24 15:55:47 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 24 Aug 2007 15:55:47 -0700 (PDT) Subject: [rfc-dist] RFC 5002 on The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) Message-ID: <20070824225547.C259EE0089@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5002 Title: The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) Author: G. Camarillo, G. Blanco Status: Informational Date: August 2007 Mailbox: Gonzalo.Camarillo at ericsson.com, German.Blanco at ericsson.com Pages: 7 Characters: 15137 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-camarillo-sipping-profile-key-02.txt URL: http://www.rfc-editor.org/rfc/rfc5002.txt This document specifies the SIP P-Profile-Key P-header. This header field is used in the 3rd-Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) to provide SIP registrars and SIP proxy servers with the key of the profile corresponding to the destination SIP URI of a particular SIP request. 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 Aug 24 17:02:22 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 24 Aug 2007 17:02:22 -0700 (PDT) Subject: [rfc-dist] Corrected Announcement: RFC 5035 on Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility Message-ID: <20070825000222.7B254E008C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5035 Title: Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility Author: J. Schaad Status: Standards Track Date: August 2007 Mailbox: jimsch at exmsft.com Pages: 17 Characters: 32674 Updates: RFC2634 See-Also: I-D Tag: draft-ietf-smime-escertid-06.txt URL: http://www.rfc-editor.org/rfc/rfc5035.txt In the original Enhanced Security Services for S/MIME document (RFC 2634), a structure for cryptographically linking the certificate to be used in validation with the signature was introduced; this structure was hardwired to use SHA-1. This document allows for the structure to have algorithm agility and defines a new attribute for this purpose. [STANDARDS TRACK] This document is a product of the S/MIME Mail Security 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 Aug 29 14:09:41 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 29 Aug 2007 14:09:41 -0700 (PDT) Subject: [rfc-dist] RFC 4978 on The IMAP COMPRESS Extension Message-ID: <20070829210941.90CF4E0447@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4978 Title: The IMAP COMPRESS Extension Author: A. Gulbrandsen Status: Standards Track Date: August 2007 Mailbox: arnt at oryx.com Pages: 9 Characters: 17554 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lemonade-compress-08.txt URL: http://www.rfc-editor.org/rfc/rfc4978.txt The COMPRESS extension allows an IMAP connection to be effectively and efficiently compressed. [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 Wed Aug 29 14:09:26 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 29 Aug 2007 14:09:26 -0700 (PDT) Subject: [rfc-dist] RFC 4977 on Problem Statement: Dual Stack Mobility Message-ID: <20070829210926.EDF44E0445@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4977 Title: Problem Statement: Dual Stack Mobility Author: G. Tsirtsis, H. Soliman Status: Informational Date: August 2007 Mailbox: tsirtsis at qualcomm.com, hesham at elevatemobile.com Pages: 8 Characters: 16758 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip6-dsmip-problem-03.txt URL: http://www.rfc-editor.org/rfc/rfc4977.txt This document discusses the issues associated with mobility management for dual stack mobile nodes. Currently, two mobility management protocols are defined for IPv4 and IPv6. Deploying both in a dual stack mobile node introduces a number of problems. Deployment and operational issues motivate the use of a single mobility management protocol. This document discusses such motivations. The document also discusses requirements for the Mobile IPv4 (MIPv4) and Mobile IPv6 (MIPv6) protocol so that they can support mobility management for a dual stack node. This memo provides information for the Internet community. This document is a product of the Mobility for IPv6 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 Aug 29 14:09:56 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 29 Aug 2007 14:09:56 -0700 (PDT) Subject: [rfc-dist] RFC 4895 on Authenticated Chunks for the Stream Control Transmission Protocol (SCTP) Message-ID: <20070829210956.40A27E0449@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4895 Title: Authenticated Chunks for the Stream Control Transmission Protocol (SCTP) Author: M. Tuexen, R. Stewart, P. Lei, E. Rescorla Status: Standards Track Date: August 2007 Mailbox: tuexen at fh-muenster.de, rrs at cisco.com, peterlei at cisco.com, ekr at rtfm.com Pages: 19 Characters: 42507 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tsvwg-sctp-auth-08.txt URL: http://www.rfc-editor.org/rfc/rfc4895.txt This document describes a new chunk type, several parameters, and procedures for the Stream Control Transmission Protocol (SCTP). This new chunk type can be used to authenticate SCTP chunks by using shared keys between the sender and receiver. The new parameters are used to establish the shared keys. [STANDARDS TRACK] This document is a product of the Transport Area Working Group Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Aug 29 14:10:08 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 29 Aug 2007 14:10:08 -0700 (PDT) Subject: [rfc-dist] RFC 4986 on Requirements Related to DNS Security (DNSSEC) Trust Anchor Rollover Message-ID: <20070829211008.B987DE044B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4986 Title: Requirements Related to DNS Security (DNSSEC) Trust Anchor Rollover Author: H. Eland, R. Mundy, S. Crocker, S. Krishnaswamy Status: Informational Date: August 2007 Mailbox: heland at afilias.info, mundy at sparta.com, steve at shinkuro.com, suresh at sparta.com Pages: 11 Characters: 22647 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dnsext-rollover-requirements-04.txt URL: http://www.rfc-editor.org/rfc/rfc4986.txt Every DNS security-aware resolver must have at least one Trust Anchor to use as the basis for validating responses from DNS signed zones. For various reasons, most DNS security-aware resolvers are expected to have several Trust Anchors. For some operations, manual monitoring and updating of Trust Anchors may be feasible, but many operations will require automated methods for updating Trust Anchors in their security-aware resolvers. This document identifies the requirements that must be met by an automated DNS Trust Anchor rollover solution for security-aware DNS resolvers. This memo provides information for the Internet community. This document is a product of the DNS Extensions 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 Aug 29 14:10:18 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 29 Aug 2007 14:10:18 -0700 (PDT) Subject: [rfc-dist] RFC 4985 on Internet X.509 Public Key Infrastructure Subject Alternative Name for Expression of Service Name Message-ID: <20070829211018.EA2EAE044D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4985 Title: Internet X.509 Public Key Infrastructure Subject Alternative Name for Expression of Service Name Author: S. Santesson Status: Standards Track Date: August 2007 Mailbox: stefans at microsoft.com Pages: 10 Characters: 17868 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pkix-srvsan-05.txt URL: http://www.rfc-editor.org/rfc/rfc4985.txt This document defines a new name form for inclusion in the otherName field of an X.509 Subject Alternative Name extension that allows a certificate subject to be associated with the service name and domain name components of a DNS Service Resource Record. [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 ...