Distribution of Link-State and Traffic Engineering Information Using BGP
draft-ketant-idr-rfc7752bis-01
| Document | Type |
Replaced Internet-Draft
(idr WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ketan Talaulikar , Hannes Gredler , Jan Medved , Stefano Previdi , Adrian Farrel , Saikat Ray | ||
| Last updated | 2019-09-02 (Latest revision 2019-07-08) | ||
| Replaced by | draft-ietf-idr-rfc7752bis | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-idr-rfc7752bis | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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).
Authors
Ketan Talaulikar
Hannes Gredler
Jan Medved
Stefano Previdi
Adrian Farrel
Saikat Ray
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)