RFC 5150: Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE)

In certain scenarios, there may be a need to combine several Generalized Multiprotocol Label Switching (GMPLS) Label Switched Paths (LSPs) such that a single…

Read RFC 5150 on the RFC Editor

Incoming relationships (14 related RFCs)

Normatively referenced by — RFC 5151: Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions
Normatively referenced by — RFC 7570: Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)
Normatively referenced by — RFC 5146: Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks
Normatively referenced by — RFC 6107: Procedures for Dynamically Signaled Hierarchical Label Switched Paths
Normatively referenced by — RFC 5251: Layer 1 VPN Basic Mode
Informatively referenced by — RFC 5921: A Framework for MPLS in Transport Networks
Informatively referenced by — RFC 6424: Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS Tunnels
Informatively referenced by — RFC 5376: Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)
Informatively referenced by — RFC 7491: A PCE-Based Architecture for Application-Based Network Operations
Informatively referenced by — RFC 8776: Common YANG Data Types for Traffic Engineering
Informatively referenced by — RFC 5145: Framework for MPLS-TE to GMPLS Migration
Informatively referenced by — RFC 5298: Analysis of Inter-Domain Label Switched Path (LSP) Recovery
Informatively referenced by — RFC 8282: Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering
Informatively referenced by — RFC 9689: Use Cases for a PCE as a Central Controller (PCECC)