RFC 6898: Link Management Protocol Behavior Negotiation and Configuration Modifications
In plain English — editorial summary, not part of the RFC
The Link Management Protocol (LMP) is used to coordinate the properties, use, and faults of data links in networks controlled by Generalized Multiprotocol Label Switching (GMPLS). This document defines an extension to LMP to negotiate capabilities and indicate support for LMP extensions. The defined extension is compatible with non-supporting implementations. This document updates RFC 4204, RFC 4207, RFC 4209, and RFC 5818.
Document record
- Document ID
- RFC6898
- Published
- March 2013
- Authors
- D. Li; D. Ceccarelli; L. Berger
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6905Requirements for Operations, Administration, and Maintenance (OAM) in Transparent Interconnection of Lots of Links (TRILL)Current
March 2013
- RFC 6907Use Cases and Interpretations of Resource Public Key Infrastructure (RPKI) Objects for Issuers and Relying PartiesCurrent
March 2013
- RFC 6916Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)Current
April 2013
- RFC 6923MPLS Transport Profile (MPLS-TP) Identifiers Following ITU-T ConventionsCurrent
May 2013
- RFC 6870Pseudowire Preferential Forwarding Status BitUpdated
February 2013
- RFC 6863Analysis of OSPF Security According to the Keying and Authentication for Routing Protocols (KARP) Design GuideCurrent
March 2013
- RFC 6862Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and RequirementsCurrent
March 2013
- RFC 6860Hiding Transit-Only Networks in OSPFCurrent
January 2013
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?