%% You should probably cite draft-ietf-mpls-p2mp-loose-path-reopt instead of this I-D. @techreport{tsaad-mpls-p2mp-loose-path-reopt-03, number = {draft-tsaad-mpls-p2mp-loose-path-reopt-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-tsaad-mpls-p2mp-loose-path-reopt/03/}, author = {Tarek Saad and Rakesh Gandhi and Zafar Ali and Robert H. Venator and Yuji Kamite}, title = {{Reoptimization of Point-to-Multipoint Traffic Engineering Loosely Routed LSPs}}, pagetotal = 11, year = 2014, month = jul, day = 21, abstract = {For a Traffic Engineered (TE) point-to-multipoint (P2MP) Label Switched Path (LSP), it is preferable in some cases to re-evaluate and re-optimize the entire P2MP-TE LSP by re-signaling all its S2L sub-LSP(s). Existing mechanisms allow the path re-evaluation and the signaling of a the notification of preferred path exists for a single S2L sub-LSP only. This document defines RSVP-TE signaling extensions to allow an ingress Label Switching Router (LSR) of a P2MP-TE LSP to trigger the re-evaluation of the entire LSP tree containing one or more S2L sub- LSPs whose paths are loose (or abstract) hop expanded, and for a mid- point LSR to signal to the ingress LSR that a better tree exists for the entire P2MP-TE LSP.}, }