Re: [radext] New Version Notification for draft-dekok-radext-deprecating-radius-03.txt

Alan DeKok <aland@deployingradius.com> Thu, 03 August 2023 18:54 UTC

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\))
Date: Thu, 03 Aug 2023 14:54:03 -0400
References: <169108881026.1178.3760681063021967297@ietfa.amsl.com>
To: radext@ietf.org
In-Reply-To: <169108881026.1178.3760681063021967297@ietfa.amsl.com>
Message-Id: <D0DA0767-DCB1-4CA7-9F2E-2F24DA44FDCC@deployingradius.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/wXLh-TiR5EZedFKoOCte65H-2Aw>
Subject: Re: [radext] New Version Notification for draft-dekok-radext-deprecating-radius-03.txt
Precedence: list

  With some additional text on privacy as discussed recently.

> On Aug 3, 2023, at 2:53 PM, internet-drafts@ietf.org wrote:
> 
> 
> A new version of I-D, draft-dekok-radext-deprecating-radius-03.txt
> has been successfully submitted by Alan DeKok and posted to the
> IETF repository.
> 
> Name:		draft-dekok-radext-deprecating-radius
> Revision:	03
> Title:		Deprecating RADIUS/UDP and RADIUS/TCP
> Document date:	2023-08-03
> Group:		Individual Submission
> Pages:		27
> URL:            https://www.ietf.org/archive/id/draft-dekok-radext-deprecating-radius-03.txt
> Status:         https://datatracker.ietf.org/doc/draft-dekok-radext-deprecating-radius/
> Html:           https://www.ietf.org/archive/id/draft-dekok-radext-deprecating-radius-03.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-dekok-radext-deprecating-radius
> Diff:           https://author-tools.ietf.org/iddiff?url2=draft-dekok-radext-deprecating-radius-03
> 
> Abstract:
>   RADIUS crypto-agility was first mandated as future work by RFC 6421.
>   The outcome of that work was the publication of RADIUS over TLS (RFC
>   6614) and RADIUS over DTLS (RFC 7360) as experimental documents.
>   Those transport protocols have been in wide-spread use for many years
>   in a wide range of networks.  They have proven their utility as
>   replacements for the previous UDP (RFC 2865) and TCP (RFC 6613)
>   transports.  With that knowledge, the continued use of insecure
>   transports for RADIUS has serious and negative implications for
>   privacy and security.
> 
>   This document formally deprecates the use of the User Datagram
>   Protocol (UDP) and of the Transmission Control Protocol (TCP) as
>   transport protocols for RADIUS.  These transports are permitted
>   inside of secure networks, but their use even in that environment is
>   strongly discouraged.  For all other environments, the use of secure
>   transports such as IPsec or TLS is mandated.
> 
> 
> 
> 
> The IETF Secretariat
> 
>

Re: [radext] New Version Notification for draft-d… Alan DeKok