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

Yisong Liu <> Wed, 12 August 2020 08:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E8C723A1124; Wed, 12 Aug 2020 01:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.329
X-Spam-Status: No, score=-1.329 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.001, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FRDREwk2XYIY; Wed, 12 Aug 2020 01:05:05 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E726A3A112A; Wed, 12 Aug 2020 01:04:58 -0700 (PDT)
Received: from (unknown[]) by rmmx-syy-dmz-app03-12003 (RichMail) with SMTP id 2ee35f33a28657c-35ab1; Wed, 12 Aug 2020 16:04:22 +0800 (CST)
X-RM-TRANSID: 2ee35f33a28657c-35ab1
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from LAPTOP-5GS3BPC8 (unknown[]) by rmsmtp-syy-appsvr01-12001 (RichMail) with SMTP id 2ee15f33a283ac9-4c0ab; Wed, 12 Aug 2020 16:04:22 +0800 (CST)
X-RM-TRANSID: 2ee15f33a283ac9-4c0ab
MIME-Version: 1.0
x-PcFlag: 098717aa-c080-4f45-9a57-924a171af3e0_5_12369
X-Mailer: PC_RICHMAIL 2.8.2
Date: 12 Aug 2020 16:04:20 +0800
From: =?utf-8?B?WWlzb25nIExpdQ==?=<>
To: rtg-bfd-bounces<>, rtg-bfd<>
Subject: Re: Adoption call for draft-cw-bfd-unaffiliated-echo (ending 16 August, 2020)
Content-Type: multipart/Alternative; boundary="----=_001_NextPart25035648_=----"
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: Wed, 12 Aug 2020 08:05:07 -0000

Hi all

I support the adoption of the draft.



-----邮件原件-----发件人: Rtg-bfd [] 代表 Jeffrey Haas
发送时间: 2020年8月4日 21:16
主题: Adoption call for draft-cw-bfd-unaffiliated-echo (ending 16 August,

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