RFC 9427 on TLS-Based Extensible Authentication Protocol (EAP) Types for Use with TLS 1.3
rfc-editor@rfc-editor.org Wed, 28 June 2023 02:31 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E81DC1516F2; Tue, 27 Jun 2023 19:31:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 92__m-G2HAYz; Tue, 27 Jun 2023 19:30:59 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (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 3AE62C151993; Tue, 27 Jun 2023 19:30:59 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 25F347FDC3; Tue, 27 Jun 2023 19:30:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9427 on TLS-Based Extensible Authentication Protocol (EAP) Types for Use with TLS 1.3
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, emu@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230628023059.25F347FDC3@rfcpa.amsl.com>
Date: Tue, 27 Jun 2023 19:30:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/mOq_onqtsxGEH90wkejKqai_7sw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jun 2023 02:31:03 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9427
Title: TLS-Based Extensible Authentication Protocol (EAP)
Types for Use with TLS 1.3
Author: A. DeKok
Status: Standards Track
Stream: IETF
Date: June 2023
Mailbox: aland@freeradius.org
Pages: 19
Updates: RFC 4851, RFC 5281, RFC 7170
I-D Tag: draft-ietf-emu-tls-eap-types-13.txt
URL: https://www.rfc-editor.org/info/rfc9427
DOI: 10.17487/RFC9427
The Extensible Authentication Protocol-TLS (EAP-TLS) (RFC 5216) has
been updated for TLS 1.3 in RFC 9190. Many other EAP Types also
depend on TLS, such as EAP-Flexible Authentication via Secure
Tunneling (EAP-FAST) (RFC 4851), EAP-Tunneled TLS (EAP-TTLS) (RFC
5281), the Tunnel Extensible Authentication Protocol (TEAP) (RFC
7170). It is possible that many vendor-specific EAP methods, such as
the Protected Extensible Authentication Protocol (PEAP), depend on
TLS as well. This document updates those methods in order to use the
new key derivation methods available in TLS 1.3. Additional changes
necessitated by TLS 1.3 are also discussed.
This document is a product of the EAP Method Update Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC