RFC 6138: LDP IGP Synchronization for Broadcast Networks
In plain English — editorial summary, not part of the RFC
RFC 5443 describes a mechanism to achieve LDP IGP synchronization to prevent black-holing traffic (e.g., VPN) when an Interior Gateway Protocol (IGP) is operational on a link but Label Distribution Protocol (LDP) is not. If this mechanism is applied to broadcast links that have more than one LDP peer, the metric increase procedure can only be applied to the link as a whole but not to an individual peer. When a new LDP peer comes up on a broadcast network, this can result in loss of traffic through other established peers on that network. This document describes a mechanism to address that use-case without dropping traffic. The mechanism does not introduce any protocol message changes. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6138
- Published
- February 2011
- Authors
- S. Kini; W. Lu
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 5443
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6136Layer 2 Virtual Private Network (L2VPN) Operations, Administration, and Maintenance (OAM) Requirements and FrameworkCurrent
March 2011
- RFC 6130Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)Updated
April 2011
- RFC 6123Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group DraftsCurrent
February 2011
- RFC 6119IPv6 Traffic Engineering in IS-ISCurrent
February 2011
- RFC 6163Framework for GMPLS and Path Computation Element (PCE) Control of Wavelength Switched Optical Networks (WSONs)Current
April 2011
- RFC 6165Extensions to IS-IS for Layer-2 SystemsCurrent
April 2011
- RFC 6166A Registry for PIM Message TypesObsoleted
April 2011
- RFC 6107Procedures for Dynamically Signaled Hierarchical Label Switched PathsCurrent
February 2011
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?