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

Jeffrey Haas <jhaas@pfrc.org> Mon, 17 August 2020 20:38 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F2CF3A10F4 for <rtg-bfd@ietfa.amsl.com>; Mon, 17 Aug 2020 13:38:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EWoq2iFuSKeN for <rtg-bfd@ietfa.amsl.com>; Mon, 17 Aug 2020 13:38:47 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id DB57B3A10E9 for <rtg-bfd@ietf.org>; Mon, 17 Aug 2020 13:38:47 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 147801E2FB; Mon, 17 Aug 2020 16:50:47 -0400 (EDT)
Date: Mon, 17 Aug 2020 16:50:46 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: rtg-bfd@ietf.org
Subject: Re: Adoption call for draft-cw-bfd-unaffiliated-echo (ending 16 August, 2020)
Message-ID: <20200817205046.GD1696@pfrc.org>
References: <20200804131549.GA31729@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200804131549.GA31729@pfrc.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/RmNYOWlZou66s51f60CzumR6uYw>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2020 20:38:49 -0000

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