Last Call: <draft-ietf-radext-radiusv11-07.txt> (RADIUS ALPN and removing MD5) to Experimental RFC

The IESG <iesg-secretary@ietf.org> Wed, 12 June 2024 19:38 UTC

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>
Subject: Last Call: <draft-ietf-radext-radiusv11-07.txt> (RADIUS ALPN and removing MD5) to Experimental RFC
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <171822109324.65402.13101295521526424546@ietfa.amsl.com>
Date: Wed, 12 Jun 2024 12:38:13 -0700
Message-ID-Hash: XDKKEKEGRW6PI7CZL2LCGRUFX7D4HDHO
CC: draft-ietf-radext-radiusv11@ietf.org, mrcullen42@gmail.com, paul.wouters@aiven.io, radext-chairs@ietf.org, radext@ietf.org, rieckers@dfn.de, rieckers@uni-bremen.de
Reply-To: last-call@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/FSI3C4eq9GaIwRhFa3Cb9HK-WWQ>

The IESG has received a request from the RADIUS EXTensions WG (radext) to
consider the following document: - 'RADIUS ALPN and removing MD5'
  <draft-ietf-radext-radiusv11-07.txt> as Experimental RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2024-06-26. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document defines Application-Layer Protocol Negotiation
   Extensions for use with RADIUS/TLS and RADIUS/DTLS.  These extensions
   permit the negotiation of an additional application protocol for
   RADIUS over (D)TLS.  No changes are made to RADIUS/UDP or RADIUS/TCP.
   The extensions allow the negotiation of a transport profile where the
   RADIUS shared secret is no longer used, and all MD5-based packet
   signing and attribute obfuscation methods are removed.  When this
   extension is used, the previous Authenticator field is repurposed to
   contain an explicit request / response identifier, called a Token.
   The Token also allows more than 256 packets to be outstanding on one
   connection.

   This extension can be seen as a transport profile for RADIUS, as it
   is not an entirely new protocol.  It uses the existing RADIUS packet
   layout and attribute format without change.  As such, it can carry
   all present and future RADIUS attributes.  Implementation of this
   extension requires only minor changes to the protocol encoder and
   decoder functionality.  The protocol defined by this extension is
   named "RADIUS version 1.1", or "RADIUS/1.1".

   This document updates RFC5176, RFC6614, and RFC 7360.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-radext-radiusv11/



No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-ietf-radext-radiusv11-07.txt> (… The IESG