IETF Logo Mail Archive

Re: [Emu] New Version Notification for draft-janfred-eap-fido-02.txt

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 05 March 2024 19:11 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B70FC1519A2 for <emu@ietfa.amsl.com>; Tue, 5 Mar 2024 11:11:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 O2ONYYeWUUg3 for <emu@ietfa.amsl.com>; Tue, 5 Mar 2024 11:11:14 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00700C15199C for <emu@ietf.org>; Tue, 5 Mar 2024 11:11:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 063B038993; Tue, 5 Mar 2024 14:11:13 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id NR0Q3s6bBzG1; Tue, 5 Mar 2024 14:11:10 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C488838991; Tue, 5 Mar 2024 14:11:10 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1709665870; bh=urA/6Qg6mzTwz4AtLNrS4Tt3UoluskVaDGT4MVHlMR8=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=Wz/Nj3unVnaIi6T5290b9mnEuUgXNMv2CvS51Y554tN/oQwzwA2kfJqx7oueQMpqv hGzziLmb8nSyCPS1E0O8vwI1q2+6ekzhbZ4lO0Mb7B5etbJ5iOnGQzqb2RQ0doLqQ0 UX4PsXRGGSZ5Oc/EseIbCUI4SNlXqCAE2Jm3QtK1kkiYMLL2HoZNh0eGQ12UgNjxaR TB5UrxXrnvdnaFQST/9/JYDaoVFrz/CYe6rm0qTwNb3Z51hw9r4mySZzQKGv2DSBAU tBeWR464DB5+kF4/BoRfKnBXRk15zUTHHPEhiZsbmBX4jUgJADAiDJT2DHq5EMUt5Z i/2lxS5jn454A==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C081D735; Tue, 5 Mar 2024 14:11:10 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alan DeKok <aland@deployingradius.com>
cc: Jan-Frederik Rieckers <rieckers@uni-bremen.de>, emu@ietf.org
In-Reply-To: <1865CE66-3B4F-4A10-96BC-49CEE9E0D78C@deployingradius.com>
References: <170932527085.22824.18343512124707075119@ietfa.amsl.com> <66bca1b2-4b2d-429d-8f85-5c76d29005ad@dfn.de> <c2951f3d-bcc7-4b90-bcdd-077a506dd464@app.fastmail.com> <523cd040-7485-4968-8367-4a6c274a284c@uni-bremen.de> <1865CE66-3B4F-4A10-96BC-49CEE9E0D78C@deployingradius.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 05 Mar 2024 14:11:10 -0500
Message-ID: <5425.1709665870@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/k0_kqetefOd15HhrQtKsMpw9NzA>
Subject: Re: [Emu] New Version Notification for draft-janfred-eap-fido-02.txt
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Mar 2024 19:11:18 -0000

Alan DeKok <aland@deployingradius.com> wrote:
    >   ALPN would be much simpler, I think.  The downside there is that
    > every time you rev the protocol, you have to register a new ALPN name.
    > That's annoying.  I don't know if it would be acceptable to register an
    > ALPN _prefix_, and then just self-allocate versions.

But, revising the protocol involves a new RFC, so I don't see the logistical
problem of registering a new ALPN.  Maybe it's annoying during development to
have to stick a new value in and not know what it's going to be?


--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email