TLS-Based Extensible Authentication Protocol (EAP) Types for Use with TLS 1.3
RFC 9427
Revision differences
Document history
Date | By | Action |
---|---|---|
2023-06-27
|
(System) | Received changes through RFC Editor sync (created alias RFC 9427, changed title to 'TLS-Based Extensible Authentication Protocol (EAP) Types for Use with TLS 1.3', … Received changes through RFC Editor sync (created alias RFC 9427, changed title to 'TLS-Based Extensible Authentication Protocol (EAP) Types for Use with TLS 1.3', changed abstract to '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.', changed pages to 19, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2023-06-27, changed IESG state to RFC Published, created updates relation between draft-ietf-emu-tls-eap-types and RFC 4851, created updates relation between draft-ietf-emu-tls-eap-types and RFC 5281, created updates relation between draft-ietf-emu-tls-eap-types and RFC 7170) |
2023-06-27
|
(System) | RFC published |