RFC 6124: An EAP Authentication Method Based on the Encrypted Key Exchange (EKE) Protocol
In plain English — editorial summary, not part of the RFC
The Extensible Authentication Protocol (EAP) describes a framework that allows the use of multiple authentication mechanisms. This document defines an authentication mechanism for EAP called EAP-EKE, based on the Encrypted Key Exchange (EKE) protocol. This method provides mutual authentication through the use of a short, easy to remember password. Compared with other common authentication methods, EAP-EKE is not susceptible to dictionary attacks. Neither does it require the availability of public-key certificates. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6124
- Published
- February 2011
- Authors
- Y. Sheffer; G. Zorn; H. Tschofenig; S. Fluhrer
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 33
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5998An Extension for EAP-Only Authentication in IKEv2Current
September 2010
- RFC 5931Extensible Authentication Protocol (EAP) Authentication Using Only a PasswordUpdated
August 2010
- RFC 5922Domain Certificates in the Session Initiation Protocol (SIP)Current
June 2010
- RFC 6467Secure Password Framework for Internet Key Exchange Version 2 (IKEv2)Current
December 2011
- RFC 8492Secure Password Ciphersuites for Transport Layer Security (TLS)Current
February 2019
- RFC 9337Generating Password-Based Keys Using the GOST AlgorithmsCurrent
December 2022
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?