Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Obsoletes:

RFC 7752,RFC 9029

Author:

K. Talaulikar, Ed.

Stream:

IETF

Source:

idr (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9552

Discuss this RFC: Send questions or comments to the mailing listidr@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9552

Abstract

In many environments, a component external to a network is calledupon to perform computations based on the network topology and thecurrent state of the connections within the network, includingTraffic Engineering (TE) information. This is information typicallydistributed by IGP routing protocols within the network.

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

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

This document obsoletes RFC 7752 by completely replacing thatdocument. It makes some small changes and clarifications to theprevious specification. This document also obsoletes RFC 9029 byincorporating the updates that it made to RFC 7752.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.