Re: bfd - Not having a session at IETF 119

Jeffrey Haas <jhaas@pfrc.org> Sun, 04 February 2024 16:40 UTC

Return-Path: <jhaas@pfrc.org>
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 315FEC14F615 for <rtg-bfd@ietfa.amsl.com>; Sun, 4 Feb 2024 08:40:39 -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_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 CCVfbGmwqw37 for <rtg-bfd@ietfa.amsl.com>; Sun, 4 Feb 2024 08:40:38 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 19287C14F5FE for <rtg-bfd@ietf.org>; Sun, 4 Feb 2024 08:40:37 -0800 (PST)
Received: from smtpclient.apple (172-125-100-52.lightspeed.livnmi.sbcglobal.net [172.125.100.52]) by slice.pfrc.org (Postfix) with ESMTPSA id 41BD31E039; Sun, 4 Feb 2024 11:40:37 -0500 (EST)
From: Jeffrey Haas <jhaas@pfrc.org>
Message-Id: <CED96BE1-1845-4444-AD51-7F6F7DE04634@pfrc.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3E56DF72-1C5D-4FE4-BA1C-07A252438D4B"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\))
Date: Sun, 04 Feb 2024 11:40:36 -0500
Subject: Re: bfd - Not having a session at IETF 119
In-Reply-To: <170688747912.43637.8340251769833526797@ietfa.amsl.com>
To: "rtg-bfd@ietf. org" <rtg-bfd@ietf.org>
References: <170688747912.43637.8340251769833526797@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3696.120.41.1.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/U7h-YUqCNSlKEWEXwuWa-cUl0yk>
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: Sun, 04 Feb 2024 16:40:39 -0000

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 <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/ <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/ <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 <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 <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.
> 
>