RFC 9930 on Tunnel Extensible Authentication Protocol (TEAP) Version 1
rfc-editor@rfc-editor.org Fri, 27 February 2026 23:54 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 763C3C008D55; Fri, 27 Feb 2026 15:54:54 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 5BE4FC000CC4; Fri, 27 Feb 2026 15:54:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9930 on Tunnel Extensible Authentication Protocol (TEAP) Version 1
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20260227235454.5BE4FC000CC4@rfcpa.rfc-editor.org>
Date: Fri, 27 Feb 2026 15:54:54 -0800
Message-ID-Hash: K3LZO5LSCGA354IYTB5ORUTVUPJPFGW4
X-Message-ID-Hash: K3LZO5LSCGA354IYTB5ORUTVUPJPFGW4
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, emu@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/9qy_e1QL3WPt1njMJNHPamvbeNA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
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: alan.dekok@inkbridge.io
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 rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team