BGP BFD Strict-Mode
draft-merciaz-idr-bgp-bfd-strict-mode-02
| Document | Type | Replaced Internet-Draft (idr WG) | |
|---|---|---|---|
| Last updated | 2019-09-17 (latest revision 2019-07-07) | ||
| Replaced by | draft-ietf-idr-bgp-bfd-strict-mode | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-idr-bgp-bfd-strict-mode | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-merciaz-idr-bgp-bfd-strict-mode-02.txt
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
(merciaz@cisco.com)
Acee Lindem
(acee@cisco.com)
Jeffrey Haas
(jhaas@juniper.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)