Re: Optimizing Authentication - periodic re-authentication

Jeffrey Haas <jhaas@pfrc.org> Wed, 31 January 2024 19:06 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 0D00CC14F5E7; Wed, 31 Jan 2024 11:06:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 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] 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 bV2Qm1Ne9-GO; Wed, 31 Jan 2024 11:06:48 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 893CAC14F69A; Wed, 31 Jan 2024 11:06:48 -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 8A6331E039; Wed, 31 Jan 2024 14:06:47 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_E6B584E6-BEF9-479D-BC63-20FA204BFC06"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\))
Subject: Re: Optimizing Authentication - periodic re-authentication
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <2A54BB75-B967-425C-B3B4-39A3A91BE4B0@yahoo.com>
Date: Wed, 31 Jan 2024 14:06:46 -0500
Cc: draft-ietf-bfd-optimizing-authentication@ietf.org, rtg-bfd@ietf.org
Message-Id: <9491CBCF-AAEA-4CF0-A07C-CB2E270EB125@pfrc.org>
References: <20240128202100.GA11839@pfrc.org> <2A54BB75-B967-425C-B3B4-39A3A91BE4B0@yahoo.com>
To: Reshad Rahman <reshad@yahoo.com>
X-Mailer: Apple Mail (2.3696.120.41.1.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/FsLhr9A0n5Nb3ll0Y3ufjunHaTE>
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: Wed, 31 Jan 2024 19:06:53 -0000

Reshad,

> On Jan 30, 2024, at 12:28 AM, Rahman <reshad@yahoo.com> wrote:
> 
> Jeff, good catch.
> 
> We can document both ways, ie we can let implementations decide which of the 2 methods below they prefer? Or is the concern that this will cause a DISCUSS?

Mahesh has proposed the fix for the next rev in this pull request:

https://github.com/bfd-wg/optimized-auth/pull/19/files <https://github.com/bfd-wg/optimized-auth/pull/19/files>

-- Jeff