rfc-3209

RSVP-TE: Extensions to RSVP for LSP Tunnels

D. Awduche, L. Berger, D. Gan, T. Li, V. Srinivasan, G. Swallow

date2001-12 streamIETF areartg wgmpls statusPROPOSED STANDARD pages61 canonicalhttps://www.rfc-editor.org/rfc/rfc3209 doi10.17487/RFC3209 errataview

This document describes the use of RSVP (Resource Reservation Protocol), including all the necessary extensions, to establish label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching). Since the flow along an LSP is completely identified by the label applied at the ingress node of the path, these paths may be treated as tunnels. A key application of LSP tunnels is traffic engineering with MPLS as specified in RFC 2702. [STANDARDS-TRACK]

updated by

rfc-3936 — Procedures for Modifying the Resource reSerVation Protocol (RSVP)
rfc-4420 — Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
rfc-4874 — Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
rfc-5151 — Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions
rfc-5420 — Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)
rfc-5711 — Node Behavior upon Originating and Receiving Resource Reservation Protocol (RSVP) Path Error Messages
rfc-6780 — RSVP ASSOCIATION Object Extensions
rfc-6790 — The Use of Entropy Labels in MPLS Forwarding
rfc-7274 — Allocating and Retiring Special-Purpose MPLS Labels