Technical Summary
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 information. This is information typically
distributed by IGP routing protocols within the network.
This document describes a mechanism by which links state and traffic
engineering 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).
Working Group Summary
The idr WG has had discussions and extensive reviews for several years.
There is strong consensus in publication.
Document Quality
The document has has extensive reviews in the idr WG for several years. There have been 7 implementations reported.
Implementation report: https://tools.ietf.org/html/draft-ietf-idr-ls-distribution-impl
Personnel
Document Shepherd: Jie Ding (jie.dong@huawei.com)
Responsible AD: Alvaro Retana (aretana@cisco.com)
RFC Editor Note
RFC Editor: a couple of late editorial changes.
1. Section 3.2.1.4: The last sentence ("The ASN...or IGP domain).") in the description of BGP-LS Identifier should be deleted.
2. Section 3.3.3: Change "with a link NLRI" to "with a prefix NLRI" in the first sentence.
3. Section 3.1: There's an extra "." right before the last sentence.