Re： WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)
Yisong Liu <liuyisong@chinamobile.com> Fri, 07 April 2023 13:48 UTC
Return-Path: <liuyisong@chinamobile.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 A818FC15C29E for <rtg-bfd@ietfa.amsl.com>; Fri, 7 Apr 2023 06:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.605
X-Spam-Level:
X-Spam-Status: No, score=0.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.001, HDRS_MISSP=2.499, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tlcy3gTRxYhR for <rtg-bfd@ietfa.amsl.com>; Fri, 7 Apr 2023 06:48:08 -0700 (PDT)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 4219FC151B12 for <rtg-bfd@ietf.org>; Fri, 7 Apr 2023 06:48:07 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.5]) by rmmx-syy-dmz-app12-12012 (RichMail) with SMTP id 2eec64301f11558-6d322; Fri, 07 Apr 2023 21:48:02 +0800 (CST)
X-RM-TRANSID: 2eec64301f11558-6d322
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from CMCC-PC (unknown[222.129.54.1]) by rmsmtp-syy-appsvr03-12003 (RichMail) with SMTP id 2ee364301f11926-a3dfc; Fri, 07 Apr 2023 21:48:02 +0800 (CST)
X-RM-TRANSID: 2ee364301f11926-a3dfc
MIME-Version: 1.0
x-PcFlag: 23bcbff7-f968-48f1-b659-d8c249fb548e_5_130205
X-Mailer: PC_RICHMAIL 2.9.23
Date: Fri, 07 Apr 2023 21:48:02 +0800
From: Yisong Liu <liuyisong@chinamobile.com>
To: Jeffrey Haas <jhaas@pfrc.org>, rtg-bfd <rtg-bfd@ietf.org>
Subject: Re： WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)
Message-ID: <202304072148022813136068@chinamobile.com>
Content-Type: multipart/Alternative; boundary="----=_001_NextPart-1481831228_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/dgzvaqYGul-ERO-D3pC_VUp1NQU>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 07 Apr 2023 13:48:12 -0000
Hi WG， I have read the document and support the publication. Best Regards Yisong 发件人: Jeffrey Haas 时间: 2023/03/22(星期三)00:02 收件人: rtg-bfd; 主题: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)Working Group, https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/05/ The authors of draft-ietf-bfd-unaffiliated-echo have requested WGLC. The draft, in my opinion, is in fairly good shape. However, since it functions via looping packets back to itself and trying to exercise the normal RFC 5880 state machine behaviors to a large extent, the draft could use very high scrutiny for several matters: - Does the state machine behave appropriately at all stages? - Are the descriptions of the values of the BFD fields clear in all cases? Please supply the authors and the Working Group with your feedback. The intended finish date for this WGLC is 7 April, 2023. This is one week after the end of IETF 116. Note that Reshad is an author on the draft, so I'll be handling the full set of review and shepherding work. -- Jeff