metasystema.org
CurrentPROPOSED STANDARDIETF stream

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

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9552
Published
December 2023
Authors
K. Talaulikar
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
60
Also known as
—
Obsoletes:
RFC 7752, RFC 9029

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 7752 (2016)
  2. RFC 9029 (2021)
  3. RFC 9552 (2023)

Read the full history of Distribution of Link-State and Traffic Engineering Information Using BGP →

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9552-distribution-of-link-state-and-traffic-engineering-information-using-bgp