{'fraction_non_alphanumeric': 0.01954120645709431, 'fraction_numerical': 0.0, 'mean_word_length': 4.718446601941747, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane

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.