[radext] I-D Action: draft-ietf-radext-deprecating-radius-00.txt
internet-drafts@ietf.org Tue, 07 November 2023 10:01 UTC
Return-Path: <internet-drafts@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 DCDC8C1E4E5A; Tue, 7 Nov 2023 02:01:45 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 11.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: radext@ietf.org
Message-ID: <169935130587.7777.10016917377776170111@ietfa.amsl.com>
Date: Tue, 07 Nov 2023 02:01:45 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/1dSMhqerlacdm-lp0Oa_V-2iP3g>
Subject: [radext] I-D Action: draft-ietf-radext-deprecating-radius-00.txt
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: Tue, 07 Nov 2023 10:01:45 -0000
Internet-Draft draft-ietf-radext-deprecating-radius-00.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-ietf-radext-deprecating-radius-00.txt Pages: 34 Dates: 2023-11-07 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 those 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-ietf-radext-deprecating-radius/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-radext-deprecating-radius-00.html Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts
- [radext] I-D Action: draft-ietf-radext-deprecatin… internet-drafts