Skip to main content

Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane
RFC 8577

Revision differences

Document history

Date By Action
2020-01-20
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2019-08-19
Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2019-08-19
Gunter Van de Velde Assignment of request for Last Call review by OPSDIR to Éric Vyncke was marked no-response
2019-05-30
(System) Received changes through RFC Editor sync (added Errata tag)
2019-04-30
(System)
Received changes through RFC Editor sync (created alias RFC 8577, changed title to 'Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane', changed abstract …
Received changes through RFC Editor sync (created alias RFC 8577, changed title to 'Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane', changed abstract to 'As the scale of MPLS RSVP-TE networks has grown, 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 the amount of control-plane state information.

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 preinstalled 'per-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 (SR) MPLS forwarding plane.', changed pages to 24, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-04-30, changed IESG state to RFC Published)
2019-04-30
(System) RFC published