Re: bfd - Not having a session at IETF 119

xiao.min2@zte.com.cn Mon, 05 February 2024 06:13 UTC

Return-Path: <xiao.min2@zte.com.cn>
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 2161FC14F5F8 for <rtg-bfd@ietfa.amsl.com>; Sun, 4 Feb 2024 22:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=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 dQqaL9ecsUyE for <rtg-bfd@ietfa.amsl.com>; Sun, 4 Feb 2024 22:13:08 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DEC5C14F5FF for <rtg-bfd@ietf.org>; Sun, 4 Feb 2024 22:13:07 -0800 (PST)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4TSwzN48B7z4xPYc; Mon, 5 Feb 2024 14:13:04 +0800 (CST)
Received: from njy2app01.zte.com.cn ([10.40.12.136]) by mse-fl1.zte.com.cn with SMTP id 4156CunY028934; Mon, 5 Feb 2024 14:12:56 +0800 (+08) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njb2app06[null]) by mapi (Zmail) with MAPI id mid201; Mon, 5 Feb 2024 14:12:58 +0800 (CST)
Date: Mon, 05 Feb 2024 14:12:58 +0800
X-Zmail-TransId: 2afe65c07c6afffffffff14-52bb6
X-Mailer: Zmail v1.0
Message-ID: <202402051412589189481@zte.com.cn>
In-Reply-To: <CED96BE1-1845-4444-AD51-7F6F7DE04634@pfrc.org>
References: 170688747912.43637.8340251769833526797@ietfa.amsl.com, CED96BE1-1845-4444-AD51-7F6F7DE04634@pfrc.org
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: jhaas@pfrc.org
Cc: rtg-bfd@ietf.org
Subject: Re: bfd - Not having a session at IETF 119
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 4156CunY028934
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 65C07C70.000/4TSwzN48B7z4xPYc
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/9WgKjN5Pi42Ks5NfNe3wGU9NGfU>
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: Mon, 05 Feb 2024 06:13:13 -0000

Hi Jeff, Reshad,

Thanks for the great summary!
Just one small update to the wiki, the title of draft-ietf-bfd-unaffiliated-echo has been changed from "Unaffiliated BFD Echo Function" to "Unaffiliated BFD Echo" since -03 version.
Cheers,
Xiao Min

Original


From: JeffreyHaas <jhaas@pfrc.org>
To: rtg-bfd@ietf. <rtg-bfd@ietf.org>;
Date: 2024年02月05日 00:40
Subject: Re: bfd - Not having a session at IETF 119

While the session request tool downgraded our area director into one of the chairs, it's our intention to not meet at the upcoming IETF 119 in Brisbane.
Current status of the working group is on the wiki:
https://wiki.ietf.org/en/group/bfd

It's our hope that prior to IETF 119 we'll have fully updated and ready for last call versions of:
draft-ietf-bfd-optimizing-authentication
draft-ietf-bfd-secure-sequence-numbers
draft-ietf-bfd-stability

Once those documents have been re-issued, we'll be asking for directorate review for them.

draft-ietf-bfd-unaffiliated-echo has been submitted for publication by the IESG and we're waiting on that process.

draft-ietf-bfd-large-packets has been refreshed, has an implementation at Juniper and was recently updated to add a YANG module covering its behavior.  The authors (including myself) are in discussions with Xiao Min to see if his recent proposal is an appropriate fit to be incorporated in this draft in some fashion, or whether to keep it as a separate draft.

In non-bfd WG news, RFC 9521 came out for BFD for Geneve.  Congratulations to the authors!

BFD for BIER is apparently ready for WGLC:
https://mailarchive.ietf.org/arch/msg/bier/j5czUxHaqJRcmnrYxe8RfqEGUm0/

draft-ietf-spring-bfd appears to be ready for WGLC:
https://mailarchive.ietf.org/arch/msg/spring/qg3anN8M8Ks-rjkpJ6pXqmyjrw4/

This bit of work in the MPLS WG has impacts on RFC 5884, BFD for MPLS LSPs:
https://datatracker.ietf.org/doc/html/draft-ietf-mpls-lspping-norao-06

Greg has raised issues covering RFC 5884 in MPLS.  The chairs believe if any work needs to be done, it's best done as a -bis to RFC 5884 in BFD:
https://mailarchive.ietf.org/arch/browse/mpls/?q=draft-mirsky-mpls-bfd-bootstrap-clarify

If I've missed anything else, please let the chairs know and we'll get the wiki updated.

-- Jeff and Reshad


On Feb 2, 2024, at 10:24 AM, IETF Meeting Session Request Tool <session-request@ietf.org> wrote:


John Scudder, a chair of the bfd working group, indicated that the bfd working group does not plan to hold a session at IETF 119.This message was generated and sent by the IETF Meeting Session Request Tool.