[radext] Re: Interim Meeting Tomorrow

Jan-Frederik Rieckers <rieckers@dfn.de> Tue, 03 March 2026 13:23 UTC

Return-Path: <rieckers@dfn.de>
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 E483CC36767A for <radext@mail2.ietf.org>; Tue, 3 Mar 2026 05:23:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=dfn.de
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 S8nImZeQvayZ for <radext@mail2.ietf.org>; Tue, 3 Mar 2026 05:23:57 -0800 (PST)
Received: from a1004.mx.srv.dfn.de (a1004.mx.srv.dfn.de [IPv6:2001:638:d:c301:acdc:1979:2:58]) (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 B9B71C367672 for <radext@ietf.org>; Tue, 3 Mar 2026 05:23:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dfn.de; h= content-type:content-type:in-reply-to:organization:from:from :content-language:references:subject:subject:user-agent :mime-version:date:date:message-id:received; s=s1; t=1772544230; x=1774358631; bh=GA/Qp4hrOYZ1EnfjWFSKBkS90ZMNBwz0O2wERnpzKwY=; b= KIv7te2iY9DffMRvH6JdBRzi1wMiWeHL8VQuEg4f4HjZYfKtNUmqEjUo0obGkDFa cG1Eylr00g4bUJ1QhxUFwNZRpTrUh5LcY+xiLApyOSrj26nvi1Dla6JgQFTicqsl YZfvHi65ZASqtbkYruvM4Vp4DTghWnK7Dflxpx7MyBA=
Received: from mail.dfn.de (mail.dfn.de [194.95.245.150]) by a1004.mx.srv.dfn.de (Postfix) with ESMTPS id EC56420021D for <radext@ietf.org>; Tue, 3 Mar 2026 14:23:49 +0100 (CET)
Received: from [IPV6:2001:638:d:10b1::8] (unknown [IPv6:2001:638:d:10b1::8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mspool2.in.dfn.de (Postfix) with ESMTPSA id A7AFE39B for <radext@ietf.org>; Tue, 3 Mar 2026 14:23:49 +0100 (CET)
Message-ID: <3f4e938d-be5c-4a7f-8f67-5f18c63729de@dfn.de>
Date: Tue, 03 Mar 2026 14:23:47 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: radext@ietf.org
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>
Content-Language: en-US
From: Jan-Frederik Rieckers <rieckers@dfn.de>
Organization: DFN e.V.
In-Reply-To: <CAA7Lko_UUjw5dj_+Fbtb9zWkDjfjT_14jaZp+kq3DyWAPqQPRg@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms050509000303000308070109"
Message-ID-Hash: TLQPXE44I3BO3UNGTL62UJB57LLDXITU
X-Message-ID-Hash: TLQPXE44I3BO3UNGTL62UJB57LLDXITU
X-MailFrom: rieckers@dfn.de
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
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/NzegyILJdCNTIkuzrlaMKEIJUTg>
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 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.

Cheers,
Janfred

-- 
Herr Jan-Frederik Rieckers
Security, Trust & Identity Services

E-Mail: rieckers@dfn.de | Fon: +49 30884299-339 | Fax: +49 30884299-370
Pronomen: er/sein | Pronouns: he/him
__________________________________________________________________________________

DFN - Deutsches Forschungsnetz | German National Research and Education 
Network
Verein zur Förderung eines Deutschen Forschungsnetzes e.V.
Alexanderplatz 1 | 10178 Berlin
https://www.dfn.de

Vorstand: Prof. Dr.-Ing. Stefan Wesner | Prof. Dr. Helmut Reiser | 
Christian Zens
Geschäftsführung: Dr. Christian Grimm | Alina Hain
VR AG Charlottenburg 7729B | USt.-ID. DE 136623822