LDP Downstream-on-Demand in Seamless MPLS

Document Type Replaced Internet-Draft (individual)
Authors Kishore Tiruveedhula  , Luca Martini  , Thomas Beckhaus  , Bruno Decraene  , Maciek Konstantynowicz 
Last updated 2012-01-05 (latest revision 2011-10-31)
Replaced by RFC 7032, RFC 7032
Stream (None)
Expired & archived
pdf htmlized bibtex
Additional Resources
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mpls-ldp-dod, draft-ietf-mpls-ldp-dod
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Seamless MPLS design enables a single IP/MPLS network to scale over core, metro and access parts of a large packet network infrastructure using standardized IP/MPLS protocols. One of the key goals of Seamless MPLS is to meet requirements specific to access, including high number of devices, their position in network topology and their compute and memory constraints that limit the amount of state access devices can hold.This can be achieved with LDP Downstream-on-Demand (LDP DoD) label advertisement. This document describes LDP DoD use cases and lists required LDP DoD procedures in the context of Seamless MPLS design. In addition, a new optional TLV type in the LDP label request message is defined for fast-up convergence.


Kishore Tiruveedhula (kishoret@juniper.net)
Luca Martini (lmartini@cisco.com)
Thomas Beckhaus (thomas.beckhaus@telekom.de)
Bruno Decraene (bruno.decraene@orange.com)
Maciek Konstantynowicz (maciek@juniper.net)

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