Skip to main content

OSPF Bidirectional Forwarding Detection (BFD) Strict-Mode
draft-ietf-lsr-ospf-bfd-strict-mode-10

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, acee@cisco.com, draft-ietf-lsr-ospf-bfd-strict-mode@ietf.org, jgs@juniper.net, lsr-chairs@ietf.org, lsr@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'OSPF BFD Strict-Mode' to Proposed Standard (draft-ietf-lsr-ospf-bfd-strict-mode-10.txt)

The IESG has approved the following document:
- 'OSPF BFD Strict-Mode'
  (draft-ietf-lsr-ospf-bfd-strict-mode-10.txt) as Proposed Standard

This document is the product of the Link State Routing Working Group.

The IESG contact persons are Alvaro Retana, Andrew Alston and John Scudder.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-bfd-strict-mode/


Ballot Text

Technical Summary

This document provides extensions to OSPF to require a BFD session (i.e.,
strict-mode) prior to OSPF adjacency formation. Extensions are provided both
OSPF Link-Local-Signaling to advertise the desire to require a BFD session and
to the OSPF neighbor FSM should BFD strict-mode be successfully negotiated.

Working Group Summary

There is stong support among those reviewing the document. The WG last call of
the document prompted discussions of additional specification. There was debate
regarding making the delay timer described in section 5 a normative
requirement. The consensus was to not make this a normative part of the
specification. The shepherd felt this is the right decision – especially given that this
is new functionality being requested at Working Group Last Call and
implementations accomplish the dampening in varying ways.

Document Quality

The document is of high quality and has been reviewed by several LSR WG
members. This same function is already standardized for IS-IS [RFC6213]

Personnel

 Document Shepherd: Acee Lindem
 Responsible AD: John Scudder

RFC Editor Note