BGP Topology Discovery Requirements
draft-ymbk-lsvr-discovery-req-01
The information below is for an old version of the document.
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Randy Bush , Keyur Patel | ||
| Last updated | 2019-03-05 (Latest revision 2018-09-01) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-ymbk-lsvr-discovery-req-01.txt
https://www.ietf.org/archive/id/draft-ymbk-lsvr-discovery-req-01.txt
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.)