RFC 3272: Overview and Principles of Internet Traffic Engineering

This memo describes the principles of Traffic Engineering (TE) in the Internet. The document is intended to promote better understanding of the issues…

Read RFC 3272 on the RFC Editor

Incoming relationships (10 related RFCs)

Updated by, Normatively referenced by — RFC 5462: Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field
Obsoleted by, Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Normatively referenced by — RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering
Informatively referenced by — RFC 4216: MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements
Informatively referenced by — RFC 8964: Deterministic Networking (DetNet) Data Plane: MPLS
Informatively referenced by — RFC 8795: YANG Data Model for Traffic Engineering (TE) Topologies
Informatively referenced by — RFC 3386: Network Hierarchy and Multilayer Survivability
Informatively referenced by — RFC 3568: Known Content Network (CN) Request-Routing Mechanisms
Informatively referenced by — RFC 3906: Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering Tunnels
Informatively referenced by — RFC 4829: Label Switched Path (LSP) Preemption Policies for MPLS Traffic Engineering