Resource Reservation Protocol - Traffic Engineering (RSVP-TE) is an extension of the Resource Reservation Protocol (RSVP) for traffic engineering. It supports the reservation of resources across an IP network.

RSVP-TE is a signaling protocol and an extension of RSVP. RSVP-TE uses a soft state to manage its resource reservation states. This means we have to periodically send refresh messages to maintain the state information in routers along the path of our TE tunnel.

This chapter describes how to configure Multiprotocol Label Switching (MPLS) Resource Reservation Protocol (RSVP) Traffic Engineering (TE) on Cisco NX-OS devices. Your software release might not support all the features documented in this module.

2022年7月28日 · RSVP经扩展后可以支持 MPLS标签的分发， 并在传送标签绑定消息的同时携带资源预留信息，这种扩展后的 RSVP称为 RSVP-TE，作为一种信令协议用于在 MPLS TE中建立 LSP隧道。 “软状态”是指在 RSVP-TE中，通过消息的定时刷新来维持节点上的资源预留状态。 资源预留状态包括由 Path 消息创建的路径状态（ path state ）和由 Resv 消息创建的预留状 …

RSVP has been extended to use for MPLS TE and is called RSVP-TE. After calculating a TE tunnel path with CSPF, the router will signal the tunnel with RSVP-TE. RSVP-TE has three primary functions: Path setup and maintenance; Path teardown; Error signaling; When the headend router wants to signal a TE tunnel, it sends a PATH message downstream to ...

RSVP-TE (Resource Reservation Protocol-Traffic Engineering) is the enhanced RSVP for MPLS (Multi Protocol Label Switching). RSVP-TE is not a real routing protocol, but it works with routing protocols.

RSVP-TE-based signaling provides a means to establish tunnels dynamically. RSVP-TE uses the Downstream on Demand (DOD) label distribution mode, sending PATH messages from the ingress LER node to the egress LER, and RESV messages in the reverse direction.

2025年4月1日 · 2 commonly used terms in MPLS are LDP and RSVP-TE. While the former relates to easy provisioning in MPLS setup, the latter i.e. RSVP-TE is related to guarantee bandwidth for traffic communication. LDP setups LSPs based on routing data, whereas RSVP setups additional traffic engineered LSPs.

In particular, the extended RSVP protocol supports the instantiation of explicitly routed LSPs, with or without resource reservations. It also supports smooth rerouting of LSPs, preemption, and loop detection. The LSPs created with RSVP can be used to carry the "Traffic Trunks" described in [3].

Incremental State Update RSVP (as defined in [RFC2205] and as extended by RSVP-TE [RFC3209] and GMPLS [RFC3473]) uses the same basic approach to state communication and synchronization -- namely, full state is sent in each state advertisement message.