BGP BFD Strict-Mode
draft-ietf-idr-bgp-bfd-strict-mode-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Mercia Zheng , Acee Lindem , Jeffrey Haas , Albert Fu | ||
| Last updated | 2020-05-07 (Latest revision 2019-11-04) | ||
| Replaces | draft-merciaz-idr-bgp-bfd-strict-mode | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| 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:
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
Albert Fu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)