BGP Topology Discovery Requirements
draft-ymbk-lsvr-discovery-req-03
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Randy Bush , Keyur Patel | ||
Last updated | 2020-04-23 (Latest revision 2019-10-21) | ||
RFC stream | (None) | ||
Intended RFC status | (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 to discover the encapsulation data on a link, link IP layer 3 attributes, attributes for IP layer 3 and above protocols on that link, and link liveness. We refer to this as neighbor discovery. BGP-LS and its enhancements provide an API to present much of these data to BGP protocols, but do not directly 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.)