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

Mach Chen <mach.chen@huawei.com> Thu, 06 August 2020 08:59 UTC

Return-Path: <mach.chen@huawei.com>
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 7662E3A105A for <rtg-bfd@ietfa.amsl.com>; Thu, 6 Aug 2020 01:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 OoMQbYW7RTrz for <rtg-bfd@ietfa.amsl.com>; Thu, 6 Aug 2020 01:59:50 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4AF03A1059 for <rtg-bfd@ietf.org>; Thu, 6 Aug 2020 01:59:49 -0700 (PDT)
Received: from lhreml731-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 87DD3D26A38CE64E546A for <rtg-bfd@ietf.org>; Thu, 6 Aug 2020 09:59:45 +0100 (IST)
Received: from lhreml731-chm.china.huawei.com (10.201.108.82) by lhreml731-chm.china.huawei.com (10.201.108.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 6 Aug 2020 09:59:45 +0100
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by lhreml731-chm.china.huawei.com (10.201.108.82) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Thu, 6 Aug 2020 09:59:45 +0100
Received: from DGGEML510-MBS.china.huawei.com ([169.254.3.246]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0487.000; Thu, 6 Aug 2020 16:58:27 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Jeffrey Haas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: RE: Adoption call for draft-cw-bfd-unaffiliated-echo (ending 16 August, 2020)
Thread-Topic: Adoption call for draft-cw-bfd-unaffiliated-echo (ending 16 August, 2020)
Thread-Index: AQHWal/X0WGDLji9UEiCbMCfWwkyKqkqyjzw
Date: Thu, 6 Aug 2020 08:58:27 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE297D7919F@dggeml510-mbs.china.huawei.com>
References: <20200804131549.GA31729@pfrc.org>
In-Reply-To: <20200804131549.GA31729@pfrc.org>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.140]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/LCL4T2pqpg5rOdARIkd9Ufk2GK4>
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: Thu, 06 Aug 2020 08:59:52 -0000

Hi Jeff,

I have read the draft, it's useful draft. I support the adoption.

Best regards,
Mach

> -----Original Message-----
> From: Rtg-bfd [mailto:rtg-bfd-bounces@ietf.org] On Behalf Of Jeffrey Haas
> Sent: Tuesday, August 4, 2020 9:16 PM
> 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