Hi All, I believe the WG should adopt this document since this is a very useful extension for BFD protocol in specific scenarios. While the document needs more details on the applicability, operational guidance and procedures, it does provide a very good starting point for the WG to address this topic/requirement.
I also believe that while the proposal may not involve new/updated encodings, it certainly describes modified protocol procedures and so likely belongs to standards track. I have a feeling that it might also end up updating RFC5880 as we go along. Thanks, Ketan -----Original Message----- From: Rtg-bfd <rtg-bfd-boun...@ietf.org> On Behalf Of Jeffrey Haas Sent: 04 August 2020 18:46 To: rtg-bfd@ietf.org Subject: Adoption call for draft-cw-bfd-unaffiliated-echo (ending 16 August, 2020) Working Group, https://datatracker.ietf.org/doc/draft-cw-bfd-unaffiliated-echo/ At the virtual IETF 108, Unaffiliated BFD Echo Function was presented. This is a followup of a presentation given at IETF 106. The authors have indicated they would like to have this work adopted by the BFD WG. This begins the adoption call ending August 16. Please respond to the mailing list with your thoughts on this adoption. It should be noted that this document overlaps work in the Broadband Forum (BBF) document TR-146. As noted in the presentation, the BBF document lacks some clarity and also doesn't discuss interactions with BFD implementations. This draft has good clarifications with regard to implementations of this mechanism when the a BFD Echo-capable implementation is used. This raises two points to consider as part of adoption: - This document with its current goals would Update RFC 5880. - The status of this document would need to be Proposed Standard. -- Jeff
