Skip to main content

Path validation toward BGP next-hop with AUTO-BFD

Document Type Expired Internet-Draft (candidate for idr WG)
Expired & archived
Authors Jerome Durand , David Freedman
Last updated 2015-10-14 (Latest revision 2015-03-09)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
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:


This document describes a solution called AUTO-BFD, that automatically initiates BFD sessions for BGP next-hops. This makes it possible to avoid blackholing scenarios when a BGP peer is not the BGP next-hop, especially on Internet eXchange Points (IXPs) when BGP Route-Servers are deployed. When they are configured with this mechanism, routers can automatically try to establish a new adjacency for every new BGP next-hop. BGP routes are then checked against the state of the BFD session for the corresponding next-hop. Foreword A placeholder to list general observations about this document.


Jerome Durand
David Freedman

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