Skip to main content

EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3
RFC 9190

Revision differences

Document history

Date By Action
2023-08-01
(System) Received changes through RFC Editor sync (added Errata tag)
2022-02-15
(System)
Received changes through RFC Editor sync (created alias RFC 9190, changed title to 'EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3', changed …
Received changes through RFC Editor sync (created alias RFC 9190, changed title to 'EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3', changed abstract to 'The Extensible Authentication Protocol (EAP), defined in RFC 3748, provides a standard mechanism for support of multiple authentication methods.  This document specifies the use of EAP-TLS with TLS 1.3 while remaining backwards compatible with existing implementations of EAP-TLS.  TLS 1.3 provides significantly improved security and privacy, and reduced latency when compared to earlier versions of TLS.  EAP-TLS with TLS 1.3 (EAP-TLS 1.3) further improves security and privacy by always providing forward secrecy, never disclosing the peer identity, and by mandating use of revocation checking when compared to EAP-TLS with earlier versions of TLS.  This document also provides guidance on authentication, authorization, and resumption for EAP-TLS in general (regardless of the underlying TLS version used).  This document updates RFC 5216.', changed pages to 31, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2022-02-15, changed IESG state to RFC Published, created updates relation between draft-ietf-emu-eap-tls13 and RFC 5216)
2022-02-15
(System) RFC published