Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6138
Discuss this RFC: Send questions or comments to the mailing listmpls@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6138
RFC 5443 describes a mechanism to achieve LDP IGP synchronization toprevent black-holing traffic (e.g., VPN) when an Interior GatewayProtocol (IGP) is operational on a link but Label DistributionProtocol (LDP) is not. If this mechanism is applied to broadcastlinks that have more than one LDP peer, the metric increaseprocedure can only be applied to the link as a whole but not to anindividual peer. When a new LDP peer comes up on a broadcast network,this can result in loss of traffic through other established peers onthat network. This document describes a mechanism to address thatuse-case without dropping traffic. The mechanism does not introduceany protocol message changes. This document is not an Internet Standards Track specification; it is published for informational purposes.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.