{'fraction_non_alphanumeric': 0.03387096774193549, 'fraction_numerical': 0.0, 'mean_word_length': 5.029126213592233, '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}}
Extending RSVP-TE to support inter-AS LSPs

Multiprotocol label switching (MPLS) is currently used inside autonomous systems (ASs) for virtual private networks (VPNs) or traffic engineering (TE) purposes. We first discuss the service provider's requirements for the utilization of MPLS label switched paths (LSPs) across AS boundaries. Then we propose a minimum set of extensions to RSVP-TE that allow inter-AS LSPs to be established in accordance with the SP's requirements. We also show how LSP protection techniques can be extended to provide link or node failure protection for the inter-AS links and border routers.