BGP Topology Discovery Requirements
draft-ymbk-lsvr-discovery-req-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Randy Bush , Keyur Patel | ||
| Last updated | 2019-03-05 (Latest revision 2018-09-01) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
For wide scale routing protocols to build their topology and reachability databases they need link neighbor discovery, link encapsulation data, and layer two liveness. BGP-LS and its enhancements provide an API to present much of these data to BGP protocols, but do not actually collect these data. This document explores the needs and criteria for the data needed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)