BGP Bestpath Selection Criteria Enhancement
draft-ietf-idr-bgp-bestpath-selection-criteria-07
| Document | Type | Expired Internet-Draft (idr WG) | |
|---|---|---|---|
| Author | Rajiv Asati | ||
| Last updated | 2017-10-07 (Latest revision 2017-04-05) | ||
| Replaces | draft-asati-idr-bgp-bestpath-selection-criteria | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-idr-bgp-bestpath-selection-criteria-07.txt
Abstract
BGP specification (RFC4271) prescribes 'BGP next-hop reachability' as one of the key 'Route Resolvability Condition' that must be satisfied before the BGP bestpath candidate selection. This condition, however, may not be sufficient (as explained in the Appendix section) and desire further granularity. This document defines enhances the "Route Resolvability Condition" to facilitate the next-hop to be resolved in the chosen data plane.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)