RFC 7170: Tunnel Extensible Authentication Protocol (TEAP) Version 1
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9930.
Current version: 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.
Document record
- Document ID
- RFC7170
- Published
- May 2014
- Authors
- H. Zhou; N. Cam-Winget; J. Salowey; S. Hanna
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 101
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7057Update to the Extensible Authentication Protocol (EAP) Applicability Statement for Application Bridging for Federated Access Beyond Web (ABFAB)Current
December 2013
- RFC 7029Extensible Authentication Protocol (EAP) Mutual Cryptographic BindingCurrent
October 2013
- RFC 6630EAP Re-authentication Protocol Extensions for Authenticated Anticipatory Keying (ERP/AAK)Current
June 2012
- RFC 7831Application Bridging for Federated Access Beyond Web (ABFAB) ArchitectureCurrent
May 2016
- RFC 7832Application Bridging for Federated Access Beyond Web (ABFAB) Use CasesCurrent
May 2016
- RFC 7833A RADIUS Attribute, Binding, Profiles, Name Identifier Format, and Confirmation Methods for the Security Assertion Markup Language (SAML)Current
May 2016
- RFC 5749Distribution of EAP-Based Keys for Handover and Re-AuthenticationCurrent
March 2010
- RFC 5433Extensible Authentication Protocol - Generalized Pre-Shared Key (EAP-GPSK) MethodCurrent
February 2009
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?