Re: [radext] I-D Action: draft-dekok-radext-deprecating-radius-05.txt

Alan DeKok <aland@deployingradius.com> Mon, 23 October 2023 20:25 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 66E4BC151995 for <radext@ietfa.amsl.com>; Mon, 23 Oct 2023 13:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 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, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 a7uYU98TxnMS for <radext@ietfa.amsl.com>; Mon, 23 Oct 2023 13:25:55 -0700 (PDT)
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 E78E5C17C53E for <radext@ietf.org>; Mon, 23 Oct 2023 13:25:53 -0700 (PDT)
Received: from smtpclient.apple (135-23-95-173.cpe.pppoe.ca [135.23.95.173]) by mail.networkradius.com (Postfix) with ESMTPSA id 394A4659 for <radext@ietf.org>; Mon, 23 Oct 2023 20:25:49 +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\))
Date: Mon, 23 Oct 2023 16:25:47 -0400
References: <169806317607.53631.5787593872794100493@ietfa.amsl.com>
To: radext@ietf.org
In-Reply-To: <169806317607.53631.5787593872794100493@ietfa.amsl.com>
Message-Id: <FD621747-F715-4AE3-933D-00F6E4D36243@deployingradius.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/BvHNqeSOfwxGR0Dljnj7XokJG7E>
Subject: Re: [radext] I-D Action: draft-dekok-radext-deprecating-radius-05.txt
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, 23 Oct 2023 20:25:59 -0000

  This document is minor word smithing over -04 based on WG feedback.  I hope to discuss some of these issues in Prague.

  I think there's no major controversy here.  The main blocking item for this document is that it should ideally be published along side 6614bis.

> On Oct 23, 2023, at 8:12 AM, internet-drafts@ietf.org wrote:
> 
> Internet-Draft draft-dekok-radext-deprecating-radius-05.txt is now available.
> It is a work item of the RADIUS EXTensions (RADEXT) WG of the IETF.
> 
>   Title:   Deprecating Insecure Practices in RADIUS
>   Author:  Alan DeKok
>   Name:    draft-dekok-radext-deprecating-radius-05.txt
>   Pages:   34
>   Dates:   2023-10-23
> 
> 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 using 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 in secure networks is still
>   discouraged.  For all other environments, the use of secure
>   transports such as IPsec or TLS is mandated.  We also discuss
>   additional security issues with RADIUS deployments, and give
>   recommendations for practices which increase security and privacy.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-dekok-radext-deprecating-radius/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-dekok-radext-deprecating-radius-05.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-dekok-radext-deprecating-radius-05
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext