BGP Bestpath Selection Criteria Enhancement
draft-ietf-idr-bgp-bestpath-selection-criteria-12
| Document | Type | Expired Internet-Draft (idr WG) | |
|---|---|---|---|
| Author | Rajiv Asati | ||
| Last updated | 2020-01-10 (latest revision 2019-06-05) | ||
| Replaces | draft-asati-idr-bgp-bestpath-selection-criteria | ||
| Stream | Internent Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | Susan Hares | ||
| Shepherd write-up | Show (last changed 2019-06-07) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Alvaro Retana | ||
| Send notices to | Susan Hares <shares@ndzh.com>, aretana.ietf@gmail.com | ||
https://www.ietf.org/archive/id/draft-ietf-idr-bgp-bestpath-selection-criteria-12.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 would 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.)