metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9552.

Current document in this lineage: RFC 9552 — Distribution of Link-State and Traffic Engineering Information Using BGP

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

In a number of environments, a component external to a network is called upon to perform computations based on the network topology and 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 new BGP Network Layer Reachability Information (NLRI) encoding format. The mechanism is applicable to physical and virtual 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).

Document record

Document ID
RFC7752
Published
March 2016
Authors
H. Gredler; J. Medved; S. Previdi; A. Farrel; S. Ray
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
48
Also known as
—
Obsoleted by:
RFC 9552
Updated by:
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 →

Referenced by

2 later RFCs formally update or obsolete part of this document.

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/7752-north-bound-distribution-of-link-state-and-traffic-engineering-te-information-us