Parikh et al 2019a - Revision history

Scipediacontent at 18:34, 5 March 2021

2021-03-05T18:34:37Z

Scipediacontent: Scipediacontent moved page Draft Content 629983216 to Parikh et al 2019a

2021-02-11T13:32:39Z

Scipediacontent moved page Draft Content 629983216 to Parikh et al 2019a

Scipediacontent: Created page with " == Abstract == 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 im..."

2021-02-11T13:32:35Z

Created page with " == Abstract == 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 im..."

New page

== Abstract ==

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.

== Original document ==

The different versions of the original document can be found in:

* [http://dx.doi.org/10.17487/rfc8577 http://dx.doi.org/10.17487/rfc8577]

* [https://www.rfc-editor.org/info/rfc8577 https://www.rfc-editor.org/info/rfc8577],
: [https://tools.ietf.org/html/rfc8577 https://tools.ietf.org/html/rfc8577],
: [https://www.rfc-editor.org/rfc/rfc8577.txt https://www.rfc-editor.org/rfc/rfc8577.txt],
: [https://trac.tools.ietf.org/html/rfc8577 https://trac.tools.ietf.org/html/rfc8577],
: [https://rfcs.web.fc2.com/draft-ietf-mpls-rsvp-shared-labels-09.html https://rfcs.web.fc2.com/draft-ietf-mpls-rsvp-shared-labels-09.html],
: [https://academic.microsoft.com/#/detail/2606277631 https://academic.microsoft.com/#/detail/2606277631]

@@ Line 2: / Line 2: @@
 == Abstract ==
- 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.
+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.
-−
 == Original document ==

← Older revision	Revision as of 13:32, 11 February 2021
(No difference)