RFC 5818: Data Channel Status Confirmation Extensions for the Link Management Protocol
In plain English — editorial summary, not part of the RFC
This document defines simple additions to the Link Management Protocol (LMP) to provide a control plane tool that can assist in the location of stranded resources by allowing adjacent Label-Switching Routers (LSRs) to confirm data channel statuses and provide triggers for notifying the management plane if any discrepancies are found. As LMP is already used to verify data plane connectivity, it is considered to be an appropriate candidate to support this feature. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5818
- Published
- April 2010
- Authors
- D. Li; H. Xu; S. Bardalai; J. Meuric; D. Caviglia
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- 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 5817Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering NetworksCurrent
April 2010
- RFC 5820Extensions to OSPF to Support Mobile Ad Hoc NetworkingUpdated
March 2010
- RFC 5814Label Switched Path (LSP) Dynamic Provisioning Performance Metrics in Generalized MPLS NetworksCurrent
March 2010
- RFC 5813Forwarding and Control Element Separation (ForCES) MIBCurrent
March 2010
- RFC 5812Forwarding and Control Element Separation (ForCES) Forwarding Element ModelUpdated
March 2010
- RFC 5824Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPNCurrent
April 2010
- RFC 5811SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) ProtocolCurrent
March 2010
- RFC 5810Forwarding and Control Element Separation (ForCES) Protocol SpecificationUpdated
March 2010
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?