[radext] Tracking issues with RFC 6613, 6614, and 7360 for (D)TLS-bis
Alan DeKok <aland@deployingradius.com> Sun, 03 December 2023 19:29 UTC
Return-Path: <aland@deployingradius.com>
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 8C81AC15107C for <radext@ietfa.amsl.com>; Sun, 3 Dec 2023 11:29:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 5vKm9do6YePw for <radext@ietfa.amsl.com>; Sun, 3 Dec 2023 11:29:28 -0800 (PST)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (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 214A1C15107A for <radext@ietf.org>; Sun, 3 Dec 2023 11:29:26 -0800 (PST)
Received: from smtpclient.apple (135-23-95-173.cpe.pppoe.ca [135.23.95.173]) by mail.networkradius.com (Postfix) with ESMTPSA id 8BF06340 for <radext@ietf.org>; Sun, 3 Dec 2023 19:29:24 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
From: Alan DeKok <aland@deployingradius.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Message-Id: <A92A13C0-DBD3-4237-BB52-F23BE9E801E3@deployingradius.com>
Date: Sun, 03 Dec 2023 14:29:22 -0500
To: radext@ietf.org
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/QWiGVc0At-O5JG-arqeqWgIDQ3E>
Subject: [radext] Tracking issues with RFC 6613, 6614, and 7360 for (D)TLS-bis
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: Sun, 03 Dec 2023 19:29:30 -0000
Based on discussions from IETF 118, I've created 3 new GitHub repositories: https://github.com/radext-wg/rfc6613 https://github.com/radext-wg/rfc6614 https://github.com/radext-wg/rfc7360 The intent is for the WG to open issues against theses RFCs for editorial content, so that we can track what needs to go into the new (D)TLS-bis document. One approach is to just open a new issue for every section of the original RFCs, and then have a discussion in the issue tracker. We could then mark the issue up as completed when there is consensus that the new document addresses all of the concerns. Alan DeKok.