RFC 4875: Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)

This document describes extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for the set up of Traffic Engineered (TE)…

Read RFC 4875 on the RFC Editor

Outgoing relationships (14 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
Normative reference — RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Normative reference — RFC 3031: Multiprotocol Label Switching Architecture
Normative reference — RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
Normative reference — RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description
Normative reference — RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels
Normative reference — RFC 4206: Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)
Normative reference — RFC 4873: GMPLS Segment Recovery
Normative reference — RFC 3477: Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)
Normative reference — RFC 2961: RSVP Refresh Overhead Reduction Extensions
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 4461: Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)
Informative reference — RFC 4003: GMPLS Signaling Procedure for Egress Control

Incoming relationships (40 related RFCs)

Updated by, Normatively referenced by — RFC 6510: Resource Reservation Protocol (RSVP) Message Formats for Label Switched Path (LSP) Attributes Objects
Normatively referenced by — RFC 6513: Multicast in MPLS/BGP IP VPNs
Normatively referenced by — RFC 5960: MPLS Transport Profile Data Plane Architecture
Normatively referenced by — RFC 5073: IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities
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 7570: Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)
Normatively referenced by — RFC 6389: MPLS Upstream Label Assignment for LDP
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 7524: Inter-Area Point-to-Multipoint (P2MP) Segmented Label Switched Paths (LSPs)
Normatively referenced by — RFC 8306: Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
Normatively referenced by — RFC 6007: Use of the Synchronization VECtor (SVEC) List for Synchronized Dependent Path Computations
Normatively referenced by — RFC 9026: Multicast VPN Fast Upstream Failover
Normatively referenced by — RFC 7167: A Framework for Point-to-Multipoint MPLS in Transport Networks
Informatively referenced by — RFC 6514: BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs
Informatively referenced by — RFC 6388: Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths
Informatively referenced by — RFC 6790: The Use of Entropy Labels in MPLS Forwarding
Informatively referenced by — RFC 6425: Detecting Data-Plane Failures in Point-to-Multipoint MPLS - Extensions to LSP Ping
Informatively referenced by — RFC 7981: IS-IS Extensions for Advertising Router Information
Informatively referenced by — RFC 7102: Terms Used in Routing for Low-Power and Lossy Networks
Informatively referenced by — RFC 7117: Multicast in Virtual Private LAN Service (VPLS)
Informatively referenced by — RFC 4971: Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information
Informatively referenced by — RFC 8964: Deterministic Networking (DetNet) Data Plane: MPLS
Informatively referenced by — RFC 6060: Generalized Multiprotocol Label Switching (GMPLS) Control of Ethernet Provider Backbone Traffic Engineering (PBB-TE)
Informatively referenced by — RFC 7260: GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) Configuration
Informatively referenced by — RFC 9572: Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures
Informatively referenced by — RFC 5671: Applicability of the Path Computation Element (PCE) to Point-to-Multipoint (P2MP) MPLS and GMPLS Traffic Engineering (TE)
Informatively referenced by — RFC 6004: Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Service Switching
Informatively referenced by — RFC 6373: MPLS Transport Profile (MPLS-TP) Control Plane Framework
Informatively referenced by — RFC 7325: MPLS Forwarding Compliance and Performance Requirements
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Informatively referenced by — RFC 5501: Requirements for Multicast Support in Virtual Private LAN Services
Informatively referenced by — RFC 5862: Path Computation Clients (PCC) - Path Computation Element (PCE) Requirements for Point-to-Multipoint MPLS-TE
Informatively referenced by — RFC 6348: Requirements for Point-to-Multipoint Extensions to the Label Distribution Protocol
Informatively referenced by — RFC 7334: PCE-Based Computation Procedure to Compute Shortest Constrained Point-to-Multipoint (P2MP) Inter-Domain Traffic Engineering Label Switched Paths
Informatively referenced by — RFC 7439: Gap Analysis for Operating IPv6-Only MPLS Networks
Informatively referenced by — RFC 7555: Proxy MPLS Echo Request
Informatively referenced by — RFC 9624: EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER)
Informatively referenced by — RFC 9938: A Framework for the Deterministic Networking (DetNet) Controller Plane
Informatively referenced by — RFC 6411: Applicability of Keying Methods for RSVP Security
Informatively referenced by — RFC 8339: Definition of P2MP PW TLV for Label Switched Path (LSP) Ping Mechanisms