Path validation toward BGP next-hop with AUTO-BFD
draft-jdurand-auto-bfd-00

Document Type Expired Internet-Draft (candidate for idr WG)
Authors Jerome Durand  , David Freedman 
Last updated 2015-10-14 (latest revision 2015-03-09)
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-jdurand-auto-bfd-00.txt

Abstract

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.

Authors

Jerome Durand (jerduran@cisco.com)
David Freedman (david.freedman@uk.clara.net)

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