RFC 6678: Requirements for a Tunnel-Based Extensible Authentication Protocol (EAP) Method
In plain English — editorial summary, not part of the RFC
This memo defines the requirements for a tunnel-based Extensible Authentication Protocol (EAP) Method. This tunnel method will use Transport Layer Security (TLS) to establish a secure tunnel. The tunnel will provide support for password authentication, EAP authentication, and the transport of additional data for other purposes. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6678
- Published
- July 2012
- Authors
- K. Hoeper; S. Hanna; H. Zhou; J. Salowey
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 23
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6677Channel-Binding Support for Extensible Authentication Protocol (EAP) MethodsCurrent
July 2012
- RFC 6680Generic Security Service Application Programming Interface (GSS-API) Naming ExtensionsCurrent
August 2012
- RFC 6684Guidelines and Template for Defining Extensions to the Incident Object Description Exchange Format (IODEF)Current
July 2012
- RFC 6685Expert Review for Incident Object Description Exchange Format (IODEF) Extensions in IANA XML RegistryObsoleted
July 2012
- RFC 6664S/MIME Capabilities for Public Key DefinitionsCurrent
July 2012
- RFC 6696EAP Extensions for the EAP Re-authentication Protocol (ERP)Current
July 2012
- RFC 6697Handover Keying (HOKEY) Architecture DesignCurrent
July 2012
- RFC 6698The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSAUpdated
August 2012
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?