RFC 5919: Signaling LDP Label Advertisement Completion
In plain English — editorial summary, not part of the RFC
There are situations following Label Distribution Protocol (LDP) session establishment where it would be useful for an LDP speaker to know when its peer has advertised all of its labels. The LDP specification provides no mechanism for an LDP speaker to notify a peer when it has completed its initial label advertisements to that peer. This document specifies means for an LDP speaker to signal completion of its initial label advertisements following session establishment. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5919
- Published
- August 2010
- Authors
- R. Asati; P. Mohapatra; E. Chen; B. Thomas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5443LDP IGP SynchronizationUpdated
March 2009
- RFC 7307LDP Extensions for Multi-TopologyUpdated
July 2014
- RFC 7552Updates to LDP for IPv6Current
June 2015
- RFC 3815Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)Current
June 2004
- RFC 3479Fault Tolerance for the Label Distribution Protocol (LDP)Current
February 2003
- RFC 3478Graceful Restart Mechanism for Label Distribution ProtocolCurrent
February 2003
- RFC 3212Constraint-Based LSP Setup using LDPUpdated
January 2002
- RFC 3038VCID Notification over ATM link for LDPUpdated
January 2001
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?