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:    al...@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-edi...@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


_______________________________________________
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu

Reply via email to