RFC 9427: TLS-Based Extensible Authentication Protocol (EAP) Types for Use with TLS 1.3
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9427
- Published
- June 2023
- Authors
- A. DeKok
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 19
- Also known as
- —
- Updated by:
- RFC 9930
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9430Extension of the Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE) to Transport Layer Security (TLS)Current
July 2023
- RFC 9431Message Queuing Telemetry Transport (MQTT) and Transport Layer Security (TLS) Profile of Authentication and Authorization for Constrained Environments (ACE) FrameworkCurrent
July 2023
- RFC 9420The Messaging Layer Security (MLS) ProtocolCurrent
July 2023
- RFC 9444Automated Certificate Management Environment (ACME) for SubdomainsCurrent
August 2023
- RFC 9447Automated Certificate Management Environment (ACME) Challenges Using an Authority TokenCurrent
September 2023
- RFC 9448TNAuthList Profile of Automated Certificate Management Environment (ACME) Authority TokenCurrent
September 2023
- RFC 9449OAuth 2.0 Demonstrating Proof of Possession (DPoP)Current
September 2023
- RFC 9399Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesCurrent
May 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?