Skip to main content

Distribution of Link-State and Traffic Engineering Information Using BGP
RFC 9552

Revision differences

Document history

Date By Action
2024-01-31
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2024-01-30
(System) Received changes through RFC Editor sync (added Errata tag)
2024-01-24
(System) Set authors from rev 17 of draft-ietf-idr-rfc7752bis: Ketan Talaulikar
2023-12-22
(System) IANA registries were updated to include RFC9552
2023-12-22
(System)
Received changes through RFC Editor sync (created document RFC 9552, created became rfc relationship between draft-ietf-idr-rfc7752bis and RFC 9552, set abstract to 'In …
Received changes through RFC Editor sync (created document RFC 9552, created became rfc relationship between draft-ietf-idr-rfc7752bis and RFC 9552, set abstract to 'In many environments, a component external to a network is called upon to perform computations based on the network topology and the current state of the connections within the network, including Traffic Engineering (TE) information. This is information typically distributed by IGP routing protocols within the network.

This document describes a mechanism by which link-state and TE information can be collected from networks and shared with external components using the BGP routing protocol. This is achieved using a BGP Network Layer Reachability Information (NLRI) encoding format. The mechanism applies to physical and virtual (e.g., tunnel) IGP links. The mechanism described is subject to policy control.

Applications of this technique include Application-Layer Traffic Optimization (ALTO) servers and Path Computation Elements (PCEs).

This document obsoletes RFC 7752 by completely replacing that document. It makes some small changes and clarifications to the previous specification. This document also obsoletes RFC 9029 by incorporating the updates that it made to RFC 7752.', set pages to 60, set standardization level to Proposed Standard, added RFC published event at 2023-12-22, created obsoletes relation between RFC 9552 and RFC 7752, created obsoletes relation between RFC 9552 and RFC 9029)
2023-12-22
(System) RFC published