BGP BFD Strict-Mode
draft-merciaz-idr-bgp-bfd-strict-mode-02
Document | Type |
Replaced Internet-Draft
(idr WG)
Expired & archived
|
|
---|---|---|---|
Authors | Mercia Zheng , Acee Lindem , Jeffrey Haas | ||
Last updated | 2019-09-17 (Latest revision 2019-07-07) | ||
Replaced by | draft-ietf-idr-bgp-bfd-strict-mode | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-idr-bgp-bfd-strict-mode | |
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:
Abstract
This document specifies extensions to RFC4271 BGP-4 that enable a BGP speaker to negotiate additional Bidirectional Forwarding Detection (BFD) extensions using a BGP capability. This BFD capability enables a BGP speaker to prevent a BGP session from being established until a BFD session is established. It is referred to as BGP BFD "strict- mode". BGP BFD strict-mode will be supported when both the local speaker and its remote peer are BFD strict-mode capable.
Authors
Mercia Zheng
Acee Lindem
Jeffrey Haas
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)