Skip to main content

LDP IGP Synchronization for broadcast networks

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Wenhu Lu , Sriganesh Kini
Last updated 2010-04-12 (Latest revision 2009-10-20)
Replaced by draft-ietf-mpls-ldp-igp-sync-bcast
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mpls-ldp-igp-sync-bcast
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


[LDP-IGP-SYNC] describes a mechanism to prevent black-holing traffic (e.g. VPN) when IGP is operational on a link but LDP is not. If this mechanism is applied to broadcast links that have more than one LDP/IGP peer, the cost-out procedure can only be applied to the link as a whole but not 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 changes.


Wenhu Lu
Sriganesh Kini

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)