IETF Logo Mail Archive

[radext] New draft: RFC6614bis (RADIUS/TLS)

Jan-Frederik Rieckers <rieckers@dfn.de> Mon, 24 October 2022 15:01 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 2A20CC14F73B for <radext@ietfa.amsl.com>; Mon, 24 Oct 2022 08:01:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 sUbm9DC17iwL for <radext@ietfa.amsl.com>; Mon, 24 Oct 2022 08:00:55 -0700 (PDT)
Received: from b1004.mx.srv.dfn.de (b1004.mx.srv.dfn.de [194.95.235.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 7262DC14CE3C for <radext@ietf.org>; Mon, 24 Oct 2022 08:00:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dfn.de; h= content-type:content-type:organization:subject:subject:from:from :content-language:user-agent:mime-version:date:date:message-id :received; s=s1; t=1666623647; x=1668438048; bh=y1sXBq8+/XG9CDOD hGzCW87JoqwbDzF9JguwIY7oEZM=; b=k6C91hltd+byK3KBDDeABsdFCVKiBWxO Bc5Zxo/Yw2pIE/HX7wGV6nMbTkT0QmtV+Kji5IzUuiO7Ghr1o8Zlnt5i7dODz12p MWPoQx84HZ30L1lzh1ofqkoUaQsz9fr5a3m9xF/cdgsOwGk548NIjC3EmW+N5ghE DHKaxqxd+oo=
Received: from mail.dfn.de (mail.dfn.de [194.95.245.150]) by b1004.mx.srv.dfn.de (Postfix) with ESMTPS id 91CCE2200D4 for <radext@ietf.org>; Mon, 24 Oct 2022 17:00:47 +0200 (CEST)
Received: from [IPV6:2001:638:d:1016::1000] (unknown [IPv6:2001:638:d:1016::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 4751D103 for <radext@ietf.org>; Mon, 24 Oct 2022 17:00:46 +0200 (CEST)
Message-ID: <d9a015f8-60a7-8eb1-65e0-ea19633c3784@dfn.de>
Date: Mon, 24 Oct 2022 17:00:44 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.3
Content-Language: en-US
To: radext@ietf.org
From: Jan-Frederik Rieckers <rieckers@dfn.de>
Organization: DFN e.V.
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms030501000104040105030605"
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/kkw55qsYJE_LZ5V_vcml_SQ9Pr4>
Subject: [radext] New draft: RFC6614bis (RADIUS/TLS)
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: Mon, 24 Oct 2022 15:01:00 -0000

Hi to all,

I have submitted a draft to re-specify RADIUS/TLS, as intended by the 
proposed radextra charter. (Moving RADIUS/TLS from experimental to 
proposed standard)

See https://github.com/Janfred/draft-rieckers-radext-rfc6614bis for the 
draft.

To spot changes more direct, I've uploaded the original text of the 
draft as -00 version, so the diff shows the changes I've already made:

https://www.ietf.org/rfcdiff?url2=draft-rieckers-radext-rfc6614bis-01.txt

I have drastically restructured section 2.2 in comparison to RFC6614, so 
the diff tool does not really show the differences in a usable way, but 
the main changes I've made are explained in section 1.2 the -01 version.

For now, I have only put myself in the author section as editor, if any 
of the original RFC6614 authors are interested in helping, please let me 
know. (I have already spoken with Stefan Winter and he wanted to 
contribute text)

Feedback welcome.

I have added some comments on possible further extension points to my 
editors copy on github and will continue to add comments there (and 
maybe some text) in preparation for IETF 115.
https://janfred.github.io/draft-rieckers-radext-rfc6614bis/draft-rieckers-radext-rfc6614bis.html

Greetings
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