Re: I-D Action: draft-ietf-bfd-rfc5883-bis-00.txt

xiao.min2@zte.com.cn Mon, 15 June 2026 06:22 UTC

Return-Path: <xiao.min2@zte.com.cn>
X-Original-To: rtg-bfd@mail2.ietf.org
Delivered-To: rtg-bfd@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 8DF2510157A5F for <rtg-bfd@mail2.ietf.org>; Sun, 14 Jun 2026 23:22:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1781504562; bh=lVlvYfPSIGVwnYl3PygK+gyzo7HT5CiQwierAgG/6JA=; h=In-Reply-To:References:Date:From:To:Cc:Subject; b=A+cSVvbPmaH2TCUlTTOGd+rkyDqtn1C0t5Id3QVXro5LcNNzl3fvL0lDoAhkpt00x kwU2CfuoKMPAEQPvpx1nXKwZgEtdYoWLBDO3MeeYmfItThbURS4n6qztoWdnizSbh2 QSDsUEQTXks+hJNE8P3l0nw4AVRKTlZ5SAjBWSeQ=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qp64_R0LjAHJ for <rtg-bfd@mail2.ietf.org>; Sun, 14 Jun 2026 23:22:41 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [160.30.148.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id ED92F10157841 for <rtg-bfd@ietf.org>; Sun, 14 Jun 2026 23:20:13 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4gf0N561mNz5B1KR; Mon, 15 Jun 2026 14:20:05 +0800 (CST)
Received: from njb2app07.zte.com.cn ([10.55.22.95]) by mse-fl1.zte.com.cn with SMTP id 65F6Jx1q017193; Mon, 15 Jun 2026 14:19:59 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njb2app06[null]) by mapi (Zmail) with MAPI id mid201; Mon, 15 Jun 2026 14:20:01 +0800 (CST)
X-Zmail-TransId: 2afe6a2f9991eec-2ef45
X-Mailer: Zmail v1.0
Message-ID: <20260615142001501bxOV2rEy72Gt9IaLJJ_Ak@zte.com.cn>
In-Reply-To: <171181728.1163985.1781455975978@mail.yahoo.com>
References: 20260610152407367p5G6lSd6pycgZgN88eKg5@zte.com.cn,171181728.1163985.1781455975978@mail.yahoo.com
Date: Mon, 15 Jun 2026 14:20:01 +0800
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: reshad@yahoo.com
Subject: Re: I-D Action: draft-ietf-bfd-rfc5883-bis-00.txt
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 65F6Jx1q017193
X-TLS: YES
X-ENVELOPE-SENDER: xiao.min2@zte.com.cn
X-SOURCE-IP: 10.5.228.132 unknown Mon, 15 Jun 2026 14:20:05 +0800
X-CLEAN: YES
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 6A2F9995.001/4gf0N561mNz5B1KR
Message-ID-Hash: KZ32PH6U3X3UFVTZ5FY6HUQWD5SBC4NU
X-Message-ID-Hash: KZ32PH6U3X3UFVTZ5FY6HUQWD5SBC4NU
X-MailFrom: xiao.min2@zte.com.cn
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtg-bfd.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rtg-bfd@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection" <rtg-bfd.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/YhupmBN334Icjc0d2tPlaq7XSt4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Owner: <mailto:rtg-bfd-owner@ietf.org>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Subscribe: <mailto:rtg-bfd-join@ietf.org>
List-Unsubscribe: <mailto:rtg-bfd-leave@ietf.org>

Hi Reshad,

Many thanks for your review and comments.
Please see inline.


Original


From: ReshadRahman <reshad@yahoo.com>
  
To: rtg-bfd@ietf.org <rtg-bfd@ietf.org>;肖敏10093570;
  
Date: 2026年06月15日 00:53
  
Subject: Re: I-D Action: draft-ietf-bfd-rfc5883-bis-00.txt
  




Hi Xiao Min,

Thank you for taking this on.

2 comments/questions:
1) There is no TOC (and neither did RFC5883), I'm assuming because it's a small document.
[XM]>>> Yes, that's done on purpose.

2) I believe you should reference RFC8174 too (as e.g. 5880-bis does).
[XM]>>> You're correct. I'll update Section 1.1 of both rfc5883bis and rfc5882bis to the latest template including the reference to RFC8174.

Cheers,
Xiao Min

Regards,
Reshad.



On Wednesday, June 10, 2026 at 03:24:37 AM EDT, xiao.min2@zte.com.cn <xiao.min2@zte.com.cn> wrote:





Dear all,

I'm the assigned editor for rfc5883bis which is intended to be progressed to an Internet Standard.
This is the 00 version wg draft, which is almost the same to rfc5883. The diff link is as below.
https://author-tools.ietf.org/iddiff?url1=rfc5883&url2=draft-ietf-bfd-rfc5883-bis-00&difftype=--html
The major change is to add Section 9 "Implementation Status", which will be removed before publication.
In this version only the ZTE's implementation report is recorded, and the feature granularity is on each MUST/SHOULD/MAY statement.
As required by RFC 6410, one criterion for Internet Standard is "at least two independent interoperating implementations with widespread deployment and successful operational experience", so the implementation reports should be as more as possible. If you have an implementation report to share, please send it to the wg chairs and me, or you may send it to the list.
As requested by Jeff, this draft has also been uploaded to GitHub: https://github.com/bfd-wg/draft-ietf-bfd-rfc5883-bis.
Much appreciate your review and comments.

Best Regards,
Xiao Min


Original



From: internet-drafts@ietf.org <internet-drafts@ietf.org>      
To: i-d-announce@ietf.org <i-d-announce@ietf.org>;      
Cc: rtg-bfd@ietf.org <rtg-bfd@ietf.org>;
Date: 2026年06月08日 20:39      
Subject: I-D Action: draft-ietf-bfd-rfc5883-bis-00.txt      


Internet-Draft draft-ietf-bfd-rfc5883-bis-00.txt is now available. It is awork item of the Bidirectional Forwarding Detection (BFD) WG of the IETF.    Title:   Bidirectional Forwarding Detection (BFD) for Multihop Paths   Authors: Dave Katz            Dave Ward            Xiao Min   Name:    draft-ietf-bfd-rfc5883-bis-00.txt   Pages:   8   Dates:   2026-06-08 Abstract:    This document describes the use of the Bidirectional Forwarding   Detection (BFD) protocol over multihop paths, including   unidirectional links.    This document obsoletes RFC 5883. The IETF datatracker status page for this Internet-Draft is:https://datatracker.ietf.org/doc/draft-ietf-bfd-rfc5883-bis/ There is also an HTMLized version available at:https://datatracker.ietf.org/doc/html/draft-ietf-bfd-rfc5883-bis-00 Internet-Drafts are also available by rsync at:rsync.ietf.org::internet-drafts