RFC 4054: Impairments and Other Constraints on Optical Layer Routing
In plain English — editorial summary, not part of the RFC
Optical networking poses a number challenges for Generalized Multi-Protocol Label Switching (GMPLS). Fundamentally, optical technology is an analog rather than digital technology whereby the optical layer is lowest in the transport hierarchy and hence has an intimate relationship with the physical geography of the network. This contribution surveys some of the aspects of optical networks that impact routing and identifies possible GMPLS responses for each: (1) Constraints arising from the design of new software controllable network elements, (2) Constraints in a single all-optical domain without wavelength conversion, (3) Complications arising in more complex networks incorporating both all-optical and opaque architectures, and (4) Impacts of diversity constraints. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4054
- Published
- May 2005
- Authors
- J. Strand; A. Chiu
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sub
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7096Evaluation of Existing GMPLS Encoding against G.709v3 Optical Transport Networks (OTNs)Current
January 2014
- RFC 3945Generalized Multi-Protocol Label Switching (GMPLS) ArchitectureUpdated
November 2004
- RFC 4201Link Bundling in MPLS Traffic Engineering (TE)Current
October 2005
- RFC 4204Link Management Protocol (LMP)Updated
October 2005
- RFC 4207Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Encoding for Link Management Protocol (LMP) Test MessagesUpdated
October 2005
- RFC 4223Reclassification of RFC 1863 to HistoricCurrent
October 2005
- RFC 4271A Border Gateway Protocol 4 (BGP-4)Updated
January 2006
- RFC 3719Recommendations for Interoperable Networks using Intermediate System to Intermediate System (IS-IS)Current
February 2004
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?