%% You should probably cite rfc8577 instead of this I-D. @techreport{ietf-mpls-rsvp-shared-labels-05, number = {draft-ietf-mpls-rsvp-shared-labels-05}, 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-rsvp-shared-labels/05/}, author = {Harish Sitaraman and Vishnu Pavan Beeram and Tejal Parikh and Tarek Saad}, title = {{Signaling RSVP-TE tunnels on a shared MPLS forwarding plane}}, pagetotal = 22, year = 2018, month = oct, day = 16, abstract = {As the scale of MPLS RSVP-TE networks has grown, so the number of Label Switched Paths (LSPs) supported by individual network elements has increased. Various implementation recommendations have been proposed to manage the resulting increase in control plane state. However, those changes have had no effect on the number of labels that a transit Label Switching Router (LSR) has to support in the forwarding plane. That number is governed by the number of LSPs transiting or terminated at the LSR and is directly related to the total LSP state in the control plane. This document defines a mechanism to prevent the maximum size of the label space limit on an LSR from being a constraint to control plane scaling on that node. It introduces the notion of pre-installed 'per Traffic Engineering (TE) link labels' that can be shared by MPLS RSVP-TE LSPs that traverse these TE links. This approach significantly reduces the forwarding plane state required to support a large number of LSPs. This couples the feature benefits of the RSVP-TE control plane with the simplicity of the Segment Routing MPLS forwarding plane.}, }