RSVP-TE

RSVP-TE
Name	RSVP-TE
Introduced	1997
Developer	Internet Engineering Task Force
Status	standardized
Related	Multiprotocol Label Switching, Resource Reservation Protocol

RSVP-TE

Resource Reservation Protocol-Traffic Engineering (RSVP-TE) is an extension of Resource Reservation Protocol designed to support label-switched paths for Multiprotocol Label Switching networks, enabling explicit path setup, bandwidth reservation, and constraint-based routing. It bridges control-plane functions used in deployments by vendors such as Cisco Systems, Juniper Networks, and Nokia with operator frameworks from AT&T, Verizon Communications, and Deutsche Telekom. Developed within the Internet Engineering Task Force working groups and standardized via several RFCs, RSVP-TE integrates with routing protocols like Open Shortest Path First and Intermediate System to Intermediate System to provide traffic-engineering capabilities for service providers and data centers.

Overview

RSVP-TE augments Resource Reservation Protocol to carry label information for Multiprotocol Label Switching LSPs, supporting explicit routing and setup of point-to-point and point-to-multipoint tunnels. The protocol operates alongside routing protocols such as Border Gateway Protocol, Open Shortest Path First, Intermediate System to Intermediate System, and leverages topology and constraint data from traffic-engineering databases similar to those in IS-IS Traffic Engineering extensions. Originally motivated by requirements from large carriers including BT Group and research from institutions like MIT and Stanford University, RSVP-TE was specified to meet the demands of modern backbone networks and carrier-grade systems.

Protocol Operation

RSVP-TE uses a downstream-assigned label model where label bindings and path state propagate hop-by-hop between ingress and egress routers. Path messages follow explicit or computed routes discovered via protocols such as OSPF or IS-IS, while Reservation messages establish and maintain resource allocations. When establishing an LSP, RSVP-TE exchanges PATH and RESV messages, installs forwarding state in routers from vendors like Juniper Networks, Huawei, and Arista Networks, and interacts with control-plane features in platforms from Cisco Systems and Nokia. RSVP-TE supports mechanisms to reroute around failures leveraging fast-reroute techniques referenced by standards bodies including the IETF and operational practices of carriers such as Sprint Corporation and Orange S.A..

Signaling Messages and Objects

Key RSVP-TE messages include PATH and RESV, augmented by objects such as LABEL_REQUEST, EXPLICIT_ROUTE, and SESSION, enabling explicit-route objects that reference addresses and constraints from networks managed by operators like Level 3 Communications or cloud providers like Amazon Web Services. The protocol defines class-specific objects for policy, recording, and bandwidth constraints, interoperating with control-plane elements from systems such as Juniper Junos, Cisco IOS XR, and network management suites from SolarWinds and NetBrain. Message types allow extension and vendor-specific objects, which have been used in deployments by IBM labs and research projects at Carnegie Mellon University to prototype advanced reservation policies.

Traffic Engineering Mechanisms

RSVP-TE implements constraint-based routing, explicit route objects, bandwidth reservation, and path setup to satisfy requirements for differentiated services for customers including enterprises served by Vodafone and content providers like Netflix. It integrates with offline and online admission control systems found in OSS tools from Ericsson and analytics platforms by Splunk to coordinate capacity. Traffic-engineering features include setup of primary and backup LSPs, fast reroute for protection against link and node failures inspired by methods researched at Bell Labs, and affinity/avoidance constraints used by carriers such as Telefonica to manage maintenance and regulatory restrictions.

Scalability, Reliability, and Security

RSVP-TE faces scalability challenges in large-scale networks due to per-LSP state in routers; operators like Google and Microsoft often assess trade-offs between RSVP-TE and alternatives such as segment routing proposals from IETF and implementations in platforms by Facebook. Reliability features include soft-state refresh, state refresh reduction, and fast-reroute extensions developed in coordination with standards bodies like IETF's working groups. Security considerations address message authentication and authorization, integrating with network AAA systems from Cisco Systems and identity frameworks used by Oracle and SAP to prevent unauthorized LSP creation or label hijacking.

Implementations and Interoperability

Major router vendors including Cisco Systems, Juniper Networks, Huawei, Nokia, and Arista Networks provide RSVP-TE in their operating systems, enabling interoperation across multi-vendor backbones operated by providers such as NTT Communications and T-Mobile. Interoperability tests have been conducted at events and labs associated with IETF meetings, carrier consortiums, and research centers like GÉANT to validate cross-platform behavior and conformance to RFC specifications. Open-source projects and research implementations exist in platforms influenced by Linux Foundation initiatives and university research from University of California, Berkeley.

Use Cases and Deployment Considerations

RSVP-TE is used for carrier backbone LSPs, VPN services for enterprise customers like IBM and Accenture, traffic segregation for content delivery networks managed by Akamai Technologies, and deterministic paths for telecommunications services offered by Vodafone and Orange S.A.. Deployment considerations include state scalability, control-plane processor load on routers by Cisco and Juniper, and operational complexity addressed in vendor training from Juniper Networks and Cisco Systems certifications. Some operators opt for segment routing to reduce per-LSP state, while others maintain RSVP-TE for fine-grained admission control and existing managed services demanded by clients such as Deutsche Bank and Goldman Sachs.

Category:Internet protocols