RFC 9930: Tunnel Extensible Authentication Protocol (TEAP) Version 1
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9930
- Published
- February 2026
- Authors
- A. DeKok
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 107
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9935Internet X.509 Public Key Infrastructure - Algorithm Identifiers for the Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM)Current
March 2026
- RFC 9925Unsigned X.509 CertificatesCurrent
February 2026
- RFC 9936Use of ML-KEM in the Cryptographic Message Syntax (CMS)Current
March 2026
- RFC 9921CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161Current
February 2026
- RFC 9939PKCS #8: Private-Key Information Content TypesCurrent
February 2026
- RFC 9919The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume EnvironmentsCurrent
July 2026
- RFC 9941Secure Shell (SSH) Key Exchange Method Using Hybrid Streamlined NTRU Prime sntrup761 and X25519 with SHA-512: sntrup761x25519-sha512Current
April 2026
- RFC 9942CBOR Object Signing and Encryption (COSE) ReceiptsCurrent
June 2026
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?