From rfc-editor at rfc-editor.org Thu Jul 3 14:17:27 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 3 Jul 2008 14:17:27 -0700 (PDT) Subject: [rfc-dist] RFC 5217 on Memorandum for Multi-Domain Public Key Infrastructure Interoperability Message-ID: <20080703211727.0227F13C02A@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5217 Title: Memorandum for Multi-Domain Public Key Infrastructure Interoperability Author: M. Shimaoka, Ed., N. Hastings, R. Nielsen Status: Informational Date: July 2008 Mailbox: m-shimaoka at secom.co.jp, nelson.hastings at nist.gov, nielsen_rebecca at bah.com Pages: 29 Characters: 64814 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-shimaoka-multidomain-pki-13.txt URL: http://www.rfc-editor.org/rfc/rfc5217.txt The objective of this document is to establish a terminology framework and to suggest the operational requirements of Public Key Infrastructure (PKI) domain for interoperability of multi-domain Public Key Infrastructure, where each PKI domain is operated under a distinct policy. This document describes the relationships between Certification Authorities (CAs), provides the definition and requirements for PKI domains, and discusses typical models of multi-domain PKI. 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu Jul 3 14:18:07 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 3 Jul 2008 14:18:07 -0700 (PDT) Subject: [rfc-dist] BCP 139, RFC 5249 on Templates for Internet-Drafts Containing MIB Modules Message-ID: <20080703211807.45C4513C02E@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. BCP 139 RFC 5249 Title: Templates for Internet-Drafts Containing MIB Modules Author: D. Harrington, Ed. Status: Best Current Practice Date: July 2008 Mailbox: dharrington at huawei.com Pages: 4 Characters: 7362 See Also: BCP0139 I-D Tag: draft-harrington-text-mib-doc-template-06.txt URL: http://www.rfc-editor.org/rfc/rfc5249.txt This memo references three annotated templates for IETF documents that contain the definition of MIB modules. It is intended to reduce the work of the editors of such documents, making these documents more uniform and easier to read and review, thus furthering the quality of such documents and expediting their publication. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. BCP: 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu Jul 3 14:17:44 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 3 Jul 2008 14:17:44 -0700 (PDT) Subject: [rfc-dist] RFC 5227 on IPv4 Address Conflict Detection Message-ID: <20080703211744.AA4C013C02C@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5227 Title: IPv4 Address Conflict Detection Author: S. Cheshire Status: Standards Track Date: July 2008 Mailbox: rfc at stuartcheshire.org Pages: 21 Characters: 53548 Updates: RFC0826 I-D Tag: draft-cheshire-ipv4-acd-06.txt URL: http://www.rfc-editor.org/rfc/rfc5227.txt When two hosts on the same link attempt to use the same IPv4 address at the same time (except in rare special cases where this has been arranged by prior coordination), problems ensue for one or both hosts. This document describes (i) a simple precaution that a host can take in advance to help prevent this misconfiguration from happening, and (ii) if this misconfiguration does occur, a simple mechanism by which a host can passively detect, after the fact, that it has happened, so that the host or administrator may respond to rectify the problem. [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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu Jul 3 14:18:23 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 3 Jul 2008 14:18:23 -0700 (PDT) Subject: [rfc-dist] RFC 5250 on The OSPF Opaque LSA Option Message-ID: <20080703211823.6A59113C030@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5250 Title: The OSPF Opaque LSA Option Author: L. Berger, I. Bryskin, A. Zinin, R. Coltun Status: Standards Track Date: July 2008 Mailbox: lberger at labn.net, ibryskin at advaoptical.com, alex.zinin at alcatel-lucent.com Pages: 17 Characters: 37657 Obsoletes: RFC2370 I-D Tag: draft-ietf-ospf-rfc2370bis-05.txt URL: http://www.rfc-editor.org/rfc/rfc5250.txt This document defines enhancements to the OSPF protocol to support a new class of link state advertisements (LSAs) called Opaque LSAs. Opaque LSAs provide a generalized mechanism to allow for the future extensibility of OSPF. Opaque LSAs consist of a standard LSA header followed by application-specific information. The information field may be used directly by OSPF or by other applications. Standard OSPF link-state database flooding mechanisms are used to distribute Opaque LSAs to all or some limited portion of the OSPF topology. This document replaces RFC 2370 and adds to it a mechanism to enable an OSPF router to validate Autonomous System (AS)-scope Opaque LSAs originated outside of the router's OSPF area. [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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu Jul 3 14:18:40 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 3 Jul 2008 14:18:40 -0700 (PDT) Subject: [rfc-dist] RFC 5251 on Layer 1 VPN Basic Mode Message-ID: <20080703211840.D024613C032@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5251 Title: Layer 1 VPN Basic Mode Author: D. Fedyk, Ed., Y. Rekhter, Ed., D. Papadimitriou, R. Rabbat, L. Berger Status: Standards Track Date: July 2008 Mailbox: dwfedyk at nortel.com, yakov at juniper.net, Dimitri.Papadimitriou at alcatel-lucent.be, rabbat at alum.mit.edu, lberger at labn.net Pages: 24 Characters: 57599 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l1vpn-basic-mode-05.txt URL: http://www.rfc-editor.org/rfc/rfc5251.txt This document describes the Basic Mode of Layer 1 VPNs (L1VPNs). L1VPN Basic Mode (L1VPN BM) is a port-based VPN. In L1VPN Basic Mode, the basic unit of service is a Label Switched Path (LSP) between a pair of customer ports within a given VPN port topology. This document defines the operational model using either provisioning or a VPN auto-discovery mechanism, and the signaling extensions for the L1VPN BM. [STANDARDS TRACK] This document is a product of the Layer 1 Virtual Private Networks 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu Jul 3 14:19:45 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 3 Jul 2008 14:19:45 -0700 (PDT) Subject: [rfc-dist] RFC 5252 on OSPF-Based Layer 1 VPN Auto-Discovery Message-ID: <20080703211945.2B84713C036@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5252 Title: OSPF-Based Layer 1 VPN Auto-Discovery Author: I. Bryskin, L. Berger Status: Standards Track Date: July 2008 Mailbox: ibryskin at advaoptical.com, lberger at labn.net Pages: 11 Characters: 23232 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l1vpn-ospf-auto-discovery-06.txt URL: http://www.rfc-editor.org/rfc/rfc5252.txt This document defines an Open Shortest Path First (OSPF) based Layer 1 Virtual Private Network (L1VPN) auto-discovery mechanism. This mechanism enables provider edge (PE) devices using OSPF to dynamically learn about the existence of each other, and attributes of configured customer edge (CE) links and their associations with L1VPNs. This document builds on the L1VPN framework and requirements and provides a L1VPN basic mode auto-discovery mechanism. [STANDARDS TRACK] This document is a product of the Layer 1 Virtual Private Networks 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu Jul 3 14:20:03 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 3 Jul 2008 14:20:03 -0700 (PDT) Subject: [rfc-dist] RFC 5253 on Applicability Statement for Layer 1 Virtual Private Network (L1VPN) Basic Mode Message-ID: <20080703212003.14ED013C038@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5253 Title: Applicability Statement for Layer 1 Virtual Private Network (L1VPN) Basic Mode Author: T. Takeda, Ed. Status: Informational Date: July 2008 Mailbox: takeda.tomonori at lab.ntt.co.jp Pages: 19 Characters: 42675 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l1vpn-applicability-basic-mode-05.txt URL: http://www.rfc-editor.org/rfc/rfc5253.txt This document provides an applicability statement on the use of Generalized Multiprotocol Label Switching (GMPLS) protocols and mechanisms to support Basic Mode Layer 1 Virtual Private Networks (L1VPNs). L1VPNs provide customer services and connectivity at Layer 1 over Layer 1 networks. The operation of L1VPNs is divided into the Basic Mode and the Enhanced Mode, where the Basic Mode of operation does not feature any exchange of routing information between the Layer 1 network and the customer domain. This document examines how GMPLS protocols can be used to satisfy the requirements of a Basic Mode L1VPN. This memo provides information for the Internet community. This document is a product of the Layer 1 Virtual Private Networks Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Wed Jul 9 16:37:12 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 9 Jul 2008 16:37:12 -0700 (PDT) Subject: [rfc-dist] RFC 5212 on Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN) Message-ID: <20080709233712.E5F6F141CF8@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5212 Title: Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN) Author: K. Shiomoto, D. Papadimitriou, JL. Le Roux, M. Vigoureux, D. Brungard Status: Informational Date: July 2008 Mailbox: shiomoto.kohei at lab.ntt.co.jp, dimitri.papadimitriou at alcatel-lucent.be, jeanlouis.leroux at orange-ftgroup.com, martin.vigoureux at alcatel-lucent.fr, dbrungard at att.com Pages: 28 Characters: 70286 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-gmpls-mln-reqs-11.txt URL: http://www.rfc-editor.org/rfc/rfc5212.txt Most of the initial efforts to utilize Generalized MPLS (GMPLS) have been related to environments hosting devices with a single switching capability. The complexity raised by the control of such data planes is similar to that seen in classical IP/MPLS networks. By extending MPLS to support multiple switching technologies, GMPLS provides a comprehensive framework for the control of a multi-layered network of either a single switching technology or multiple switching technologies. In GMPLS, a switching technology domain defines a region, and a network of multiple switching types is referred to in this document as a multi-region network (MRN). When referring in general to a layered network, which may consist of either single or multiple regions, this document uses the term multi-layer network (MLN). This document defines a framework for GMPLS based multi-region / multi-layer networks and lists a set of functional requirements. This memo provides information for the Internet community. This document is a product of the Common Control and Measurement Plane Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu Jul 10 16:03:13 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 10 Jul 2008 16:03:13 -0700 (PDT) Subject: [rfc-dist] RFC 5211 on An Internet Transition Plan Message-ID: <20080710230313.1740D1420F0@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5211 Title: An Internet Transition Plan Author: J. Curran Status: Informational Date: July 2008 Mailbox: jcurran at istaff.org Pages: 8 Characters: 17158 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-jcurran-v6transitionplan-03.txt URL: http://www.rfc-editor.org/rfc/rfc5211.txt This memo provides one possible plan for transitioning the Internet from a predominantly IPv4-based connectivity model to a predominantly IPv6-based connectivity model. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu Jul 10 16:03:10 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 10 Jul 2008 16:03:10 -0700 (PDT) Subject: [rfc-dist] RFC 5260 on Sieve Email Filtering: Date and Index Extensions Message-ID: <20080710230310.6521B1420EE@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5260 Title: Sieve Email Filtering: Date and Index Extensions Author: N. Freed Status: Standards Track Date: July 2008 Mailbox: ned.freed at mrochek.com Pages: 13 Characters: 25735 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-freed-sieve-date-index-12.txt URL: http://www.rfc-editor.org/rfc/rfc5260.txt This document describes the "date" and "index" extensions to the Sieve email filtering language. The "date" extension gives Sieve the ability to test date and time values in various ways. The "index" extension provides a means to limit header and address tests to specific instances of header fields when header fields are repeated. [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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Tue Jul 15 16:06:24 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 15 Jul 2008 16:06:24 -0700 (PDT) Subject: [rfc-dist] RFC 5221 on Requirements for Address Selection Mechanisms Message-ID: <20080715230624.48AD0143A09@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5221 Title: Requirements for Address Selection Mechanisms Author: A. Matsumoto, T. Fujisaki, R. Hiromi, K. Kanayama Status: Informational Date: July 2008 Mailbox: arifumi at nttv6.net, fujisaki at nttv6.net, hiromi at inetcore.com, kanayama_kenichi at intec-si.co.jp Pages: 7 Characters: 13732 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-v6ops-addr-select-req-07.txt URL: http://www.rfc-editor.org/rfc/rfc5221.txt There are some problematic cases when using the default address selection mechanism that RFC 3484 defines. This document describes additional requirements that operate with RFC 3484 to solve the problems. 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Tue Jul 15 16:06:21 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 15 Jul 2008 16:06:21 -0700 (PDT) Subject: [rfc-dist] RFC 5220 on Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules Message-ID: <20080715230621.B7927143A07@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5220 Title: Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules Author: A. Matsumoto, T. Fujisaki, R. Hiromi, K. Kanayama Status: Informational Date: July 2008 Mailbox: arifumi at nttv6.net, fujisaki at nttv6.net, hiromi at inetcore.com, kanayama_kenichi at intec-si.co.jp Pages: 17 Characters: 33661 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-v6ops-addr-select-ps-09.txt URL: http://www.rfc-editor.org/rfc/rfc5220.txt A single physical link can have multiple prefixes assigned to it. In that environment, end hosts might have multiple IP addresses and be required to use them selectively. RFC 3484 defines default source and destination address selection rules and is implemented in a variety of OSs. But, it has been too difficult to use operationally for several reasons. In some environments where multiple prefixes are assigned on a single physical link, the host using the default address selection rules will experience some trouble in communication. This document describes the possible problems that end hosts could encounter in an environment with multiple prefixes. 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu Jul 17 16:39:15 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 17 Jul 2008 16:39:15 -0700 (PDT) Subject: [rfc-dist] RFC 5259 on Internet Message Access Protocol - CONVERT Extension Message-ID: <20080717233915.C1E241440D6@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5259 Title: Internet Message Access Protocol - CONVERT Extension Author: A. Melnikov, Ed., P. Coates, Ed. Status: Standards Track Date: July 2008 Mailbox: Alexey.Melnikov at isode.com, peter.coates at Sun.COM Pages: 30 Characters: 63831 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lemonade-convert-20.txt URL: http://www.rfc-editor.org/rfc/rfc5259.txt CONVERT defines extensions to IMAP allowing clients to request adaptation and/or transcoding of attachments. Clients can specify the conversion details or allow servers to decide based on knowledge of client capabilities, on user or administrator preferences, or on server settings. [STANDARDS TRACK] This document is a product of the Enhancements to Internet email to support diverse service environments Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Fri Jul 18 16:39:57 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 18 Jul 2008 16:39:57 -0700 (PDT) Subject: [rfc-dist] RFC 5218 on What Makes For a Successful Protocol? Message-ID: <20080718233957.D575C1443E3@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5218 Title: What Makes For a Successful Protocol? Author: D. Thaler, B. Aboba Status: Informational Date: July 2008 Mailbox: dthaler at microsoft.com, bernarda at microsoft.com Pages: 28 Characters: 58409 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-protocol-success-04.txt URL: http://www.rfc-editor.org/rfc/rfc5218.txt The Internet community has specified a large number of protocols to date, and these protocols have achieved varying degrees of success. Based on case studies, this document attempts to ascertain factors that contribute to or hinder a protocol's success. It is hoped that these observations can serve as guidance for future protocol work. 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Fri Jul 18 16:40:01 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 18 Jul 2008 16:40:01 -0700 (PDT) Subject: [rfc-dist] RFC 5277 on NETCONF Event Notifications Message-ID: <20080718234001.152CE1443E6@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5277 Title: NETCONF Event Notifications Author: S. Chisholm, H. Trevino Status: Standards Track Date: July 2008 Mailbox: schishol at nortel.com, htrevino at cisco.com Pages: 35 Characters: 70878 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-netconf-notification-14.txt URL: http://www.rfc-editor.org/rfc/rfc5277.txt This document defines mechanisms that provide an asynchronous message notification delivery service for the Network Configuration protocol (NETCONF). This is an optional capability built on top of the base NETCONF definition. This document defines the capabilities and operations necessary to support this service. [STANDARDS TRACK] This document is a product of the Network Configuration 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Tue Jul 22 16:41:37 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 22 Jul 2008 16:41:37 -0700 (PDT) Subject: [rfc-dist] RFC 5279 on A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP) Message-ID: <20080722234137.CE42C14502F@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5279 Title: A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP) Author: A. Monrad, S. Loreto Status: Informational Date: July 2008 Mailbox: atle.monrad at ericsson.com, Salvatore.Loreto at ericsson.com Pages: 7 Characters: 11582 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-monrad-sipping-3gpp-urn-namespace-03.txt URL: http://www.rfc-editor.org/rfc/rfc5279.txt This document describes the Namespace Identifier (NID) for Uniform Resource Namespace (URN) resources published by the 3rd Generation Partnership Project (3GPP). 3GPP defines and manages resources that utilize this URN name model. Management activities for these and other resource types are provided by the 3GPP Support Team. 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Tue Jul 22 16:41:16 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 22 Jul 2008 16:41:16 -0700 (PDT) Subject: [rfc-dist] RFC 5283 on LDP Extension for Inter-Area Label Switched Paths (LSPs) Message-ID: <20080722234116.CA0A614502D@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5283 Title: LDP Extension for Inter-Area Label Switched Paths (LSPs) Author: B. Decraene, JL. Le Roux, I. Minei Status: Standards Track Date: July 2008 Mailbox: bruno.decraene at orange-ftgroup.com, jeanlouis.leroux at orange-ftgroup.com, ina at juniper.net Pages: 12 Characters: 26534 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-ldp-interarea-04.txt URL: http://www.rfc-editor.org/rfc/rfc5283.txt To facilitate the establishment of Label Switched Paths (LSPs) that would span multiple IGP areas in a given Autonomous System (AS), this document describes a new optional Longest-Match Label Mapping Procedure for the Label Distribution Protocol (LDP). This procedure allows the use of a label if the Forwarding Equivalence Class (FEC) Element matches an entry in the Routing Information Base (RIB). Matching is defined by an IP longest-match search and does not mandate an exact match. [STANDARDS TRACK] This document is a product of the Multiprotocol Label Switching Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Tue Jul 22 16:41:55 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Tue, 22 Jul 2008 16:41:55 -0700 (PDT) Subject: [rfc-dist] RFC 5267 on Contexts for IMAP4 Message-ID: <20080722234155.ED02D145031@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5267 Title: Contexts for IMAP4 Author: D. Cridland, C. King Status: Standards Track Date: July 2008 Mailbox: dave.cridland at isode.com, cking at mumbo.ca Pages: 18 Characters: 36709 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-cridland-imap-context-05.txt URL: http://www.rfc-editor.org/rfc/rfc5267.txt The IMAP4rev1 protocol has powerful search facilities as part of the core protocol, but lacks the ability to create live, updated results that can be easily handled. This memo provides such an extension, and shows how it can be used to provide a facility similar to virtual mailboxes. [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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Wed Jul 23 15:50:57 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 23 Jul 2008 15:50:57 -0700 (PDT) Subject: [rfc-dist] RFC 5285 on A General Mechanism for RTP Header Extensions Message-ID: <20080723225057.AE1341454E4@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5285 Title: A General Mechanism for RTP Header Extensions Author: D. Singer, H. Desineni Status: Standards Track Date: July 2008 Mailbox: singer at apple.com, hd at qualcomm.com Pages: 17 Characters: 36844 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-rtp-hdrext-15.txt URL: http://www.rfc-editor.org/rfc/rfc5285.txt This document provides a general mechanism to use the header extension feature of RTP (the Real-Time Transport Protocol). It provides the option to use a small number of small extensions in each RTP packet, where the universe of possible extensions is large and registration is de-centralized. The actual extensions in use in a session are signaled in the setup information for that session. [STANDARDS TRACK] This document is a product of the Audio/Video Transport Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Wed Jul 23 15:50:59 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Wed, 23 Jul 2008 15:50:59 -0700 (PDT) Subject: [rfc-dist] RFC 5340 on OSPF for IPv6 Message-ID: <20080723225059.328C51454E6@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5340 Title: OSPF for IPv6 Author: R. Coltun, D. Ferguson, J. Moy, A. Lindem Status: Standards Track Date: July 2008 Mailbox: dennis at juniper.net, jmoy at sycamorenet.com, acee at redback.com Pages: 94 Characters: 225664 Obsoletes: RFC2740 I-D Tag: draft-ietf-ospf-ospfv3-update-23.txt URL: http://www.rfc-editor.org/rfc/rfc5340.txt This document describes the modifications to OSPF to support version 6 of the Internet Protocol (IPv6). The fundamental mechanisms of OSPF (flooding, Designated Router (DR) election, area support, Short Path First (SPF) calculations, etc.) remain unchanged. However, some changes have been necessary, either due to changes in protocol semantics between IPv4 and IPv6, or simply to handle the increased address size of IPv6. These modifications will necessitate incrementing the protocol version from version 2 to version 3. OSPF for IPv6 is also referred to as OSPF version 3 (OSPFv3). Changes between OSPF for IPv4, OSPF Version 2, and OSPF for IPv6 as described herein include the following. Addressing semantics have been removed from OSPF packets and the basic Link State Advertisements (LSAs). New LSAs have been created to carry IPv6 addresses and prefixes. OSPF now runs on a per-link basis rather than on a per-IP-subnet basis. Flooding scope for LSAs has been generalized. Authentication has been removed from the OSPF protocol and instead relies on IPv6's Authentication Header and Encapsulating Security Payload (ESP). Even with larger IPv6 addresses, most packets in OSPF for IPv6 are almost as compact as those in OSPF for IPv4. Most fields and packet- size limitations present in OSPF for IPv4 have been relaxed. In addition, option handling has been made more flexible. All of OSPF for IPv4's optional capabilities, including demand circuit support and Not-So-Stubby Areas (NSSAs), are also supported in OSPF for IPv6. [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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Thu Jul 24 12:00:52 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Thu, 24 Jul 2008 12:00:52 -0700 (PDT) Subject: [rfc-dist] RFC 5290 on Comments on the Usefulness of Simple Best-Effort Traffic Message-ID: <20080724190052.7D2A41456BE@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5290 Title: Comments on the Usefulness of Simple Best-Effort Traffic Author: S. Floyd, M. Allman Status: Informational Date: July 2008 Mailbox: floyd at icir.org, mallman at icir.org Pages: 20 Characters: 48612 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-floyd-tsvwg-besteffort-03.txt URL: http://www.rfc-editor.org/rfc/rfc5290.txt This document presents some observations on "simple best-effort traffic", defined loosely for the purposes of this document as Internet traffic that is not covered by Quality of Service (QOS) mechanisms, congestion-based pricing, cost-based fairness, admissions control, or the like. One observation is that simple best-effort traffic serves a useful role in the Internet, and is worth keeping. While differential treatment of traffic can clearly be useful, we believe such mechanisms are useful as *adjuncts* to simple best- effort traffic, not as *replacements* of simple best-effort traffic. A second observation is that for simple best-effort traffic, some form of rough flow-rate fairness is a useful goal for resource allocation, where "flow-rate fairness" is defined by the goal of equal flow rates for different flows over the same path. 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute From rfc-editor at rfc-editor.org Fri Jul 25 14:54:23 2008 From: rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Date: Fri, 25 Jul 2008 14:54:23 -0700 (PDT) Subject: [rfc-dist] RFC 5278 on IANA Registration of Enumservices for Voice and Video Messaging Message-ID: <20080725215423.1F695145AC0@bosco.isi.edu> A new Request for Comments is now available in online RFC libraries. RFC 5278 Title: IANA Registration of Enumservices for Voice and Video Messaging Author: J. Livingood, D. Troshynski Status: Standards Track Date: July 2008 Mailbox: jason_livingood at cable.comcast.com, dtroshynski at acmepacket.com Pages: 22 Characters: 39745 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-enum-vmsg-02.txt URL: http://www.rfc-editor.org/rfc/rfc5278.txt This document registers the Enumservice named "vmsg", which is used to facilitate the real-time routing of voice, video, and unified communications to a messaging system. This vmsg Enumservice registers three Enumservice types: "voicemsg", "videomsg", and "unifmsg". Each type also registers the subtypes "sip", "sips", "http", and "https", as well as the subtype "tel" for the "voicemsg" type. [STANDARDS TRACK] This document is a product of the Telephone Number Mapping Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute