BGP Bestpath Selection Criteria Enhancement
draft-ietf-idr-bgp-bestpath-selection-criteria-08
| Document | Type | Expired Internet-Draft (idr WG) | |
|---|---|---|---|
| Last updated | 2018-04-19 (latest revision 2017-10-10) | ||
| Replaces | draft-asati-idr-bgp-bestpath-selection-criteria | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-idr-bgp-bestpath-selection-criteria-08.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
Rajiv Asati (rajiva@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)