%% You should probably cite rfc7032 instead of this I-D. @techreport{ietf-mpls-ldp-dod-01, number = {draft-ietf-mpls-ldp-dod-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-mpls-ldp-dod/01/}, author = {Thomas Beckhaus and Bruno Decraene and Kishore Tiruveedhula and Maciek Konstantynowicz and Luca Martini}, title = {{LDP Downstream-on-Demand in Seamless MPLS}}, pagetotal = 33, year = 2012, month = mar, day = 12, abstract = {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.}, }