Browse Prior Art Database

Tunnel Extensible Authentication Protocol (TEAP) Version 1 (RFC7170) Disclosure Number: IPCOM000236660D
Original Publication Date: 2014-May-01
Included in the Prior Art Database: 2014-May-09

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

H. Zhou: AUTHOR [+4]


A tunnel-based Extensible Authentication Protocol (EAP) method is an EAP method that establishes a secure tunnel and executes other EAP methods under the protection of that secure tunnel. A tunnel-based EAP method can be used in any lower-layer protocol that supports EAP authentication. There are several existing tunnel-based EAP methods that use Transport Layer Security (TLS) [RFC5246] to establish the secure tunnel. EAP methods supporting this include Protected EAP (PEAP) [PEAP], EAP Tunneled Transport Layer Security (EAP-TTLS) [RFC5281], and EAP Flexible Authentication via Secure Tunneling (EAP- FAST) [RFC4851]. However, they all are either vendor-specific or informational, and the industry calls for a Standards Track tunnel- based EAP method. [RFC6678] outlines the list of requirements for a standard tunnel-based EAP method.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 1% of the total text.

Internet Engineering Task Force (IETF)                           H. Zhou Request for Comments: 7170                                 N. Cam-Winget Category: Standards Track                                     J. Salowey ISSN: 2070-1721                                            Cisco Systems                                                                 S. Hanna                                                    Infineon Technologies                                                                 May 2014

        Tunnel Extensible Authentication Protocol (TEAP) Version 1


   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

Zhou, et al.                 Standards Track                    [Page 1]
 RFC 7170                          TEAP                          May 2014

 Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    ( in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . ....