RFC 7581: Routing and Wavelength Assignment Information Encoding for Wavelength Switched Optical Networks
In plain English — editorial summary, not part of the RFC
A Wavelength Switched Optical Network (WSON) requires certain key information fields be made available to facilitate path computation and the establishment of Label Switched Paths (LSPs). The information model described in "Routing and Wavelength Assignment Information Model for Wavelength Switched Optical Networks" (RFC 7446) shows what information is required at specific points in the WSON. Part of the WSON information model contains aspects that may be of general applicability to other technologies, while other parts are specific to WSONs. This document provides efficient, protocol-agnostic encodings for the WSON-specific information fields. It is intended that protocol- specific documents will reference this memo to describe how information is carried for specific uses. Such encodings can be used to extend GMPLS signaling and routing protocols. In addition, these encodings could be used by other mechanisms to convey this same information to a Path Computation Element (PCE).
Document record
- Document ID
- RFC7581
- Published
- June 2015
- Authors
- G. Bernstein; Y. Lee; D. Li; W. Imajuku; J. Han
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7580OSPF-TE Extensions for General Network Element ConstraintsCurrent
June 2015
- RFC 7792RSVP-TE Signaling Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) NetworksCurrent
March 2016
- RFC 7582Multicast Virtual Private Network (MVPN): Using Bidirectional P-TunnelsUpdated
July 2015
- RFC 7579General Network Element Constraint Encoding for GMPLS-Controlled NetworksCurrent
June 2015
- RFC 7571GMPLS RSVP-TE Extensions for Lock Instruct and LoopbackCurrent
July 2015
- RFC 7570Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)Current
July 2015
- RFC 7602IS-IS Extended Sequence Number TLVCurrent
July 2015
- RFC 7606Revised Error Handling for BGP UPDATE MessagesCurrent
August 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?