IETF Logo Mail Archive

Re: draft-ietf-bfd-optimizing-authentication-13 nits

Jeffrey Haas <jhaas@pfrc.org> Mon, 22 January 2024 14:02 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 324CAC14CEFD; Mon, 22 Jan 2024 06:02:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 brfDeHUccqLu; Mon, 22 Jan 2024 06:02:50 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 66629C14CEF9; Mon, 22 Jan 2024 06:02:49 -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 D47D81E039; Mon, 22 Jan 2024 09:02:48 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_753EA260-376A-4E81-9CC2-104D9CE0FF02"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\))
Subject: Re: draft-ietf-bfd-optimizing-authentication-13 nits
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <5EE1006F-0CA6-4D63-9E8A-B7CDB2B7B124@pfrc.org>
Date: Mon, 22 Jan 2024 09:02:48 -0500
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, "rtg-bfd@ietf. org" <rtg-bfd@ietf.org>, draft-ietf-bfd-optimizing-authentication@ietf.org, Ashesh Mishra <mishra.ashesh@gmail.com>
Message-Id: <B89CC55B-1A9E-45E4-8706-01A9E3DBCDA4@pfrc.org>
References: <B49A64C7-731F-4729-9D99-AC6C133983C8@deployingradius.com> <F9A30ECC-28E1-4272-A23F-191310424E0F@pfrc.org> <A9091D9D-1F6F-4AB7-BAD6-04229B0F3EFF@deployingradius.com> <5EE1006F-0CA6-4D63-9E8A-B7CDB2B7B124@pfrc.org>
To: Alan DeKok <aland@deployingradius.com>
X-Mailer: Apple Mail (2.3696.120.41.1.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/zYAcyo7UZpxq_QFyCQw1vwjL41s>
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, 22 Jan 2024 14:02:53 -0000

Correction for the pedants on the list. :-)

> On Jan 21, 2024, at 3:37 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:
> 
> 
> A reasonable procedure for an implementation of ISAAC is verifying that the contents do not vary.  For the BFD state machinery, any changes to those fields is expected to be accomplished through a poll sequence, unless we're going Down/AdminDown, in which case we're also wanting strong authentication.

Several changes to BFD states DO NOT require a poll sequence and can simply be done without coordination.  My memory on this detail were incorrect.

However, authentication still needs to pass in order for it to do so.

-- Jeff

v2.23.0 | Report a Bug | By Email