Skip to main content

BGP Bestpath Selection Criteria Enhancement
draft-ietf-idr-bgp-bestpath-selection-criteria-12

Document Type Expired Internet-Draft (idr WG)
Expired & archived
Author Rajiv Asati
Last updated 2020-01-10 (Latest revision 2019-06-05)
Replaces draft-asati-idr-bgp-bestpath-selection-criteria
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Awaiting Expert Review/Resolution of Issues Raised, Revised I-D Needed - Issue raised by AD, Other - see Comment Log
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 (None)
Responsible AD Alvaro Retana
Send notices to Susan Hares <shares@ndzh.com>, aretana.ietf@gmail.com

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)