RFC 8821: PCE-Based Traffic Engineering (TE) in Native IP Networks

This document defines an architecture for providing traffic engineering in a native IP network using multiple BGP sessions and a Path Computation Element…

Read RFC 8821 on the RFC Editor

Outgoing relationships (10 related RFCs)

Normative reference — RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Normative reference — RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP)
Normative reference — RFC 4272: BGP Security Vulnerabilities Analysis
Normative reference — RFC 8231: Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
Normative reference — RFC 8253: PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)
Normative reference — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Normative reference — RFC 4456: BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
Normative reference — RFC 8283: An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central Control
Informative reference — RFC 4655: A Path Computation Element (PCE)-Based Architecture
Informative reference — RFC 8735: Scenarios and Simulation Results of PCE in a Native IP Network

Incoming relationships (1 related RFC)

Informatively referenced by — RFC 9689: Use Cases for a PCE as a Central Controller (PCECC)