Re: I-D Action: draft-ietf-bfd-rfc5880bis-01.txt
Jeffrey Haas <jhaas@pfrc.org> Fri, 19 June 2026 19:02 UTC
Return-Path: <jhaas@pfrc.org>
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 3BEF5104239B8 for <rtg-bfd@mail2.ietf.org>; Fri, 19 Jun 2026 12:02:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1781895736; bh=jp0T6QdeX1CRIo2hSf+6EJiHpILNPOM5fXTuX6OnQxU=; h=Date:Subject:To:References:From:In-Reply-To; b=bQ0R/tkYyPOOB6yC5pID3MJHCEOicdWICGpT30LlasboVIaECfPXD55Xm0HK/OR85 TEIFLDIvVyUkOFyTuH53S96ASg6pEm/NfVXs4yMOxhaK5AmHfap08lgHq9UKKWCflc CoiNYk7X6rCKoCTfQwPSMXpKRq9s6+nxQ+P5y1Uc=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=pfrc.org
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 9HfgaE13wKOT for <rtg-bfd@mail2.ietf.org>; Fri, 19 Jun 2026 12:02:14 -0700 (PDT)
Received: from prospero.pfrc.org (prospero.pfrc.org [72.60.64.110]) (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 00E8C1042388B for <rtg-bfd@ietf.org>; Fri, 19 Jun 2026 12:02:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pfrc.org; s=prospero20250622; t=1781895718; bh=jp0T6QdeX1CRIo2hSf+6EJiHpILNPOM5fXTuX6OnQxU=; h=Date:Subject:To:References:From:In-Reply-To:From; b=liCXw7vehy5mXl3Ijv/yVnCxYCVUMNqmicxcyxA4kPQz/MPX75Fcu7LMDhJyo+N1a NCzcC0qRI9U94MoMV5gFKkr8uUfWmOgUUmhOe/Uht94WmO+EznZ37m2WgMihqDhAMp O1EX9CwTIey41jgqVGTBPKacNj4mlcB6H9GyFk1JKmXFG7+LOnanLp3NyGtCEx64Hz aTQ4G/0XZz9qIjW1pP5VTOdab7ct9NWSOITwHXSd1qsLeloN/PyrfXc9nVIpFFQQYt 4XWpNM7AQnXi+FikoZEz85u0dc7FsbCOI2eGABbkKgNoy2YsoFEHTl0mqpoKnobvN7 fA2s9URnFa1yg==
Received: from [IPV6:2600:1702:80c0:8960:a31e:c382:81b1:ef48] (unknown [IPv6:2600:1702:80c0:8960:a31e:c382:81b1:ef48]) by prospero.pfrc.org (Postfix) with ESMTPSA id 69A3E80087; Fri, 19 Jun 2026 19:01:58 +0000 (UTC)
Content-Type: multipart/alternative; boundary="------------JFXtP907A6eiqR3LuhNTVKCE"
Message-ID: <a463f47d-3692-4bf8-9521-a49acef50ab2@pfrc.org>
Date: Fri, 19 Jun 2026 15:01:55 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: I-D Action: draft-ietf-bfd-rfc5880bis-01.txt
To: Alvaro Retana <aretana.ietf@gmail.com>, rtg-bfd@ietf.org
References: <178187704380.811376.3967572853345540884@dt-datatracker-f9b87776f-xzl65> <CAMMESsw2dr99mC5d-6CBomMVpnnm6W5j2gZJbmJCxedECTEioA@mail.gmail.com>
Content-Language: en-US
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <CAMMESsw2dr99mC5d-6CBomMVpnnm6W5j2gZJbmJCxedECTEioA@mail.gmail.com>
Message-ID-Hash: NRZMLRKYW2ONOFA34IHGV7C3JCFP7BIV
X-Message-ID-Hash: NRZMLRKYW2ONOFA34IHGV7C3JCFP7BIV
X-MailFrom: jhaas@pfrc.org
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
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/-M4Ht5u-BtnWXaXOcTrlgcJqOJA>
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>
Thanks, Alvaro. A full diff vs. RFC 5880 can be seen via this URL: https://author-tools.ietf.org/diff?url_1=https://www.rfc-editor.org/rfc/rfc5880.txt&url_2=https://www.ietf.org/archive/id/draft-ietf-bfd-rfc5880bis-01.txt&iddiff=1 One thing I'd like to suggest for the working group to think about for the bis to our base RFC 5880 is "meticulous" keying. We found when we were working on the cluster of recent BFD authentication features, "meticulous" was defined in a way that generated significant IESG discussion. The eventual resolution for this was the definition here: https://datatracker.ietf.org/doc/html/draft-ietf-bfd-secure-sequence-numbers-27#name-meticulous-keying "In this context, the term "meticulous" means that the Sequence number is incremented on every new packet which is sent.*"* -- Jeff On 6/19/26 09:54, Alvaro Retana wrote: > Hi! > > This version includes the following changes from version -00: > > (1) Added an implementation status section. > > (2) Incorporated the Verified Errata: > 2530 (https://errata.rfc-editor.org/eid2530/) > 6926 (https://errata.rfc-editor.org/eid6926/) > 7082 (https://errata.rfc-editor.org/eid7082/) > 7083 (https://errata.rfc-editor.org/eid7083/) > > Thanks! > > Alvaro. > > > On June 19, 2026 at 9:52:47 AM, internet-drafts@ietf.org > (internet-drafts@ietf.org) wrote: > >> Internet-Draft draft-ietf-bfd-rfc5880bis-01.txt is now available. It >> is a work >> item of the Bidirectional Forwarding Detection (BFD) WG of the IETF. >> >> Title: Bidirectional Forwarding Detection (BFD) >> Authors: Dave Katz >> Dave Ward >> Alvaro Retana >> Name: draft-ietf-bfd-rfc5880bis-01.txt >> Pages: 52 >> Dates: 2026-06-19 >> >> Abstract: >> >> This document describes a protocol intended to detect faults in the >> bidirectional path between two forwarding engines, including >> interfaces, data link(s), and to the extent possible the forwarding >> engines themselves, with potentially very low latency. It operates >> independently of media, data protocols, and routing protocols. >> >> This document obsoletes RFC 5880. >> >> The IETF datatracker status page for this Internet-Draft is: >> https://datatracker.ietf.org/doc/draft-ietf-bfd-rfc5880bis/ >> >> There is also an HTML version available at: >> https://www.ietf.org/archive/id/draft-ietf-bfd-rfc5880bis-01.html >> >> A diff from the previous version is available at: >> https://author-tools.ietf.org/iddiff?url2=draft-ietf-bfd-rfc5880bis-01 >> >> Internet-Drafts are also available by rsync at: >> rsync.ietf.org::internet-drafts >> >>
- I-D Action: draft-ietf-bfd-rfc5880bis-01.txt internet-drafts
- Re: I-D Action: draft-ietf-bfd-rfc5880bis-01.txt Alvaro Retana
- Re: I-D Action: draft-ietf-bfd-rfc5880bis-01.txt Jeffrey Haas