RFC 4209: Link Management Protocol (LMP) for Dense Wavelength Division Multiplexing (DWDM) Optical Line Systems
In plain English — editorial summary, not part of the RFC
The Link Management Protocol (LMP) is defined to manage traffic engineering (TE) links. In its present form, LMP focuses on peer nodes, i.e., nodes that peer in signaling and/or routing. This document proposes extensions to LMP to allow it to be used between a peer node and an adjacent optical line system (OLS). These extensions are intended to satisfy the "Optical Link Interface Requirements" described in a companion document. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4209
- Published
- October 2005
- Authors
- A. Fredette; J. Lang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
- Updated by:
- RFC 6898
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4558Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification StatementCurrent
June 2006
- RFC 3812Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)Current
June 2004
- RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current
February 2003
- RFC 7025Requirements for GMPLS Applications of PCECurrent
September 2013
- RFC 7399Unanswered Questions in the Path Computation Element ArchitectureCurrent
October 2014
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
- RFC 3785Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) MetricCurrent
May 2004
- RFC 4220Traffic Engineering Link Management Information BaseCurrent
November 2005
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?