Dear authors and BFD WG, Congratulations for the IESG approval of this draft! It took longer than expected, but it is now approved and will be published as an RFC in 2-3 months probably.
It was an interesting ride for me as the alternate AD ;-) Cheers -éric From: The IESG <[email protected]> Date: Wednesday, 11 December 2024 at 18:31 To: IETF-Announce <[email protected]> Cc: The IESG <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, Eric Vyncke (evyncke) <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]> Subject: Protocol Action: 'Unaffiliated Bidirectional Forwarding Detection (BFD) Echo' to Proposed Standard (draft-ietf-bfd-unaffiliated-echo-14.txt) The IESG has approved the following document: - 'Unaffiliated Bidirectional Forwarding Detection (BFD) Echo' (draft-ietf-bfd-unaffiliated-echo-14.txt) as Proposed Standard This document is the product of the Bidirectional Forwarding Detection Working Group. The IESG contact persons are Gunter Van de Velde, Jim Guichard, Éric Vyncke and John Scudder. A URL of this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/ Technical Summary Bidirectional Forwarding Detection (BFD) is a fault detection protocol that can quickly determine a communication failure between two forwarding engines. This document defines a use of the BFD Echo where the local system supports BFD but the adjacent system does not support BFD. BFD Control packet and its processing procedures can be executed over the BFD Echo port where the adjacent system only loops packets back to the local system. This document updates RFC 5880 by defining a new method of BFD Echo-Only without requiring an implementation to support the full BFD protocol. Working Group Summary The document has weak but positive Working Group consensus to advance. This is somewhat typical of documents progressing through BFD at this point. That said, the document has had a degree of strong review from the interested parties. There were several concerns from Greg Mirsky, which were replied to (notably about the intended status, please refer to the detailed shepherd's write-up). Document Quality While neither the I-D nor the shepherd's write-up mention implementations, Xiao listed some implementations in his reply to Adrian Farrel's RTG-directorate review at: https://mailarchive.ietf.org/arch/msg/rtg-dir/3AUX1d5_2wkA6M4D66NqSsrS5M4/ Personnel The Document Shepherd for this document is Jeffrey Haas. The Responsible Area Director is Éric Vyncke.
