RFC 4216: MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements

This document discusses requirements for the support of inter-AS MPLS Traffic Engineering (MPLS TE). Its main objective is to present a set of requirements…

Read RFC 4216 on the RFC Editor

Outgoing relationships (18 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 2702: Requirements for Traffic Engineering Over MPLS
Informative reference — RFC 3031: Multiprotocol Label Switching Architecture
Informative reference — RFC 3473: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
Informative reference — RFC 2475: An Architecture for Differentiated Services
Informative reference — RFC 4090: Fast Reroute Extensions to RSVP-TE for LSP Tunnels
Informative reference — RFC 1771: A Border Gateway Protocol 4 (BGP-4)
Informative reference — RFC 3246: An Expedited Forwarding PHB (Per-Hop Behavior)
Informative reference — RFC 3270: Multi-Protocol Label Switching (MPLS) Support of Differentiated Services
Informative reference — RFC 4206: Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)
Informative reference — RFC 2597: Assured Forwarding PHB Group
Informative reference — RFC 3443: Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks
Informative reference — RFC 3272: Overview and Principles of Internet Traffic Engineering
Informative reference — RFC 3469: Framework for Multi-Protocol Label Switching (MPLS)-based Recovery
Informative reference — RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering
Informative reference — RFC 3346: Applicability Statement for Traffic Engineering with MPLS
Informative reference — RFC 2430: A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)

Incoming relationships (14 related RFCs)

Normatively referenced by — RFC 5394: Policy-Enabled Path Computation Framework
Normatively referenced by — RFC 5376: Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)
Normatively referenced by — RFC 8694: Applicability of the Path Computation Element to Inter-area and Inter-AS MPLS and GMPLS Traffic Engineering
Informatively referenced by — RFC 5441: A Backward-Recursive PCE-Based Computation (BRPC) Procedure to Compute Shortest Constrained Inter-Domain Traffic Engineering Label Switched Paths
Informatively referenced by — RFC 5520: Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism
Informatively referenced by — RFC 5316: ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Informatively referenced by — RFC 5559: Pre-Congestion Notification (PCN) Architecture
Informatively referenced by — RFC 4874: Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
Informatively referenced by — RFC 5392: OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Informatively referenced by — RFC 5151: Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions
Informatively referenced by — RFC 6805: The Application of the Path Computation Element Architecture to the Determination of a Sequence of Domains in MPLS and GMPLS
Informatively referenced by — RFC 8685: Path Computation Element Communication Protocol (PCEP) Extensions for the Hierarchical Path Computation Element (H-PCE) Architecture
Informatively referenced by — RFC 9346: IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Informatively referenced by — RFC 6411: Applicability of Keying Methods for RSVP Security