North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 48
- Abstract
- 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).
- Publication Date
- 2016-03-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC7752- Link
- https://doi.org/10.17487/RFC7752
- Author(s)
- Hannes GredlerJan MedvedStefano PrevidiAdrian FarrelSaikat Ray
- Keyword(s)
- BGP, North-Bound, API, Link-State, Topology, Controller, Multi-Area, Multi-AS
Latest version of IETF RFC 7752
Document Versions — IETF RFC 7752
-
▶ IETF RFC 7752 (2016-03-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Superseded by:
- RFC9552 NOT IN REGISTRY
Amended by:
- RFC9029 NOT IN REGISTRY
Normative Reference(s)
- ISO.10589 — 14 EXTERNAL
- IETF RFC 2119 [Active*]
- IETF RFC 2328 [Active*]
- IETF RFC 2545 [Active*]
- IETF RFC 3209 [Active*]
- RFC4202 — GMPLS-ROUTING EXTERNAL
- IETF RFC 4203 [Active*]
- IETF RFC 4271 [Active*]
- RFC4760 — RFC4760 EXTERNAL
- RFC4915 — RFC4915 EXTERNAL
- RFC5036 — RFC5036 EXTERNAL
- RFC5120 — RFC5120 EXTERNAL
- RFC5130 — RFC5130 EXTERNAL
- IETF RFC 5226 [Superseded*]
- RFC5301 — RFC5301 EXTERNAL
- RFC5305 — RFC5305 EXTERNAL
- RFC5307 — RFC5307 EXTERNAL
- IETF RFC 5340 [Active*]
- IETF RFC 5890 [Active*]
- RFC6119 — RFC6119 EXTERNAL
- RFC6549 — RFC6549 EXTERNAL
- RFC6822 — RFC6822 EXTERNAL
- RFC7606 — RFC7606 EXTERNAL
Bibliographic Reference(s)
- IETF RFC 1918 [Active*]
- IETF RFC 4272 [Active*]
- IETF RFC 4364 [Active*]
- RFC4655 — RFC4655 EXTERNAL
- RFC5073 — RFC5073 EXTERNAL
- RFC5152 — RFC5152 EXTERNAL
- RFC5316 — RFC5316 EXTERNAL
- RFC5392 — RFC5392 EXTERNAL
- RFC5693 — RFC5693 EXTERNAL
- RFC5706 — RFC5706 EXTERNAL
- RFC6952 — RFC6952 EXTERNAL
- RFC7285 — RFC7285 EXTERNAL
- RFC7770 — RFC7770 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7752.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7752, North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP. Available at https://doi.org/10.17487/RFC7752
Snippet:
IETF RFC 7752, North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP. Available at https://doi.org/10.17487/RFC7752
HTML (ISO 690 compliant)
Preview:
IETF RFC 7752, North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP. Available at https://doi.org/10.17487/RFC7752
Snippet:
<span class="citation"><cite>IETF RFC 7752</cite>, North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP. Available at <a href="https://doi.org/10.17487/RFC7752" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7752</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7752, North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
doi: 10.17487/RFC7752
url: https://doi.org/10.17487/RFC7752
doi: 10.17487/RFC7752
url: https://doi.org/10.17487/RFC7752
Snippet:
<li> <cite id="bib-rfc7752">IETF RFC 7752</cite>, North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP <span class="doi">10.17487/RFC7752</span> </li>
Referenced By
- IETF RFC 8126 [Active*]