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

Jeffrey Haas <> Tue, 04 August 2020 13:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B6D9D3A0B1C for <>; Tue, 4 Aug 2020 06:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dnA1E7hF-0sw for <>; Tue, 4 Aug 2020 06:04:26 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 6E3BE3A0B2F for <>; Tue, 4 Aug 2020 06:04:26 -0700 (PDT)
Received: by (Postfix, from userid 1001) id 911F01E2F9; Tue, 4 Aug 2020 09:15:49 -0400 (EDT)
Date: Tue, 4 Aug 2020 09:15:49 -0400
From: Jeffrey Haas <>
Subject: Adoption call for draft-cw-bfd-unaffiliated-echo (ending 16 August, 2020)
Message-ID: <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 04 Aug 2020 13:04:28 -0000

Working Group,

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