RFC 7926: Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks

In Traffic-Engineered (TE) systems, it is sometimes desirable to establish an end-to-end TE path with a set of constraints (such as bandwidth) across one or…

Read RFC 7926 on the RFC Editor

Outgoing relationships (1 related RFC)

Informative reference — RFC 6071: IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap

Incoming relationships (5 related RFCs)

Normatively referenced by — RFC 8795: YANG Data Model for Traffic Engineering (TE) Topologies
Informatively referenced by — RFC 9543: A Framework for Network Slices in Networks Built from IETF Technologies
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
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 9125: Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment Routing