Hi Robert,
This is great to hear – I thought you wanted to make this required for
implementation as opposed to a recommendation.
Thanks,
Acee
From: Robert Raszuk
Date: Thursday, February 10, 2022 at 10:57 AM
To: Acee Lindem
Cc: "lsr@ietf.org" ,
"draft-ietf-lsr-ospf-bfd-strict-m...@ietf.org"
Hi Acee,
> There was debate regarding making the delay timer described in section 5
a normative requirement.
I see added into new version of the draft the following text into section
5:
The use of OSPF BFD strict-
mode along with mechanisms such as hold-down
*(a delay in the initial
Acee Lindem has requested publication of draft-ietf-lsr-ospf-bfd-strict-mode-05
as Proposed Standard on behalf of the LSR working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-bfd-strict-mode/
___
The WG last call has all but ended and we’ve had a lot of support, two
implementations, and some good discussion. Please review the -05 version of the
draft reflecting including changes reflecting this discussion. There was debate
regarding making the delay timer described in section 5 a
Hi Aijun,
A BFD session and/or neighborship going down between two DRother routers
does not impact the topology since there is no change in the Network LSA
for that LAN advertised by the DR. However, in the common scenario where a
DRother router goes down, a BFD session does help another DRother
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Link State Routing WG of the IETF.
Title : OSPF BFD Strict-Mode
Authors : Ketan Talaulikar
Peter Psenak
