Automatically Switched Optical Network (ASON) Routing for OSPFv2 Protocols
RFC 6827
Document | Type |
RFC - Proposed Standard
(January 2013; No errata)
Obsoletes RFC 5787
Updates RFC 5786
|
|
---|---|---|---|
Authors | Andy Malis , Acee Lindem , Papadimitriou Dimitri | ||
Last updated | 2018-12-20 | ||
Replaces | draft-malis-ccamp-rfc5787bis | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | Deborah Brungard | ||
IESG | IESG state | RFC 6827 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Adrian Farrel | ||
IESG note | Deborah Brungard (dbrungard@att.com) is the Document Shepherd. | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) A. Malis, Ed. Request for Comments: 6827 Verizon Communications Obsoletes: 5787 A. Lindem, Ed. Updates: 5786 Ericsson Category: Standards Track D. Papadimitriou, Ed. ISSN: 2070-1721 Alcatel-Lucent January 2013 Automatically Switched Optical Network (ASON) Routing for OSPFv2 Protocols Abstract The ITU-T has defined an architecture and requirements for operating an Automatically Switched Optical Network (ASON). The Generalized Multiprotocol Label Switching (GMPLS) protocol suite is designed to provide a control plane for a range of network technologies. These include optical networks such as time division multiplexing (TDM) networks including the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH), Optical Transport Networks (OTNs), and lambda switching optical networks. The requirements for GMPLS routing to satisfy the requirements of ASON routing and an evaluation of existing GMPLS routing protocols are provided in other documents. This document defines extensions to the OSPFv2 Link State Routing Protocol to meet the requirements for routing in an ASON. Note that this work is scoped to the requirements and evaluation expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations that were current when those documents were written. Future extensions or revisions of this work may be necessary if the ITU-T Recommendations are revised or if new requirements are introduced into a revision of RFC 4258. This document obsoletes RFC 5787 and updates RFC 5786. Malis, et al. Standards Track [Page 1] RFC 6827 ASON Routing for OSPFv2 Protocols January 2013 Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6827. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Malis, et al. Standards Track [Page 2] RFC 6827 ASON Routing for OSPFv2 Protocols January 2013 Table of Contents 1. Introduction ....................................................4 1.1. Conventions Used in This Document ..........................5 2. Routing Areas, OSPF Areas, and Protocol Instances ...............5 3. Terminology and Identification ..................................6 4. Reachability ....................................................7 5. Link Attribute ..................................................8 5.1. Local Adaptation ...........................................8 5.2. Bandwidth Accounting .......................................9 6. Routing Information Scope .......................................9 6.1. Link Advertisement (Local and Remote TE Router ID Sub-TLV) .9 6.2. Reachability Advertisement (Local TE Router ID Sub-TLV) ...11 7. Routing Information Dissemination ..............................11 7.1. Import/Export Rules .......................................12 7.2. Loop Prevention ...........................................12 7.2.1. Inter-RA Export Upward/Downward Sub-TLVs ...........13 7.2.2. Inter-RA Export Upward/Downward Sub-TLV Processing .13 8. OSPFv2 Scalability .............................................14 9. Security Considerations ........................................15 10. IANA Considerations ...........................................15 10.1. Sub-TLVs of the Link TLV .................................15 10.2. Sub-TLVs of the Node Attribute TLV .......................16Show full document text