[radext] WG Review: RADIUS EXTensions (radext)
The IESG <iesg-secretary@ietf.org> Fri, 17 February 2023 18:39 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: radext@ietf.org
Delivered-To: radext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 303FEC14CF15; Fri, 17 Feb 2023 10:39:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 9.10.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: radext@ietf.org
Reply-To: iesg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <167665919318.19067.15793841454678347039@ietfa.amsl.com>
Date: Fri, 17 Feb 2023 10:39:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/gLuXXro2gc32tps-DNA4_OrhYtY>
Subject: [radext] WG Review: RADIUS EXTensions (radext)
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 17 Feb 2023 18:39:53 -0000
A new IETF WG has been proposed in the Operations and Management Area. The IESG has not made any determination yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by 2023-02-27. RADIUS EXTensions (radext) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: Margaret Cullen <mrcullen42@gmail.com> Valery Smyslov <valery@smyslov.net> Assigned Area Director: Paul Wouters <paul.wouters@aiven.io> Operations and Management Area Directors: Warren Kumari <warren@kumari.net> Robert Wilton <rwilton@cisco.com> Mailing list: Address: radext@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/radext Archive: https://mailarchive.ietf.org/arch/browse/radext/ Group page: https://datatracker.ietf.org/group/radext/ Charter: https://datatracker.ietf.org/doc/charter-ietf-radext/ The RADIUS Extensions Working Group will focus on extensions to the RADIUS protocol. To ensure backward compatibility with existing RADIUS implementations, as well as compatibility between RADIUS and Diameter, all documents produced must specify means of interoperation with legacy RADIUS. Any non-backwards compatibility changes with existing RADIUS RFCs, including RFCs 2865-2869, 3162, 3575, 3579, 3580, 4668-4673,4675, 5080, 5090, 5176 and 6158 must be justified. Transport profiles should be compatible with RFC 3539, with any non-backwards compatibility changes justified. The WG will review its existing RFCs' document track categories and where necessary or useful change document tracks, with minor changes in the documents if needed. Work Items The immediate goals of the RADEXT working group are: - Deprecating the use of insecure transports outside of secure networks. This work updates RFC 6421. - Bring RFC 6614 (RADIUS/TLS), and RFC 7360 (RADIUS/DTLS) to Standards track. - Define best practices for using TLS-PSK with TLS-based transport. - Define best practices for RADIUS roaming, and roaming consortia based on experience with RADIUS/TLS. - Improve operations for multi-hop RADIUS networks: e.g. loop detection and prevention, a multi-hop Status-Server equivalent with ability to Trace the proxy steps a RADIUS message will follow. - Extend the 8-bit RADIUS ID space to allow more than 256 "in flight" packets across one connection. - Allow for CoA / Disconnect packets to be sent in "reverse" down a RADIUS/TLS or RADIUS/DTLS connection. This functionality assists with transit of NATs. - Defining Application-Layer Protocol Negotiation (ALPN) extensions for RADIUS/TLS and RADIUS/TLS which allow the use of those transports in a FIPS-140 compliant environment. Timeline: Much of this work should be completed by 2024 in order to be part of the Wi-Fi 8 release, with products in 2026. Milestones: TBD