From rfc-editor at rfc-editor.org Tue Jul 10 17:28:22 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 10 Jul 2007 17:28:22 -0700 (PDT) Subject: [rfc-dist] RFC 4837 on Managed Objects of Ethernet Passive Optical Networks (EPON) Message-ID: <20070711002822.0888BD9A15@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4837 Title: Managed Objects of Ethernet Passive Optical Networks (EPON) Author: L. Khermosh Status: Standards Track Date: July 2007 Mailbox: lior_khermosh at pmc-sierra.com Pages: 91 Characters: 206726 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hubmib-efm-epon-mib-06.txt URL: http://www.rfc-editor.org/rfc/rfc4837.txt This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based Internets. In particular, it defines objects for managing interfaces that conform to the Ethernet Passive Optical Networks (EPON) standard as defined in the IEEE Std 802.3ah-2004, which are extended capabilities to the Ethernet like interfaces. [STANDARDS TRACK] This document is a product of the Ethernet Interfaces and Hub MIB 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 Jul 10 17:28:27 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 10 Jul 2007 17:28:27 -0700 (PDT) Subject: [rfc-dist] RFC 4926 on A URN Namespace for GEANT Message-ID: <20070711002827.A3202D9A17@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4926 Title: A URN Namespace for GEANT Author: T. Kalin, M. Molina Status: Informational Date: July 2007 Mailbox: tomaz.kalin at dante.org.uk, maurizio.molina at dante.org.uk Pages: 9 Characters: 16672 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-kalin-geant-urn-namespace-01.txt URL: http://www.rfc-editor.org/rfc/rfc4926.txt This document describes a proposed URN (Uniform Resource Name) namespace that would be managed by DANTE, representing European Research and academic networks, for naming persistent resources defined by GEANT, the Consortium of European Academic and Research Networks, its projects, activities, working groups, and other designated subordinates. 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 Sat Jul 14 13:26:10 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 14 Jul 2007 13:26:10 -0700 (PDT) Subject: [rfc-dist] RFC 4912 on Abstract Syntax Notation X (ASN.X) Message-ID: <20070714202610.8435FDA2B1@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4912 Title: Abstract Syntax Notation X (ASN.X) Author: S. Legg Status: Experimental Date: July 2007 Mailbox: steven.legg at eb2bcom.com Pages: 165 Characters: 325190 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-legg-xed-asd-07.txt URL: http://www.rfc-editor.org/rfc/rfc4912.txt Abstract Syntax Notation X (ASN.X) is a semantically equivalent Extensible Markup Language (XML) representation for Abstract Syntax Notation One (ASN.1) specifications. ASN.X completely avoids the numerous ambiguities inherent in the ASN.1 language; therefore, specifications written in ASN.X are much easier to parse and manage than original ASN.1 specifications. ASN.X, together with the Robust XML Encoding Rules (RXER), constitutes a schema language for XML documents that offers, through other ASN.1 encoding rules, alternative compact binary encodings for XML instance documents. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Sat Jul 14 13:26:12 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 14 Jul 2007 13:26:12 -0700 (PDT) Subject: [rfc-dist] RFC 4914 on Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the XML Encoding Rules (XER Message-ID: <20070714202612.A3161DA2B3@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4914 Title: Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the XML Encoding Rules (XER Author: S. Legg Status: Experimental Date: July 2007 Mailbox: steven.legg at eb2bcom.com Pages: 38 Characters: 71526 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-legg-xed-asd-xerei-03.txt URL: http://www.rfc-editor.org/rfc/rfc4914.txt Abstract Syntax Notation X (ASN.X) is an Extensible Markup Language (XML) representation for Abstract Syntax Notation One (ASN.1) specifications. This document specifies the ASN.X representation of encoding instructions for the XML Encoding Rules (XER). This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Sat Jul 14 13:26:14 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 14 Jul 2007 13:26:14 -0700 (PDT) Subject: [rfc-dist] RFC 4910 on Robust XML Encoding Rules (RXER) for Abstract Syntax Notation One (ASN.1) Message-ID: <20070714202614.BBC29DA2BB@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4910 Title: Robust XML Encoding Rules (RXER) for Abstract Syntax Notation One (ASN.1) Author: S. Legg, D. Prager Status: Experimental Date: July 2007 Mailbox: steven.legg at eb2bcom.com, dap at austhink.com Pages: 80 Characters: 182175 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-legg-xed-rxer-07.txt URL: http://www.rfc-editor.org/rfc/rfc4910.txt This document defines a set of Abstract Syntax Notation One (ASN.1) encoding rules, called the Robust XML Encoding Rules or RXER, that produce an Extensible Markup Language (XML) representation for values of any given ASN.1 data type. Rules for producing a canonical RXER encoding are also defined. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Sat Jul 14 13:26:13 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 14 Jul 2007 13:26:13 -0700 (PDT) Subject: [rfc-dist] RFC 4913 on Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the Generic String Encoding Rules (GSER) Message-ID: <20070714202613.8AAA8DA2B5@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4913 Title: Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the Generic String Encoding Rules (GSER) Author: S. Legg Status: Experimental Date: July 2007 Mailbox: steven.legg at eb2bcom.com Pages: 9 Characters: 17194 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-legg-xed-asd-gserei-03.txt URL: http://www.rfc-editor.org/rfc/rfc4913.txt Abstract Syntax Notation X (ASN.X) is an Extensible Markup Language (XML) representation for Abstract Syntax Notation One (ASN.1) specifications. This document specifies the ASN.X representation of encoding instructions for the Generic String Encoding Rules (GSER). This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Sat Jul 14 13:26:14 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 14 Jul 2007 13:26:14 -0700 (PDT) Subject: [rfc-dist] RFC 4911 on Encoding Instructions for the Robust XML Encoding Rules (RXER) Message-ID: <20070714202614.3D764DA2B7@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4911 Title: Encoding Instructions for the Robust XML Encoding Rules (RXER) Author: S. Legg Status: Experimental Date: July 2007 Mailbox: steven.legg at eb2bcom.com Pages: 91 Characters: 178977 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-legg-xed-rxer-ei-04.txt URL: http://www.rfc-editor.org/rfc/rfc4911.txt This document defines encoding instructions that may be used in an Abstract Syntax Notation One (ASN.1) specification to alter how ASN.1 values are encoded by the Robust XML Encoding Rules (RXER) and Canonical Robust XML Encoding Rules (CRXER), for example, to encode a component of an ASN.1 value as an Extensible Markup Language (XML) attribute rather than as a child element. Some of these encoding instructions also affect how an ASN.1 specification is translated into an Abstract Syntax Notation X (ASN.X) specification. Encoding instructions that allow an ASN.1 specification to reference definitions in other XML schema languages are also defined. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Sat Jul 14 13:26:15 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Sat, 14 Jul 2007 13:26:15 -0700 (PDT) Subject: [rfc-dist] RFC 4920 on Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE Message-ID: <20070714202615.BA9EBDA2BA@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4920 Title: Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE Author: A. Farrel, Ed., A. Satyanarayana, A. Iwata, N. Fujita, G. Ash Status: Standards Track Date: July 2007 Mailbox: adrian at olddog.co.uk, asatyana at cisco.com, a-iwata at ah.jp.nec.com, n-fujita at bk.jp.nec.com, gash5107 at yahoo.com Pages: 38 Characters: 88679 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-crankback-06.txt URL: http://www.rfc-editor.org/rfc/rfc4920.txt In a distributed, constraint-based routing environment, the information used to compute a path may be out of date. This means that Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered (TE) Label Switched Path (LSP) setup requests may be blocked by links or nodes without sufficient resources. Crankback is a scheme whereby setup failure information is returned from the point of failure to allow new setup attempts to be made avoiding the blocked resources. Crankback can also be applied to LSP recovery to indicate the location of the failed link or node. This document specifies crankback signaling extensions for use in MPLS signaling using RSVP-TE as defined in "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, and GMPLS signaling as defined in "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description", RFC 3473. These extensions mean that the LSP setup request can be retried on an alternate path that detours around blocked links or nodes. This offers significant improvements in the successful setup and recovery ratios for LSPs, especially in situations where a large number of setup requests are triggered at the same time. [STANDARDS TRACK] This document is a product of the Common Control and Measurement Plane Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jul 18 17:11:51 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 18 Jul 2007 17:11:51 -0700 (PDT) Subject: [rfc-dist] RFC 4845 on Process for Publication of IAB RFCs Message-ID: <20070719001151.E357FDA5B0@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4845 Title: Process for Publication of IAB RFCs Author: L. Daigle, Ed., Internet Architecture Board Status: Informational Date: July 2007 Mailbox: leslie at thinkingcat.com, iab at iab.org Pages: 5 Characters: 9228 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-publication-00.txt URL: http://www.rfc-editor.org/rfc/rfc4845.txt >From time to time, the Internet Architecture Board (IAB) publishes documents as Requests for Comments (RFCs). This document defines the process by which those documents are produced, reviewed, and published in the RFC Series. 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 Wed Jul 18 17:11:38 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 18 Jul 2007 17:11:38 -0700 (PDT) Subject: [rfc-dist] RFC 4844 on The RFC Series and RFC Editor Message-ID: <20070719001138.A1A4FDA5AE@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4844 Title: The RFC Series and RFC Editor Author: L. Daigle, Ed., Internet Architecture Board Status: Informational Date: July 2007 Mailbox: leslie at thinkingcat.com, iab at iab.org Pages: 20 Characters: 38752 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-rfc-editor-04.txt URL: http://www.rfc-editor.org/rfc/rfc4844.txt This document describes the framework for an RFC Series and an RFC Editor function that incorporate the principles of organized community involvement and accountability that has become necessary as the Internet technical community has grown, thereby enabling the RFC Series to continue to fulfill its mandate. 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 Wed Jul 18 17:12:23 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 18 Jul 2007 17:12:23 -0700 (PDT) Subject: [rfc-dist] BCP 130, RFC 4940 on IANA Considerations for OSPF Message-ID: <20070719001223.8AD85DA5B4@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. BCP 130 RFC 4940 Title: IANA Considerations for OSPF Author: K. Kompella, B. Fenner Status: Best Current Practice Date: July 2007 Mailbox: kireeti at juniper.net, fenner at research.att.com Pages: 15 Characters: 27595 Updates: See-Also: BCP0130 I-D Tag: draft-ietf-ospf-iana-03.txt URL: http://www.rfc-editor.org/rfc/rfc4940.txt This memo creates a number of OSPF registries and provides guidance to IANA for assignment of code points within these registries. 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 Open Shortest Path First IGP 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 Wed Jul 18 17:12:02 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 18 Jul 2007 17:12:02 -0700 (PDT) Subject: [rfc-dist] RFC 4846 on Independent Submissions to the RFC Editor Message-ID: <20070719001202.A8032DA5B2@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4846 Title: Independent Submissions to the RFC Editor Author: J. Klensin, Ed., D. Thaler, Ed. Status: Informational Date: July 2007 Mailbox: john-ietf at jck.com, dthaler at microsoft.com Pages: 16 Characters: 36562 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-rfc-independent-00.txt URL: http://www.rfc-editor.org/rfc/rfc4846.txt There is a long-standing tradition in the Internet community, predating the Internet Engineering Task Force (IETF) by many years, of use of the RFC Series to publish materials that are not rooted in the IETF standards process and its review and approval mechanisms. These documents, known as "Independent Submissions", serve a number of important functions for the Internet community, both inside and outside of the community of active IETF participants. This document discusses the Independent Submission model and some reasons why it is important. It then describes editorial and processing norms that can be used for Independent Submissions as the community goes forward into new relationships between the IETF community and its primary technical publisher. 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 Wed Jul 18 17:12:35 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 18 Jul 2007 17:12:35 -0700 (PDT) Subject: [rfc-dist] RFC 4885 on Network Mobility Support Terminology Message-ID: <20070719001235.3670BDA5B6@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4885 Title: Network Mobility Support Terminology Author: T. Ernst, H-Y. Lach Status: Informational Date: July 2007 Mailbox: thierry.ernst at inria.fr, hong-yon.lach at motorola.com Pages: 19 Characters: 37967 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nemo-terminology-06.txt URL: http://www.rfc-editor.org/rfc/rfc4885.txt This document defines a terminology for discussing network mobility (NEMO) issues and solution requirements. This memo provides information for the Internet community. This document is a product of the Network Mobility 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 Jul 18 17:12:45 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 18 Jul 2007 17:12:45 -0700 (PDT) Subject: [rfc-dist] RFC 4886 on Network Mobility Support Goals and Requirements Message-ID: <20070719001245.AF5DBDA5B8@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4886 Title: Network Mobility Support Goals and Requirements Author: T. Ernst Status: Informational Date: July 2007 Mailbox: thierry.ernst at inria.fr Pages: 13 Characters: 29083 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nemo-requirements-06.txt URL: http://www.rfc-editor.org/rfc/rfc4886.txt Network mobility arises when a router connecting a network to the Internet dynamically changes its point of attachment to the Internet thereby causing the reachability of the said network to be changed in relation to the fixed Internet topology. Such a type of network is referred to as a mobile network. With appropriate mechanisms, sessions established between nodes in the mobile network and the global Internet can be maintained after the mobile router changes its point of attachment. This document outlines the goals expected from network mobility support and defines the requirements that must be met by the NEMO Basic Support solution. This memo provides information for the Internet community. This document is a product of the Network Mobility 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 Jul 18 17:12:59 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 18 Jul 2007 17:12:59 -0700 (PDT) Subject: [rfc-dist] RFC 4887 on Network Mobility Home Network Models Message-ID: <20070719001259.87F60DA5BA@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4887 Title: Network Mobility Home Network Models Author: P. Thubert, R. Wakikawa, V. Devarapalli Status: Informational Date: July 2007 Mailbox: pthubert at cisco.com, ryuji at sfc.wide.ad.jp, vijay.devarapalli at azairenet.com Pages: 19 Characters: 40372 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nemo-home-network-models-06.txt URL: http://www.rfc-editor.org/rfc/rfc4887.txt This paper documents some of the usage patterns and the associated issues when deploying a Home Network for Network Mobility (NEMO)- enabled Mobile Routers, conforming to the NEMO Basic Support. The aim here is specifically to provide some examples of organization of the Home Network, as they were discussed in NEMO-related mailing lists. This memo provides information for the Internet community. This document is a product of the Network Mobility 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 Jul 18 17:13:14 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 18 Jul 2007 17:13:14 -0700 (PDT) Subject: [rfc-dist] RFC 4888 on Network Mobility Route Optimization Problem Statement Message-ID: <20070719001314.026F8DA5BC@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4888 Title: Network Mobility Route Optimization Problem Statement Author: C. NgUC Davis, P. Thubert, M. Watari, F. Zhao Status: Informational Date: July 2007 Mailbox: chanwah.ng at sg.panasonic.com, pthubert at cisco.com, watari at kddilabs.jp, fanzhao at ucdavis.edu Pages: 26 Characters: 56756 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nemo-ro-problem-statement-03.txt URL: http://www.rfc-editor.org/rfc/rfc4888.txt With current Network Mobility (NEMO) Basic Support, all communications to and from Mobile Network Nodes must go through the bi-directional tunnel established between the Mobile Router and Home Agent when the mobile network is away. This sub-optimal routing results in various inefficiencies associated with packet delivery, such as increased delay and bottleneck links leading to traffic congestion, which can ultimately disrupt all communications to and from the Mobile Network Nodes. Additionally, with nesting of Mobile Networks, these inefficiencies get compounded, and stalemate conditions may occur in specific dispositions. This document investigates such problems and provides the motivation behind Route Optimization (RO) for NEMO. This memo provides information for the Internet community. This document is a product of the Network Mobility 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 Jul 18 17:13:25 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 18 Jul 2007 17:13:25 -0700 (PDT) Subject: [rfc-dist] RFC 4889 on Network Mobility Route Optimization Solution Space Analysis Message-ID: <20070719001325.19AA2DA5BE@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4889 Title: Network Mobility Route Optimization Solution Space Analysis Author: C. Ng, F. Zhao, M. Watari, P. Thubert Status: Informational Date: July 2007 Mailbox: chanwah.ng at sg.panasonic.com, fanzhao at ucdavis.edu, watari at kddilabs.jp, pthubert at cisco.com Pages: 38 Characters: 95880 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nemo-ro-space-analysis-03.txt URL: http://www.rfc-editor.org/rfc/rfc4889.txt With current Network Mobility (NEMO) Basic Support, all communications to and from Mobile Network Nodes must go through the Mobile Router and Home Agent (MRHA) tunnel when the mobile network is away. This results in increased length of packet route and increased packet delay in most cases. To overcome these limitations, one might have to turn to Route Optimization (RO) for NEMO. This memo documents various types of Route Optimization in NEMO and explores the benefits and tradeoffs in different aspects of NEMO Route Optimization. This memo provides information for the Internet community. This document is a product of the Network Mobility 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 Jul 18 17:13:40 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 18 Jul 2007 17:13:40 -0700 (PDT) Subject: [rfc-dist] RFC 4947 on Address Resolution Mechanisms for IP Datagrams over MPEG-2 Networks Message-ID: <20070719001340.CF6FFDA5C0@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4947 Title: Address Resolution Mechanisms for IP Datagrams over MPEG-2 Networks Author: G. Fairhurst, M. Montpetit Status: Informational Date: July 2007 Mailbox: gorry at erg.abdn.ac.uk, mmontpetit at motorola.com Pages: 41 Characters: 102717 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipdvb-ar-06.txt URL: http://www.rfc-editor.org/rfc/rfc4947.txt This document describes the process of binding/associating IPv4/IPv6 addresses with MPEG-2 Transport Streams (TS). This procedure is known as Address Resolution (AR) or Neighbor Discovery (ND). Such address resolution complements the higher-layer resource discovery tools that are used to advertise IP sessions. In MPEG-2 Networks, an IP address must be associated with a Packet ID (PID) value and a specific Transmission Multiplex. This document reviews current methods appropriate to a range of technologies (such as DVB (Digital Video Broadcasting), ATSC (Advanced Television Systems Committee), DOCSIS (Data-Over-Cable Service Interface Specifications), and variants). It also describes the interaction with well-known protocols for address management including DHCP, ARP, and the ND protocol. This memo provides information for the Internet community. This document is a product of the IP over DVB 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 Jul 23 11:45:30 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 23 Jul 2007 11:45:30 -0700 (PDT) Subject: [rfc-dist] RFC 4982 on Support for Multiple Hash Algorithms in Cryptographically Generated Addresses (CGAs) Message-ID: <20070723184530.764D1DA97C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4982 Title: Support for Multiple Hash Algorithms in Cryptographically Generated Addresses (CGAs) Author: M. Bagnulo, J. Arkko Status: Standards Track Date: July 2007 Mailbox: marcelo at it.uc3m.es, jari.arkko at ericsson.com Pages: 9 Characters: 20961 Updates: RFC3972 See-Also: I-D Tag: draft-bagnulo-multiple-hash-cga-03.txt URL: http://www.rfc-editor.org/rfc/rfc4982.txt This document analyzes the implications of recent attacks on commonly used hash functions on Cryptographically Generated Addresses (CGAs) and updates the CGA specification to support multiple hash algorithms. [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 Jul 23 11:47:24 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 23 Jul 2007 11:47:24 -0700 (PDT) Subject: [rfc-dist] RFC 4958 on A Framework for Supporting Emergency Telecommunications Services (ETS) within a Single Administrative Domain Message-ID: <20070723184724.B5E7CDA980@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4958 Title: A Framework for Supporting Emergency Telecommunications Services (ETS) within a Single Administrative Domain Author: K. Carlberg Status: Informational Date: July 2007 Mailbox: carlberg at g11.org.uk Pages: 28 Characters: 44008 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ieprep-domain-frame-08.txt URL: http://www.rfc-editor.org/rfc/rfc4958.txt This document presents a framework discussing the role of various protocols and mechanisms that could be considered candidates for supporting Emergency Telecommunication Services (ETS) within a single administrative domain. Comments about their potential usage as well as their current deployment are provided to the reader. Specific solutions are not presented. This memo provides information for the Internet community. This document is a product of the Internet Emergency Preparedness 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 Jul 23 11:47:03 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 23 Jul 2007 11:47:03 -0700 (PDT) Subject: [rfc-dist] RFC 4954 on SMTP Service Extension for Authentication Message-ID: <20070723184703.4F36ADA97E@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4954 Title: SMTP Service Extension for Authentication Author: R. Siemborski, Ed., A. Melnikov, Ed. Status: Standards Track Date: July 2007 Mailbox: robsiemb at google.com, Alexey.Melnikov at isode.com Pages: 20 Characters: 43493 Obsoletes: RFC2554 Updates: RFC3463 I-D Tag: draft-siemborski-rfc2554bis-09.txt URL: http://www.rfc-editor.org/rfc/rfc4954.txt This document defines a Simple Mail Transport Protocol (SMTP) extension whereby an SMTP client may indicate an authentication mechanism to the server, perform an authentication protocol exchange, and optionally negotiate a security layer for subsequent protocol interactions during this session. This extension includes a profile of the Simple Authentication and Security Layer (SASL) for SMTP. This document obsoletes RFC 2554. [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 Jul 23 11:47:53 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 23 Jul 2007 11:47:53 -0700 (PDT) Subject: [rfc-dist] RFC 4946 on Atom License Extension Message-ID: <20070723184753.5D6D4DA982@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4946 Title: Atom License Extension Author: J. Snell Status: Experimental Date: July 2007 Mailbox: jasnell at gmail.com Pages: 8 Characters: 14602 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-snell-atompub-feed-license-11.txt URL: http://www.rfc-editor.org/rfc/rfc4946.txt This memo defines an extension to the Atom Syndication Format for describing licenses associated with Atom feeds and entries. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Mon Jul 23 11:48:26 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 23 Jul 2007 11:48:26 -0700 (PDT) Subject: [rfc-dist] BCP 132, RFC 4962 on Guidance for Authentication, Authorization, and Accounting (AAA) Key Management, Message-ID: <20070723184826.B7A8EDA984@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. BCP 132 RFC 4962 Title: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management, Author: R. Housley, B. Aboba Status: Best Current Practice Date: July 2007 Mailbox: housley at vigilsec.com, bernarda at microsoft.com Pages: 23 Characters: 54927 See-Also: BCP0132 I-D Tag: draft-housley-aaa-key-mgmt-09.txt URL: http://www.rfc-editor.org/rfc/rfc4962.txt This document provides guidance to designers of Authentication, Authorization, and Accounting (AAA) key management protocols. The guidance is also useful to designers of systems and solutions that include AAA key management protocols. Given the complexity and difficulty in designing secure, long-lasting key management algorithms and protocols by experts in the field, it is almost certainly inappropriate for IETF working groups without deep expertise in the area to be designing their own key management algorithms and protocols based on Authentication, Authorization, and Accounting (AAA) protocols. The guidelines in this document apply to documents requesting publication as IETF RFCs. Further, these guidelines will be useful to other standards development organizations (SDOs) that specify AAA key management. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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 Mon Jul 23 11:48:51 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 23 Jul 2007 11:48:51 -0700 (PDT) Subject: [rfc-dist] RFC 4939 on Definitions of Managed Objects for iSNS (Internet Storage Name Service) Message-ID: <20070723184851.9DACDDA986@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4939 Title: Definitions of Managed Objects for iSNS (Internet Storage Name Service) Author: K. Gibbons, G. Ramkumar, S. Kipp Status: Standards Track Date: July 2007 Mailbox: kgibbons at yahoo.com, gramkumar at stanfordalumni.org, skipp at brocade.com Pages: 80 Characters: 165381 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ips-isns-mib-11.txt URL: http://www.rfc-editor.org/rfc/rfc4939.txt The iSNS (Internet Storage Name Service) protocol provides storage name service functionality on an IP network that is being used for iSCSI (Internet Small Computer System Interface) or iFCP (Internet Fibre Channel Protocol) storage. This document provides a mechanism to monitor multiple iSNS Servers, including information about registered objects in an iSNS Server. [STANDARDS TRACK] This document is a product of the IP 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 Wed Jul 25 09:01:07 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 25 Jul 2007 09:01:07 -0700 (PDT) Subject: [rfc-dist] RFC 4883 on Benchmarking Terminology for Resource Reservation Capable Routers Message-ID: <20070725160107.D1154DAA5B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4883 Title: Benchmarking Terminology for Resource Reservation Capable Routers Author: G. Feher, K. Nemeth, A. Korn, I. Cselenyi Status: Informational Date: July 2007 Mailbox: Gabor.Feher at tmit.bme.hu, Krisztian.Nemeth at tmit.bme.hu, Andras.Korn at tmit.bme.hu, Istvan.Cselenyi at teliasonera.com Pages: 24 Characters: 54205 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-bmwg-benchres-term-08.txt URL: http://www.rfc-editor.org/rfc/rfc4883.txt The primary purpose of this document is to define terminology specific to the benchmarking of resource reservation signaling of Integrated Services (IntServ) IP routers. These terms can be used in additional documents that define benchmarking methodologies for routers that support resource reservation or reporting formats for the benchmarking measurements. This memo provides information for the Internet community. This document is a product of the Benchmarking Methodology 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 Jul 25 09:01:28 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 25 Jul 2007 09:01:28 -0700 (PDT) Subject: [rfc-dist] RFC 5034 on The Post Office Protocol (POP3) Simple Authentication and Security Layer (SASL) Authentication Mechanism Message-ID: <20070725160128.4B689DAA5D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5034 Title: The Post Office Protocol (POP3) Simple Authentication and Security Layer (SASL) Authentication Mechanism Author: R. Siemborski, A. Menon-Sen Status: Standards Track Date: July 2007 Mailbox: robsiemb at google.com, ams at oryx.com Pages: 12 Characters: 24170 I-D Tag: draft-siemborski-rfc1734bis-11.txt URL: http://www.rfc-editor.org/rfc/rfc5034.txt This document defines a profile of the Simple Authentication and Security Layer (SASL) for the Post Office Protocol (POP3). This extension allows a POP3 client to indicate an authentication mechanism to the server, perform an authentication protocol exchange, and optionally negotiate a security layer for subsequent protocol interactions during this session. This document seeks to consolidate the information related to POP3 AUTH into a single document. To this end, this document obsoletes and replaces RFC 1734, and updates the information contained in Section 6.3 of RFC 2449. [STANDARDS TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jul 25 09:01:45 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 25 Jul 2007 09:01:45 -0700 (PDT) Subject: [rfc-dist] RFC 4924 on Reflections on Internet Transparency Message-ID: <20070725160145.9414ADAA5F@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4924 Title: Reflections on Internet Transparency Author: B. Aboba, Ed., E. Davies Status: Informational Date: July 2007 Mailbox: bernarda at microsoft.com, elwynd at dial.pipex.com Pages: 15 Characters: 35040 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-net-transparent-05.txt URL: http://www.rfc-editor.org/rfc/rfc4924.txt This document provides a review of previous IAB statements on Internet transparency, as well a discussion of new transparency issues. Far from having lessened in relevance, technical implications of intentionally or inadvertently impeding network transparency play a critical role in the Internet's ability to support innovation and global communication. This document provides some specific illustrations of those potential impacts. 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 Wed Jul 25 09:01:59 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 25 Jul 2007 09:01:59 -0700 (PDT) Subject: [rfc-dist] RFC 4966 on Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status Message-ID: <20070725160159.56399DAA61@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4966 Title: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status Author: C. Aoun, E. Davies Status: Informational Date: July 2007 Mailbox: ietf at energizeurnet.com, elwynd at dial.pipex.com Pages: 25 Characters: 60284 Obsoletes: RFC2766 See-Also: I-D Tag: draft-ietf-v6ops-natpt-to-historic-00.txt URL: http://www.rfc-editor.org/rfc/rfc4966.txt This document discusses issues with the specific form of IPv6-IPv4 protocol translation mechanism implemented by the Network Address Translator - Protocol Translator (NAT-PT) defined in RFC 2766. These issues are sufficiently serious that recommending RFC 2766 as a general purpose transition mechanism is no longer desirable, and this document recommends that the IETF should reclassify RFC 2766 from Proposed Standard to Historic status. This memo provides information for the Internet community. This document is a product of the IPv6 Operations Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Wed Jul 25 09:02:14 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 25 Jul 2007 09:02:14 -0700 (PDT) Subject: [rfc-dist] RFC 4952 on Overview and Framework for Internationalized Email Message-ID: <20070725160214.7B831DAA63@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4952 Title: Overview and Framework for Internationalized Email Author: J. Klensin, Y. Ko Status: Informational Date: July 2007 Mailbox: john-ietf at jck.com, yw at mrko.pe.kr Pages: 20 Characters: 48409 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-eai-framework-05.txt URL: http://www.rfc-editor.org/rfc/rfc4952.txt Full use of electronic mail throughout the world requires that people be able to use their own names, written correctly in their own languages and scripts, as mailbox names in email addresses. This document introduces a series of specifications that define mechanisms and protocol extensions needed to fully support internationalized email addresses. These changes include an SMTP extension and extension of email header syntax to accommodate UTF-8 data. The document set also includes discussion of key assumptions and issues in deploying fully internationalized email. This memo provides information for the Internet community. This document is a product of the Email Address Internationalization 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 Jul 27 13:30:50 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 27 Jul 2007 13:30:50 -0700 (PDT) Subject: [rfc-dist] RFC 4955 on DNS Security (DNSSEC) Experiments Message-ID: <20070727203050.2A836DAC14@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4955 Title: DNS Security (DNSSEC) Experiments Author: D. Blacka Status: Standards Track Date: July 2007 Mailbox: davidb at verisign.com Pages: 7 Characters: 15417 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dnsext-dnssec-experiments-04.txt URL: http://www.rfc-editor.org/rfc/rfc4955.txt This document describes a methodology for deploying alternate, non-backwards-compatible, DNS Security (DNSSEC) methodologies in an experimental fashion without disrupting the deployment of standard DNSSEC. [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 Fri Jul 27 13:31:04 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 27 Jul 2007 13:31:04 -0700 (PDT) Subject: [rfc-dist] RFC 4956 on DNS Security (DNSSEC) Opt-In Message-ID: <20070727203104.A3552DAC16@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4956 Title: DNS Security (DNSSEC) Opt-In Author: R. Arends, M. Kosters, D. Blacka Status: Experimental Date: July 2007 Mailbox: roy at nominet.org.uk, markk at verisign.com, davidb at verisign.com Pages: 17 Characters: 32033 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dnsext-dnssec-opt-in-09.txt URL: http://www.rfc-editor.org/rfc/rfc4956.txt In the DNS security (DNSSEC) extensions, delegations to unsigned subzones are cryptographically secured. Maintaining this cryptography is not always practical or necessary. This document describes an experimental "Opt-In" model that allows administrators to omit this cryptography and manage the cost of adopting DNSSEC with large zones. This memo defines an Experimental Protocol for the Internet community. This document is a product of the DNS Extensions Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Fri Jul 27 13:30:21 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 27 Jul 2007 13:30:21 -0700 (PDT) Subject: [rfc-dist] RFC 4925 on Softwire Problem Statement Message-ID: <20070727203021.61DDDDAC12@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4925 Title: Softwire Problem Statement Author: X. Li, Ed., S. Dawkins, Ed., D. Ward, Ed., A. Durand, Ed. Status: Informational Date: July 2007 Mailbox: xing at cernet.edu.cn, spencer at mcsr-labs.org, dward at cisco.com, alain_durand at cable.comcast.com Pages: 23 Characters: 49298 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-softwire-problem-statement-03.txt URL: http://www.rfc-editor.org/rfc/rfc4925.txt This document captures the problem statement for the Softwires Working Group, which is developing standards for the discovery, control, and encapsulation methods for connecting IPv4 networks across IPv6-only networks as well as IPv6 networks across IPv4-only networks. The standards will encourage multiple, inter-operable vendor implementations by identifying, and extending where necessary, existing standard protocols to resolve a selected set of "IPv4/IPv6" and "IPv6/IPv4" transition problems. This document describes the specific problems ("Hubs and Spokes" and "Mesh") that will be solved by the standards developed by the Softwires Working Group. Some requirements (and non-requirements) are also identified to better describe the specific problem scope. This memo provides information for the Internet community. This document is a product of the Softwires 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 Jul 27 13:31:25 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 27 Jul 2007 13:31:25 -0700 (PDT) Subject: [rfc-dist] RFC 4967 on Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier Message-ID: <20070727203125.16944DAC18@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4967 Title: Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier Author: B. Rosen Status: Standards Track Date: July 2007 Mailbox: br at brianrosen.net Pages: 6 Characters: 12659 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-rosen-iptel-dialstring-05.txt URL: http://www.rfc-editor.org/rfc/rfc4967.txt RFC 3966 explicitly states that 'tel' URIs may not represent a dial string. That leaves no way specify a dial string in a standardized way. Great confusion exists with the SIP URI parameter "user=phone", and specifically, if it can represent a dial string. This memo creates a new value for the user parameter "dialstring", so that one may specify "user=dialstring" to encode a dial string as a 'sip:' or 'sips:' URI. [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 Jul 27 14:33:30 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 27 Jul 2007 14:33:30 -0700 (PDT) Subject: [rfc-dist] RFC 4963 on IPv4 Reassembly Errors at High Data Rates Message-ID: <20070727213330.DE22BDAC1B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4963 Title: IPv4 Reassembly Errors at High Data Rates Author: J. Heffner, M. Mathis, B. Chandler Status: Informational Date: July 2007 Mailbox: jheffner at psc.edu, mathis at psc.edu, bchandle at gmail.com Pages: 10 Characters: 22399 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-heffner-frag-harmful-05.txt URL: http://www.rfc-editor.org/rfc/rfc4963.txt IPv4 fragmentation is not sufficiently robust for use under some conditions in today's Internet. At high data rates, the 16-bit IP identification field is not large enough to prevent frequent incorrectly assembled IP fragments, and the TCP and UDP checksums are insufficient to prevent the resulting corrupted datagrams from being delivered to higher protocol layers. This note describes some easily reproduced experiments demonstrating the problem, and discusses some of the operational implications of these observations. 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 Jul 30 18:03:46 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 30 Jul 2007 18:03:46 -0700 (PDT) Subject: [rfc-dist] RFC 4995 on The RObust Header Compression (ROHC) Framework Message-ID: <20070731010346.8E614DAFD7@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4995 Title: The RObust Header Compression (ROHC) Framework Author: L-E. Jonsson, G. Pelletier, K. Sandlund Status: Standards Track Date: July 2007 Mailbox: lars-erik at lejonsson.com, ghyslain.pelletier at ericsson.com, kristofer.sandlund at ericsson.com Pages: 40 Characters: 87198 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rohc-rfc3095bis-framework-04.txt URL: http://www.rfc-editor.org/rfc/rfc4995.txt The Robust Header Compression (ROHC) protocol provides an efficient, flexible, and future-proof header compression concept. It is designed to operate efficiently and robustly over various link technologies with different characteristics. The ROHC framework, along with a set of compression profiles, was initially defined in RFC 3095. To improve and simplify the ROHC specifications, this document explicitly defines the ROHC framework and the profile for uncompressed separately. More specifically, the definition of the framework does not modify or update the definition of the framework specified by RFC 3095. [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 Mon Jul 30 18:03:31 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 30 Jul 2007 18:03:31 -0700 (PDT) Subject: [rfc-dist] RFC 4953 on Defending TCP Against Spoofing Attacks Message-ID: <20070731010331.964DBDAFD5@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4953 Title: Defending TCP Against Spoofing Attacks Author: J. Touch Status: Informational Date: July 2007 Mailbox: touch at isi.edu Pages: 28 Characters: 72756 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tcpm-tcp-antispoof-06.txt URL: http://www.rfc-editor.org/rfc/rfc4953.txt Recent analysis of potential attacks on core Internet infrastructure indicates an increased vulnerability of TCP connections to spurious resets (RSTs), sent with forged IP source addresses (spoofing). TCP has always been susceptible to such RST spoofing attacks, which were indirectly protected by checking that the RST sequence number was inside the current receive window, as well as via the obfuscation of TCP endpoint and port numbers. For pairs of well-known endpoints often over predictable port pairs, such as BGP or between web servers and well-known large-scale caches, increases in the path bandwidth-delay product of a connection have sufficiently increased the receive window space that off-path third parties can brute-force generate a viable RST sequence number. The susceptibility to attack increases with the square of the bandwidth, and thus presents a significant vulnerability for recent high-speed networks. This document addresses this vulnerability, discussing proposed solutions at the transport level and their inherent challenges, as well as existing network level solutions and the feasibility of their deployment. This document focuses on vulnerabilities due to spoofed TCP segments, and includes a discussion of related ICMP spoofing attacks on TCP connections. 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 Mon Jul 30 18:04:06 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 30 Jul 2007 18:04:06 -0700 (PDT) Subject: [rfc-dist] RFC 4997 on Formal Notation for RObust Header Compression (ROHC-FN) Message-ID: <20070731010406.36F91DAFDB@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4997 Title: Formal Notation for RObust Header Compression (ROHC-FN) Author: R. Finking, G. Pelletier Status: Standards Track Date: July 2007 Mailbox: robert.finking at roke.co.uk, ghyslain.pelletier at ericsson.com Pages: 62 Characters: 131231 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rohc-formal-notation-13.txt URL: http://www.rfc-editor.org/rfc/rfc4997.txt This document defines Robust Header Compression - Formal Notation (ROHC-FN), a formal notation to specify field encodings for compressed formats when defining new profiles within the ROHC framework. ROHC-FN offers a library of encoding methods that are often used in ROHC profiles and can thereby help to simplify future profile development work. [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 Mon Jul 30 18:03:56 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Mon, 30 Jul 2007 18:03:56 -0700 (PDT) Subject: [rfc-dist] RFC 4996 on RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP) Message-ID: <20070731010356.30D02DAFD9@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4996 Title: RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP) Author: G. Pelletier, K. Sandlund, L-E. Jonsson, M. West Status: Standards Track Date: July 2007 Mailbox: ghyslain.pelletier at ericsson.com, kristofer.sandlund at ericsson.com, lars-erik at lejonsson.com, mark.a.west at roke.co.uk Pages: 94 Characters: 183113 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rohc-tcp-16.txt URL: http://www.rfc-editor.org/rfc/rfc4996.txt This document specifies a ROHC (Robust Header Compression) profile for compression of TCP/IP packets. The profile, called ROHC-TCP, provides efficient and robust compression of TCP headers, including frequently used TCP options such as SACK (Selective Acknowledgments) and Timestamps. ROHC-TCP works well when used over links with significant error rates and long round-trip times. For many bandwidth-limited links where header compression is essential, such characteristics are common. [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 Tue Jul 31 18:07:44 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 31 Jul 2007 18:07:44 -0700 (PDT) Subject: [rfc-dist] BCP 131 RFC 4961 on Symmetric RTP / RTP Control Protocol (RTCP) Message-ID: <20070801010744.98A8ADB065@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. BCP 131 RFC 4961 Title: Symmetric RTP / RTP Control Protocol (RTCP) Author: D. Wing Status: Best Current Practice Date: July 2007 Mailbox: dwing at cisco.com Pages: 6 Characters: 12539 Updates: See-Also: BCP0131 I-D Tag: draft-wing-behave-symmetric-rtprtcp-03.txt URL: http://www.rfc-editor.org/rfc/rfc4961.txt This document recommends using one UDP port pair for both communication directions of bidirectional RTP and RTP Control Protocol (RTCP) sessions, commonly called "symmetric RTP" and "symmetric RTCP". This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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 Tue Jul 31 18:08:22 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 31 Jul 2007 18:08:22 -0700 (PDT) Subject: [rfc-dist] RFC 4971 on Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information Message-ID: <20070801010822.CCB67DB069@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4971 Title: Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information Author: JP. Vasseur, Ed., N. Shen, Ed., R. Aggarwal, Ed. Status: Standards Track Date: July 2007 Mailbox: jpv at cisco.com, naiming at cisco.com, rahul at juniper.net Pages: 9 Characters: 18541 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-caps-07.txt URL: http://www.rfc-editor.org/rfc/rfc4971.txt This document defines a new optional Intermediate System to Intermediate System (IS-IS) TLV named CAPABILITY, formed of multiple sub-TLVs, which allows a router to announce its capabilities within an IS-IS level or the entire routing domain. [STANDARDS TRACK] This document is a product of the IS-IS for IP Internets 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 Jul 31 18:08:12 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 31 Jul 2007 18:08:12 -0700 (PDT) Subject: [rfc-dist] RFC 4970 on Extensions to OSPF for Advertising Optional Router Capabilities Message-ID: <20070801010812.94EF6DB067@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4970 Title: Extensions to OSPF for Advertising Optional Router Capabilities Author: A. Lindem, Ed., N. Shen, JP. Vasseur, R. Aggarwal, S. Shaffer Status: Standards Track Date: July 2007 Mailbox: acee at redback.com, naiming at cisco.com, jpv at cisco.com, rahul at juniper.net, sshaffer at bridgeport-networks.com Pages: 13 Characters: 26416 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ospf-cap-11.txt URL: http://www.rfc-editor.org/rfc/rfc4970.txt It is useful for routers in an OSPFv2 or OSPFv3 routing domain to know the capabilities of their neighbors and other routers in the routing domain. This document proposes extensions to OSPFv2 and OSPFv3 for advertising optional router capabilities. A new Router Information (RI) Link State Advertisement (LSA) is proposed for this purpose. In OSPFv2, the RI LSA will be implemented with a new opaque LSA type ID. In OSPFv3, the RI LSA will be implemented with a new LSA type function code. In both protocols, the RI LSA can be advertised at any of the defined flooding scopes (link, area, or autonomous system (AS)). [STANDARDS TRACK] This document is a product of the Open Shortest Path First IGP 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 Jul 31 18:08:40 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 31 Jul 2007 18:08:40 -0700 (PDT) Subject: [rfc-dist] RFC 4973 on OSPF-xTE: Experimental Extension to OSPF for Traffic Engineering Message-ID: <20070801010840.451C1DB06D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4973 Title: OSPF-xTE: Experimental Extension to OSPF for Traffic Engineering Author: P. Srisuresh, P. Joseph Status: Experimental Date: July 2007 Mailbox: srisuresh at yahoo.com, paul_95014 at yahoo.com Pages: 50 Characters: 115361 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-srisuresh-ospf-te-07.txt URL: http://www.rfc-editor.org/rfc/rfc4973.txt This document defines OSPF-xTE, an experimental traffic engineering (TE) extension to the link-state routing protocol OSPF. OSPF-xTE defines new TE Link State Advertisements (LSAs) to disseminate TE metrics within an autonomous System (AS), which may consist of multiple areas. When an AS consists of TE and non-TE nodes, OSPF-xTE ensures that non-TE nodes in the AS are unaffected by the TE LSAs. OSPF-xTE generates a stand-alone TE Link State Database (TE-LSDB), distinct from the native OSPF LSDB, for computation of TE circuit paths. OSPF-xTE is versatile and extendible to non-packet networks such as Synchronous Optical Network (SONET) / Time Division Multiplexing (TDM) and optical networks. This memo defines an Experimental Protocol for the Internet community. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From rfc-editor at rfc-editor.org Tue Jul 31 18:08:33 2007 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 31 Jul 2007 18:08:33 -0700 (PDT) Subject: [rfc-dist] RFC 4972 on Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh Membership Message-ID: <20070801010833.20651DB06B@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 4972 Title: Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh Membership Author: JP. Vasseur, Ed., JL. Leroux, Ed., S. Yasukawa, S. Previdi, P. Psenak, P. Mabbey Status: Standards Track Date: July 2007 Mailbox: jpv at cisco.com, jeanlouis.leroux at orange-ftgroup.com, s.yasukawa at hco.ntt.co.jp, sprevidi at cisco.com, ppsenak at cisco.com, Paul_Mabey at cable.comcast.com Pages: 15 Characters: 32044 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-automesh-04.txt URL: http://www.rfc-editor.org/rfc/rfc4972.txt The setup of a full mesh of Multi-Protocol Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths (LSP) among a set of Label Switch Routers (LSR) is a common deployment scenario of MPLS Traffic Engineering either for bandwidth optimization, bandwidth guarantees or fast rerouting with MPLS Fast Reroute. Such deployment may require the configuration of a potentially large number of TE LSPs (on the order of the square of the number of LSRs). This document specifies Interior Gateway Protocol (IGP) routing extensions for Intermediate System-to-Intermediate System (IS-IS) and Open Shortest Path First (OSPF) so as to provide an automatic discovery of the set of LSRs members of a mesh in order to automate the creation of such mesh of TE LSPs. [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-ed at ISI.EDU Sat Jul 28 20:55:16 2007 From: rfc-ed at ISI.EDU (rfc-ed@ISI.EDU) Date: Tue, 28 Jul 2007 24:55:16 -0300 Subject: [rfc-dist] (no subject) Message-ID: <443861424340568242.74628846824736293@ISI.EDU> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.rfc-editor.org/pipermail/rfc-dist/attachments/20070731/97d73161/attachment.html