IETF Logo Mail Archive

Re: [radext] Proposed charter text based on IETF-115 BoF

Jan-Frederik Rieckers <rieckers@dfn.de> Thu, 24 November 2022 23:24 UTC

Return-Path: <rieckers@dfn.de>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B15C14CE44 for <radext@ietfa.amsl.com>; Thu, 24 Nov 2022 15:24:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 (1024-bit key) header.d=dfn.de
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 u-hoQ3Z1LDeJ for <radext@ietfa.amsl.com>; Thu, 24 Nov 2022 15:24:15 -0800 (PST)
Received: from a1004.mx.srv.dfn.de (a1004.mx.srv.dfn.de [194.95.233.6]) (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 C538CC14CF11 for <radext@ietf.org>; Thu, 24 Nov 2022 15:24:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dfn.de; h= content-type:content-type:in-reply-to:subject:subject :organization:from:from:references:content-language:user-agent :mime-version:date:date:message-id:received; s=s1; t=1669332249; x=1671146650; bh=y9ZkrRSUNJisMppddBXgFXeO+SZhz+8uuSsgNrhIL3g=; b= XiblTQgwJxP/hVvSveyTCgWUBE8QL9CJCGmLqB9yL3kGxnbtDEsyxStVWHbcxsrV VzkTtyFITWq7QIaeybZs30JrJKyg9Ireo4xpCZBYDlnGFzL5CftarcHBGDMDV9fd t5ElSz6wLJy9OnOsvVvlDL1QF5+7MF7Q2QQbMJhFYBc=
Received: from mail.dfn.de (mail.dfn.de [194.95.245.150]) by a1004.mx.srv.dfn.de (Postfix) with ESMTPS id A42832000F1 for <radext@ietf.org>; Fri, 25 Nov 2022 00:24:09 +0100 (CET)
Received: from [IPV6:2001:638:d:1010::1000] (unknown [IPv6:2001:638:d:1010::1000]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mspool2.srv.dfn.de (Postfix) with ESMTPSA id 0AE97103 for <radext@ietf.org>; Fri, 25 Nov 2022 00:24:07 +0100 (CET)
Message-ID: <7604703a-075f-7ad6-9c85-24e9a0f845fb@dfn.de>
Date: Fri, 25 Nov 2022 00:24:06 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0
Content-Language: en-US
To: radext@ietf.org
References: <FD0507D4-2C1D-478A-97E0-ECEEF1A5613B@deployingradius.com> <E82B0ECD-4580-4F35-B07B-35685CFC5C44@aiven.io> <883f3572-121f-5ed8-7378-1a91c5525f88@iea-software.com> <EAAC2507-5D29-4453-8881-BC8D9D5314D8@deployingradius.com> <CAOW+2dsKg_H9f3zRUnanCpgGO+G=VPyxzWa9hsrCJCpsnoBsxA@mail.gmail.com> <7CB701B8-BD8F-4ADC-9265-12FC7EBE8FB6@deployingradius.com> <CAOW+2dtDkN3Hvk1vmuyJYGP9KS5WaGDenwQBb7-g12e6SxvEzw@mail.gmail.com> <05f4711f-4f9f-7bb6-e04f-b3c9ebc73202@dfn.de> <9e24bb0f-b12b-8235-3e88-65d4c59f205c@newtoncomputing.co.uk> <e94b8273-6189-efc4-dfa5-3ab3bacbdac6@dfn.de> <7cdb23d1-1d91-71ed-14ee-157315beb278@newtoncomputing.co.uk>
From: Jan-Frederik Rieckers <rieckers@dfn.de>
Autocrypt: addr=rieckers@dfn.de; keydata= xjMEYS90/RYJKwYBBAHaRw8BAQdAWXYFYTJZD1YR1SztUNqHenPGnf+gdQe/9LjiHlr2XATN J0phbi1GcmVkZXJpayBSaWVja2VycyA8cmllY2tlcnNAZGZuLmRlPsKWBBMWCAA+AhsDBQsJ CAcCBhUKCQgLAgQWAgMBAh4BAheAFiEE/fv7DCp4WBOrb8RyDYuiXSS+ypYFAmMXdJkFCQNL 9JwACgkQDYuiXSS+ypYZhQD+IvXSlzMB632TceTFUZ66vWijHZA9TymKjM27QzxjCcQA/ilb zGnQRFxRvpqGeJCwK/9MP9CZyyUjgAPQBaZNoTcOzjgEYS90/RIKKwYBBAGXVQEFAQEHQBxo 6esD49rxn4d3su5fJJL79XjfKNy26LiFE9Gpg38+AwEIB8J+BBgWCAAmAhsMFiEE/fv7DCp4 WBOrb8RyDYuiXSS+ypYFAmMXdKIFCQNL9KUACgkQDYuiXSS+ypY8IwEA5hkI+oA2pFmD6zXj rULCT+G9o8A5xSkMZBiw6U6yKcMBAMpTki1h4qCwaQR+hvt1rNjJr4ISUtd+ErlHlPWsxIgI
Organization: DFN e.V.
In-Reply-To: <7cdb23d1-1d91-71ed-14ee-157315beb278@newtoncomputing.co.uk>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------eV0J0RIHSHZ4kgB9D2J365e5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/nEivFRAmvFPpUKiqvwLM0Fm9UoA>
Subject: Re: [radext] Proposed charter text based on IETF-115 BoF
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2022 23:24:19 -0000

On 24.11.22 20:00, Matthew Newton wrote:
> On 24/11/2022 18:09, Jan-Frederik Rieckers wrote:
>> On 24.11.22 17:51, Matthew Newton wrote:
>>> On 24/11/2022 16:23, Jan-Frederik Rieckers wrote:
>>>> Of course you can do this locally if you have control over all 
>>>> involved servers, but if you don't then this is not possible without 
>>>> a flag day 
>>>
>>> I'm not sure why you would need a flag day? Or a configuration flag.
>>>
>>> There is no need to update all servers at once, just each hop. The 
>>> "upstream" server can be configured to listen on the new SRADIUS port 
>>> as well as e.g. 1812/udp. Then the "downstream" servers can in time 
>>> be configured to connect over SRADIUS instead of UDP. Once nothing is 
>>> using 1812/udp, the "upstream" server is reconfigured to stop 
>>> listening on it.
>>
>> The problem here is: As far as I understood Bernard (please correct me 
>> if I misunderstood something here), the new spec for RADIUS without 
>> MD5 should run on the same port. And with this, the two variants 
>> cannot be used in parallel, or you would have to have a means of 
>> negotiation.
> 
> draft-dekok-radext-sradius sect.10 requests two new ports.

Sorry, I did not express myself clearly on this one. What I meant was: I 
understood Bernards comments that he suggests re-using the same port 
instead of the separate port as it is currently planned in the draft.

But if ALPN (as just suggested by Alan) is a usable way, that seems to 
be the best option. (Not sure about the name RADIUS+FIPS though, but I 
suppose that's a discussion for when the WG is chartered)

Cheers,

Janfred

-- 
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
www.dfn.de

Vorstand: Prof. Dr. Odej Kao (Vorsitzender) | Dr. Rainer Bockholt | 
Christian Zens
Geschäftsführung: Dr. Christian Grimm | Jochem Pattloch
VR AG Charlottenburg 7729B | USt.-ID. DE 1366/23822

v2.23.0 | Report a Bug | By Email