OSPFv2 Routing Protocols Extensions for Automatically Switched Optical Network (ASON) Routing
RFC 5787
| Document | Type |
RFC - Experimental
(March 2010; No errata)
Obsoleted by RFC 6827
|
|
|---|---|---|---|
| Last updated | 2018-12-20 | ||
| Replaces | draft-dimitri-ccamp-gmpls-ason-routing-ospf | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5787 (Experimental) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Adrian Farrel | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) D. Papadimitriou
Request for Comments: 5787 Alcatel-Lucent
Category: Experimental March 2010
ISSN: 2070-1721
OSPFv2 Routing Protocols Extensions for
Automatically Switched Optical Network (ASON) Routing
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 including optical networks such as time division
multiplexing (TDM) networks including SONET/SDH and 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
current when those documents were written. Future extensions of
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.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. 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). Not
all documents approved by the IESG are a candidate for any level of
Internet Standard; see Section 2 of RFC 5741.
Papdimitriou Experimental [Page 1]
RFC 5787 ASON Routing for OSPFv2 Protocols March 2010
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/rfc5787.
Copyright Notice
Copyright (c) 2010 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.
Papdimitriou Experimental [Page 2]
RFC 5787 ASON Routing for OSPFv2 Protocols March 2010
Table of Contents
1. Introduction ....................................................4
1.1. Conventions Used in This Document ..........................5
2. Routing Areas, OSPF Areas, and Protocol Instances ...............5
3. Reachability ....................................................6
3.1. Node IPv4 Local Prefix Sub-TLV .............................6
3.2. Node IPv6 Local Prefix Sub-TLV .............................7
4. Link Attribute ..................................................8
4.1. Local Adaptation ...........................................8
4.2. Bandwidth Accounting .......................................9
5. Routing Information Scope .......................................9
5.1. Terminology and Identification .............................9
5.2. Link Advertisement (Local and Remote TE Router ID
Sub-TLV) ..................................................10
5.3. Reachability Advertisement (Local TE Router ID sub-TLV) ...11
6. Routing Information Dissemination ..............................12
6.1. Import/Export Rules .......................................13
6.2. Discovery and Selection ...................................13
6.2.1. Upward Discovery and Selection .....................13
6.2.2. Downward Discovery and Selection ...................14
6.2.3. Router Information Experimental Capabilities TLV ...16
6.3. Loop Prevention ...........................................16
6.3.1. Associated RA ID ...................................17
6.3.2. Processing .........................................18
Show full document text