OSPF Strict-Mode for BFD
draft-ketant-lsr-ospf-bfd-strict-mode-03
Document | Type |
Replaced Internet-Draft
(lsr WG)
Expired & archived
|
|
---|---|---|---|
Authors | Ketan Talaulikar , Peter Psenak , Albert Fu , Rajesh Shetty | ||
Last updated | 2020-01-06 (Latest revision 2019-11-01) | ||
Replaced by | draft-ietf-lsr-ospf-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-lsr-ospf-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 the extensions to OSPF that enables a router and its neighbor to signal their intention to use Bidirectional Forwarding Detection (BFD) for their adjacency using link-local advertisement between them. The signaling of this BFD enablement, allows the router to block and not allow the establishment of adjacency with its neighbor router until a BFD session is successfully established between them. The document describes this OSPF "strict-mode" of BFD establishment as a prerequisite to adjacency formation.
Authors
Ketan Talaulikar
Peter Psenak
Albert Fu
Rajesh Shetty
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)