RFC 5151: Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions

This document describes procedures and protocol extensions for the use of Resource Reservation Protocol-Traffic Engineering (RSVP-TE) signaling in…

Read RFC 5151 on the RFC Editor

Outgoing relationships (24 related RFCs)

Updates, Normative reference — RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
Updates, Normative reference — RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Normative reference — RFC 4206: Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)
Normative reference — RFC 5150: Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE)
Normative reference — RFC 4420: Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
Informative reference — RFC 4655: A Path Computation Element (PCE)-Based Architecture
Informative reference — RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels
Informative reference — RFC 4379: Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
Informative reference — RFC 4107: Guidelines for Cryptographic Key Management
Informative reference — RFC 2747: RSVP Cryptographic Authentication
Informative reference — RFC 4873: GMPLS Segment Recovery
Informative reference — RFC 5152: A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)
Informative reference — RFC 4726: A Framework for Inter-Domain Multiprotocol Label Switching Traffic Engineering
Informative reference — RFC 4216: MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements
Informative reference — RFC 4208: Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model
Informative reference — RFC 4874: Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
Informative reference — RFC 3097: RSVP Cryptographic Authentication -- Updated Message Type Value
Informative reference — RFC 4920: Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE
Informative reference — RFC 4105: Requirements for Inter-Area MPLS Traffic Engineering
Informative reference — RFC 4736: Reoptimization of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Loosely Routed Label Switched Path (LSP)
Informative reference — RFC 5063: Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart
Informative reference — RFC 4561: Definition of a Record Route Object (RRO) Node-Id Sub-Object

Incoming relationships (8 related RFCs)

Normatively referenced by — RFC 7570: Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)
Normatively referenced by — RFC 6373: MPLS Transport Profile (MPLS-TP) Control Plane Framework
Informatively referenced by — RFC 6518: Keying and Authentication for Routing Protocols (KARP) Design Guidelines
Informatively referenced by — RFC 5376: Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)
Informatively referenced by — RFC 8776: Common YANG Data Types for Traffic Engineering
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Informatively referenced by — RFC 5298: Analysis of Inter-Domain Label Switched Path (LSP) Recovery
Informatively referenced by — RFC 5283: LDP Extension for Inter-Area Label Switched Paths (LSPs)