IETF Logo Mail Archive

[radext] Re: Gorry Fairhurst's Discuss on draft-ietf-radext-radiusdtls-bis-15: (with DISCUSS and COMMENT)

Jan-Frederik Rieckers <rieckers@dfn.de> Fri, 05 June 2026 20:40 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 B1516FBFA66D; Fri, 5 Jun 2026 13:40:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780692054; bh=eEZRnQOnf1lQ8vtvVBGxtydqclwN5lZVi2dQS7eCJVY=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=L4bzNRKCQGCicTrD6AymCsTk/cVF+nn+hJXWlzBRdkSkKPr6TQgOPmDHFDZUHoHlx AmP4k2eHgjCKzRp1lpecJn/BM0aP/GO0/KOw1mfxiHtQ7ggTDD/wXz+HtOfFGBzBoH OG3zl2q5yw+MgdYePdNFz6gI9eMh9Dn7/uqau5Mc=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 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_MED=-2.3, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, 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 kMzK2Qn4JZ0r; Fri, 5 Jun 2026 13:40:53 -0700 (PDT)
Received: from c1004.mx.srv.dfn.de (c1004.mx.srv.dfn.de [194.95.239.6]) (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 B1ED7FBF9DAB; Fri, 5 Jun 2026 13:37:25 -0700 (PDT)
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=1780691837; x=1782506238; bh=eEZRnQOnf1lQ8vtvVBGxtydqclwN5lZVi2dQS7eCJVY=; b= lpfiZLZ2uT6ksPpQKC7jXGIFh3MKWcQBeKUDhL4+JdjKi5bXTnvWhGM2KHeVtj47 GCew9rwVtOf6B+7Ho7UQ+XzxTNiA8EyXcsS+bM36Ra/ucegEABy9ZIuj1NrnfZds 21xNTCw088aBrbuXWRAkWC093b99xoBuaiotBvj3vPs=
Received: from mail.dfn.de (mail.dfn.de [IPv6:2001:638:d:c102::150]) by c1004.mx.srv.dfn.de (Postfix) with ESMTPS id 496B5120109; Fri, 05 Jun 2026 22:37:16 +0200 (CEST)
Received: from [IPV6:2001:638:d:10b1::9] (unknown [IPv6:2001:638:d:10b1::9]) (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 291A939B; Fri, 5 Jun 2026 22:37:15 +0200 (CEST)
Message-ID: <26439355-e06c-48fc-87e3-83461867cbcc@dfn.de>
Date: Fri, 05 Jun 2026 22:37:09 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
References: <177263477673.4189860.18422256499304151674@dt-datatracker-6ff7c68975-7k42g> <70F300A2-4747-47AD-948E-5CBC1E599F06@inkbridge.io> <d61c9879-a4b2-4978-9ead-d1ac92242b21@erg.abdn.ac.uk> <78A01BFD-CCF2-4B02-92BD-DDC0F8BBC50F@inkbridge.io> <5eb0c79f-89e1-4e13-9b5c-2fbc74b7bf6c@erg.abdn.ac.uk>
Content-Language: en-US
From: Jan-Frederik Rieckers <rieckers@dfn.de>
X-Enigmail-Draft-Status: N11222
Organization: DFN e.V.
In-Reply-To: <5eb0c79f-89e1-4e13-9b5c-2fbc74b7bf6c@erg.abdn.ac.uk>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms030604000503030209000003"
Message-ID-Hash: Q6QI2WAY4VEUJP7DD4LPBN2KCBNPPX2H
X-Message-ID-Hash: Q6QI2WAY4VEUJP7DD4LPBN2KCBNPPX2H
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
CC: The IESG <iesg@ietf.org>, draft-ietf-radext-radiusdtls-bis@ietf.org, mrcullen42@gmail.com, radext-chairs@ietf.org, radext@ietf.org, valery@smyslov.net
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [radext] Re: Gorry Fairhurst's Discuss on draft-ietf-radext-radiusdtls-bis-15: (with DISCUSS and COMMENT)
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/Hsc7zpR2TST54W9h4cMdWFDW8LU>
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>

Hi Gorry,

sorry for replying so late.

On 5/6/26 15:14, Gorry Fairhurst wrote:
> More could have been expanded on the areas of my DISCUScomments and I'd 
> always happy to help further on any of these topics However, I am 
> grateful that the new text you ahve prepared has avoided the problematic 
> areas into which document had ventured, and hence I no longer see the 
> need to hold a DISCUSS position. I shall update my ballot position to NO 
> OBJECTION.

Thanks for your discusses, and for confirming they are now addressed.
I'm happy to update the document further, if there's still wording that 
can be improved.

> Please note also my comments, in particular my recommendation to cite 
> RFC8085 with respect to the requirements for the use of UDP.
I've read your comments again, and looked over RFC 8085 too, and my 
comment from earlier still stands:

I'm not sure which parts of RFC8085 we can reference here that would add 
value to this document.
 From what I read, there is little guidance on implementation and more 
on how to design a UDP-based protocol. Since we are using an existing 
UDP-based protocol (RADIUS) and only extending it, there is not much 
that we can do without significantly changing the way RADIUS behaves.

If you have specific parts of RFC 8085 that you feel are applicable to 
this document and should be referenced, I'm happy to add 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

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