RFC 4206: Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)

To improve scalability of Generalized Multi-Protocol Label Switching (GMPLS) it may be useful to aggregate Label Switched Paths (LSPs) by creating a hierarchy…

Read RFC 4206 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 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 3630: Traffic Engineering (TE) Extensions to OSPF Version 2
Normative reference — RFC 4203: OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Normative reference — RFC 2747: RSVP Cryptographic Authentication
Normative reference — RFC 3036: LDP Specification
Normative reference — RFC 3477: Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)
Normative reference — RFC 3784: Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE)
Normative reference — RFC 3472: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions
Normative reference — RFC 4205: Intermediate System to Intermediate System (IS-IS) Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Normative reference — RFC 3480: Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)
Informative reference — RFC 4201: Link Bundling in MPLS Traffic Engineering (TE)
Informative reference — RFC 4204: Link Management Protocol (LMP)

Incoming relationships (30 related RFCs)

Updated by, Normatively referenced by — RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)
Updated by, Normatively referenced by — RFC 6107: Procedures for Dynamically Signaled Hierarchical Label Switched Paths
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 5212: Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN)
Normatively referenced by — RFC 5151: Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions
Normatively referenced by — RFC 8964: Deterministic Networking (DetNet) Data Plane: MPLS
Normatively referenced by — RFC 6373: MPLS Transport Profile (MPLS-TP) Control Plane Framework
Normatively referenced by — RFC 7062: Framework for GMPLS and PCE Control of G.709 Optical Transport Networks
Normatively referenced by — RFC 5146: Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks
Normatively referenced by — RFC 7698: Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks
Normatively referenced by — RFC 7810: IS-IS Traffic Engineering (TE) Metric Extensions
Normatively referenced by — RFC 8282: Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering
Normatively referenced by — RFC 4990: Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks
Normatively referenced by — RFC 5251: Layer 1 VPN Basic Mode
Normatively referenced by — RFC 5439: An Analysis of Scaling Issues in MPLS-TE Core Networks
Normatively referenced by — RFC 6457: PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic Engineering
Informatively referenced by — RFC 5420: Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)
Informatively referenced by — RFC 4216: MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements
Informatively referenced by — RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
Informatively referenced by — RFC 5376: Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)
Informatively 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)
Informatively referenced by — RFC 5817: Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks
Informatively referenced by — RFC 8795: YANG Data Model for Traffic Engineering (TE) Topologies
Informatively referenced by — RFC 7325: MPLS Forwarding Compliance and Performance Requirements
Informatively referenced by — RFC 5145: Framework for MPLS-TE to GMPLS Migration
Informatively referenced by — RFC 5339: Evaluation of Existing GMPLS Protocols against Multi-Layer and Multi-Region Networks (MLN/MRN)
Informatively referenced by — RFC 6016: Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs
Informatively referenced by — RFC 6411: Applicability of Keying Methods for RSVP Security
Informatively referenced by — RFC 7190: Use of Multipath with MPLS and MPLS Transport Profile (MPLS-TP)
Informatively referenced by — RFC 9689: Use Cases for a PCE as a Central Controller (PCECC)