Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

linchangwang <linchangwang.04414@h3c.com> Tue, 04 April 2023 07:00 UTC

Return-Path: <linchangwang.04414@h3c.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 47C1FC1516E0 for <rtg-bfd@ietfa.amsl.com>; Tue, 4 Apr 2023 00:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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=ham 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 C2cRam5AHVGu for <rtg-bfd@ietfa.amsl.com>; Tue, 4 Apr 2023 00:00:09 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (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 26B12C151547 for <rtg-bfd@ietf.org>; Tue, 4 Apr 2023 00:00:08 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 3346xULj098047; Tue, 4 Apr 2023 14:59:30 +0800 (GMT-8) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG2EX04-BASE.srv.huawei-3com.com (unknown [10.69.0.52]) by mail.maildlp.com (Postfix) with ESMTP id 769D82005949; Tue, 4 Apr 2023 15:03:34 +0800 (CST)
Received: from DAG2EX07-IDC.srv.huawei-3com.com (172.20.54.130) by DAG2EX04-BASE.srv.huawei-3com.com (10.69.0.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Tue, 4 Apr 2023 14:59:31 +0800
Received: from DAG2EX07-IDC.srv.huawei-3com.com ([::1]) by DAG2EX07-IDC.srv.huawei-3com.com ([fe80::fd0a:6e94:67d9:5ce8%10]) with mapi id 15.01.2507.006; Tue, 4 Apr 2023 14:59:31 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: JeffreyHaas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)
Thread-Topic: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)
Thread-Index: AdlmwvQU8OWHVn8H0kyI3sRKQbz3iA==
Date: Tue, 04 Apr 2023 06:59:31 +0000
Message-ID: <84454f62a53c4c859f704e919ebfb802@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.76.67]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_84454f62a53c4c859f704e919ebfb802h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 3346xULj098047
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/jAnmVrO275kN8OQ_uRp_2i32pTc>
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: Tue, 04 Apr 2023 07:00:12 -0000

Hi all,


I've read the document and believe it is ready for publication.

We have lots of deployments using BFD Echo,such as local protection for faster failure dection.
It would be greatly appreciated if this draft could be standardized ASAP!

Best Regards,
Changwang lin



Original
From: JeffreyHaas <jhaas@pfrc.org>
To: rtg-bfd@ietf.org <rtg-bfd@ietf.org>;
Date: 2023年03月22日 00:02
Subject: 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



-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
This e-mail and its attachments contain confidential information from New H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!