RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels

This document describes the use of RSVP (Resource Reservation Protocol), including all the necessary extensions, to establish label-switched paths (LSPs) in…

Read RFC 3209 on the RFC Editor

Outgoing relationships (13 related RFCs)

Informative reference — RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Informative reference — RFC 3031: Multiprotocol Label Switching Architecture
Informative reference — RFC 2474: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
Informative reference — RFC 1191: Path MTU discovery
Informative reference — RFC 3032: MPLS Label Stack Encoding
Informative reference — RFC 2210: The Use of RSVP with IETF Integrated Services
Informative reference — RFC 2702: Requirements for Traffic Engineering Over MPLS
Informative reference — RFC 2463: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
Informative reference — RFC 2211: Specification of the Controlled-Load Network Element Service
Informative reference — RFC 1349: Type of Service in the Internet Protocol Suite
Informative reference — RFC 2751: Signaled Preemption Priority Policy Element
Informative reference — RFC 2997: Specification of the Null Service Type
Informative reference — RFC 3210: Applicability Statement for Extensions to RSVP for LSP-Tunnels

Incoming relationships (156 related RFCs)

Showing 50 of 156 related RFCs.

Updated by, Normatively referenced by — RFC 6790: The Use of Entropy Labels in MPLS Forwarding
Updated by, Normatively referenced by — RFC 5420: Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)
Updated by, Normatively referenced by — RFC 4874: Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
Updated by, Normatively referenced by — RFC 5151: Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions
Updated by, Normatively referenced by — RFC 7274: Allocating and Retiring Special-Purpose MPLS Labels
Updated by, Normatively referenced by — RFC 4420: Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
Updated by, Normatively referenced by — RFC 5711: Node Behavior upon Originating and Receiving Resource Reservation Protocol (RSVP) Path Error Messages
Updated by, Normatively referenced by — RFC 6780: RSVP ASSOCIATION Object Extensions
Updated by, Normatively referenced by — RFC 3936: Procedures for Modifying the Resource reSerVation Protocol (RSVP)
Normatively referenced by — RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
Normatively referenced by — RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP)
Normatively referenced by — RFC 5920: Security Framework for MPLS and GMPLS Networks
Normatively referenced by — RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description
Normatively referenced by — RFC 3945: Generalized Multi-Protocol Label Switching (GMPLS) Architecture
Normatively referenced by — RFC 4875: Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)
Normatively referenced by — RFC 8231: Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
Normatively referenced by — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Normatively referenced by — RFC 4872: RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery
Normatively referenced by — RFC 4873: GMPLS Segment Recovery
Normatively referenced by — RFC 4461: Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)
Normatively referenced by — RFC 4216: MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements
Normatively referenced by — RFC 5394: Policy-Enabled Path Computation Framework
Normatively referenced by — RFC 5316: ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Normatively referenced by — RFC 5960: MPLS Transport Profile Data Plane Architecture
Normatively referenced by — RFC 7308: Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)
Normatively referenced by — RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Normatively referenced by — RFC 5073: IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities
Normatively referenced by — RFC 5392: OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Normatively referenced by — RFC 6372: MPLS Transport Profile (MPLS-TP) Survivability Framework
Normatively referenced by — RFC 7117: Multicast in Virtual Private LAN Service (VPLS)
Normatively referenced by — RFC 3811: Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management
Normatively referenced by — RFC 5521: Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions
Normatively referenced by — RFC 5565: Softwire Mesh Framework
Normatively referenced by — RFC 8964: Deterministic Networking (DetNet) Data Plane: MPLS
Normatively referenced by — RFC 3469: Framework for Multi-Protocol Label Switching (MPLS)-based Recovery
Normatively referenced by — RFC 4920: Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE
Normatively referenced by — RFC 4974: Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of Calls
Normatively referenced by — RFC 5557: Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization
Normatively referenced by — RFC 6006: Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
Normatively referenced by — RFC 6060: Generalized Multiprotocol Label Switching (GMPLS) Control of Ethernet Provider Backbone Traffic Engineering (PBB-TE)
Normatively referenced by — RFC 7139: GMPLS Signaling Extensions for Control of Evolving G.709 Optical Transport Networks
Normatively referenced by — RFC 5063: Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart
Normatively referenced by — RFC 6004: Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Service Switching
Normatively referenced by — RFC 7570: Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)
Normatively referenced by — RFC 7579: General Network Element Constraint Encoding for GMPLS-Controlled Networks
Normatively referenced by — RFC 6003: Ethernet Traffic Parameters
Normatively referenced by — RFC 6373: MPLS Transport Profile (MPLS-TP) Control Plane Framework
Normatively referenced by — RFC 6511: Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths
Normatively referenced by — RFC 7062: Framework for GMPLS and PCE Control of G.709 Optical Transport Networks
Normatively referenced by — RFC 7325: MPLS Forwarding Compliance and Performance Requirements