IETF Logo Mail Archive

[radext] Re: Interim Meeting Tomorrow

Alan DeKok <alan.dekok@inkbridge.io> Tue, 03 March 2026 13:44 UTC

Return-Path: <alan.dekok@inkbridge.io>
X-Original-To: radext@mail2.ietf.org
Delivered-To: radext@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 37A35C36B422 for <radext@mail2.ietf.org>; Tue, 3 Mar 2026 05:44:40 -0800 (PST)
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, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=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=inkbridge.io header.b="hxw7LrJ6"; dkim=pass (2048-bit key) header.d=inkbridge.io header.b="SGzKBMfE"
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 KetUN0uAWy4f for <radext@mail2.ietf.org>; Tue, 3 Mar 2026 05:44:39 -0800 (PST)
Received: from mail2.networkradius.com (mail2.networkradius.com [184.95.211.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 4CAA9C36B3BF for <radext@ietf.org>; Tue, 3 Mar 2026 05:44:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=inkbridge.io; s=sep2024; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=BltW2aZQY7kdfFFZJzc4SR1v7AGb28H+ULCSOXQhWwc=; b=hxw7LrJ6zYiRNi7SXqLbmXi/Si TegrSW7FhU+bmc3VeDH4/lGmB6cvcljNCIuaNFadWXJeeJctOFHLqCtwviPLOIwwA72Na1rPyzf0q CKz1dJft80hobNvWUDq8Tn9TXPJqXPvJ7kNZ22wjQlw29Ks6/zLB1627rynGScUcnFR4T5US19iQM sOqn5EWVyTDJ/RAxlLoeM+NH+YqNIo6xP31BSP/r+JXoZ0MAGUEmxdzAPs4/FARjcs1BJZxKNt6kt AVdi7P1EAzpauSP+yy9qm2oH/fcAJ+fqNlRrw1kP98qsVoiyulgjRHM/vL8XRDDEYQcJGMPPEm9Hv gfxnC2+Q==;
Received: from mail.servers.fr.internal.networkradius.com ([192.168.42.56]:51132 helo=mail.networkradius.com) by mail2.networkradius.com with esmtp (Exim 4.97) (envelope-from <alan.dekok@inkbridge.io>) id 1vxQ34-00000000XYG-2UJF; Tue, 03 Mar 2026 13:44:30 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inkbridge.io; s=sep2024; t=1772545470; bh=BltW2aZQY7kdfFFZJzc4SR1v7AGb28H+ULCSOXQhWwc=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=SGzKBMfEpLNzUSzbNv/xWpq62f2QiCr0yLWxJ8QQ8lW7tBf+mdiq/NchrFgk/j6kK 8zCv1QsQDgKYuNf0eEfIF+az9awaM+mNxx5MPqtZDZJuUJXWBbfjKuN+EvyReV6bPY LY0GkOr+Mk756KbjtZJ364zrJdh0epfZkwkLfAQMYwnYJ/bPXgBntMq0BLKFz2BGPK LbsLAjNXFIbwJvpGcj6PlZiRBSNSoh9Ar77rf+TtWmmmuumpI26C0Y8zBFrwBtBoG5 UwCS3E72nhbrWlnF9FEXPOmGgt/V7t8wY09Gbm5rjKrdVZFy2G0jBck0rbfUzWrC7Y RandmyK9eLv0Q==
Received: from smtpclient.apple (unknown [75.98.136.130]) by mail.networkradius.com (Postfix) with ESMTPSA id A212A180; Tue, 3 Mar 2026 13:44:29 +0000 (UTC)
Content-Type: multipart/signed; boundary="Apple-Mail=_490CDEBD-9A6D-44E3-B3DD-1AFB35AC0AEB"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81.1.4\))
From: Alan DeKok <alan.dekok@inkbridge.io>
In-Reply-To: <3f4e938d-be5c-4a7f-8f67-5f18c63729de@dfn.de>
Date: Tue, 03 Mar 2026 08:44:17 -0500
Message-Id: <C2F8C59A-86CD-4D16-9A37-D5927FD5C5B8@inkbridge.io>
References: <CADZZzuqBDypBnOp9-sz=ZAnHC+-Qno-snm__MPFGY50NC_SLgg@mail.gmail.com> <08e101dca673$631b0fc0$29512f40$@smyslov.net> <e22fe2ef-9c89-40ba-9bbe-0aeaa18d6d2d@dfn.de> <CAA7Lko_UUjw5dj_+Fbtb9zWkDjfjT_14jaZp+kq3DyWAPqQPRg@mail.gmail.com> <3f4e938d-be5c-4a7f-8f67-5f18c63729de@dfn.de>
To: Jan-Frederik Rieckers <rieckers@dfn.de>
X-Mailer: Apple Mail (2.3826.700.81.1.4)
Message-ID-Hash: 2EU337YQ2XB7NVVKWWVA2GBSJGY2VQ33
X-Message-ID-Hash: 2EU337YQ2XB7NVVKWWVA2GBSJGY2VQ33
X-MailFrom: alan.dekok@inkbridge.io
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-radext.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: radext@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [radext] Re: Interim Meeting Tomorrow
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/DHnWBYRCS1sx4kF_zMedNaz-gFY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/radext>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Owner: <mailto:radext-owner@ietf.org>
List-Post: <mailto:radext@ietf.org>
List-Subscribe: <mailto:radext-join@ietf.org>
List-Unsubscribe: <mailto:radext-leave@ietf.org>

On Mar 3, 2026, at 8:23 AM, Jan-Frederik Rieckers <rieckers@dfn.de> wrote:
> On 3/3/26 11:49, Heikki Vatiainen wrote:
>> The current pull request uses SHOULD and RECOMMENDED as follows:
>> https://github.com/radext-wg/draft-ietf-radext-radiusdtls-bis/pull/162/ files#diff-168cb701f980750c7f337195b2ff5445abeb2742deebe68f7571dd0ba02b3582R292-R305 <https://github.com/radext-wg/draft-ietf-radext-radiusdtls-bis/pull/162/files#diff-168cb701f980750c7f337195b2ff5445abeb2742deebe68f7571dd0ba02b3582R292-R305>
>> - RadSec clients SHOULD use Application-Layer Protocol Negotiation (ALPN) to signal RadSec support.
>> - RadSec servers SHOULD implement support for ALPN.
>> - However, using ALPN will assist with future changes to RADIUS, and as such, its use is RECOMMENDED.
>> Would the above mean that the 'RECOMMENDED' is also a 'SHOULD'
> I think, the last "RECOMMENDED" is redundant and wouldn't need to be capitalized, because the two previous SHOULD's already say exactly the same thing.
> In terms of BCP14, "SHOULD" and "RECOMMENDED" are equivalent.
> 
> I don't think it's harmful to have this in the current form. The first two describe the behavior, the last part gives reasoning why we recommend it.

  Agreed.  "RECOMMENDED" is largely a synonym for "SHOULD".

  Alan DeKok.

v2.46.0 | Report a Bug | By Email | System Status