Re: Adoption call for draft-cw-bfd-unaffiliated-echo (ending 16 August, 2020)

[Jeffrey Haas <[e-mail]>]

Authors,

We seem to have pretty clear consensus that this work is useful and should
be adopted by the BFD Working Group.

Please re-submit the document as draft-ietf-bfd-unaffiliated-echo.

There's also the start of good discussion on issues in the document.  Please
continue to address those.

-- Jeff

On Tue, Aug 04, 2020 at 09:15:49AM -0400, Jeffrey Haas wrote:
> 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