A new Request for Comments is now available in online RFC libraries.

        
        RFC 9930

        Title:      Tunnel Extensible Authentication Protocol (TEAP) 
                    Version 1 
        Author:     A. DeKok, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2026
        Mailbox:    [email protected]
        Pages:      107
        Obsoletes:  RFC 7170
        Updates:    RFC 9427

        I-D Tag:    draft-ietf-emu-rfc7170bis-22.txt

        URL:        https://www.rfc-editor.org/info/rfc9930

        DOI:        10.17487/RFC9930

This document defines the Tunnel Extensible Authentication Protocol
(TEAP) version 1.  TEAP is a tunnel-based EAP method that enables
secure communication between a peer and a server by using the
Transport Layer Security (TLS) protocol to establish a mutually
authenticated tunnel.  Within the tunnel, TLV objects are used to
convey authentication-related data between the EAP peer and the EAP
server.  This document obsoletes RFC 7170 and updates RFC 9427 by
moving all TEAP specifications from those documents to this one.

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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team


_______________________________________________
Emu mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to