RFC 5106: The Extensible Authentication Protocol-Internet Key Exchange Protocol version 2 (EAP-IKEv2) Method
In plain English — editorial summary, not part of the RFC
This document specifies EAP-IKEv2, an Extensible Authentication Protocol (EAP) method that is based on the Internet Key Exchange (IKEv2) protocol. EAP-IKEv2 provides mutual authentication and session key establishment between an EAP peer and an EAP server. It supports authentication techniques that are based on passwords, high-entropy shared keys, and public key certificates. EAP-IKEv2 further provides support for cryptographic ciphersuite negotiation, hash function agility, identity confidentiality (in certain modes of operation), fragmentation, and an optional "fast reconnect" mode. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC5106
- Published
- February 2008
- Authors
- H. Tschofenig; D. Kroeselberg; A. Pashalidis; Y. Ohba; F. Bersani
- Status
- EXPERIMENTAL
- 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 5584RTP Payload Format for the Adaptive TRansform Acoustic Coding (ATRAC) FamilyCurrent
July 2009
- RFC 5722Handling of Overlapping IPv6 FragmentsUpdated
December 2009
- RFC 6006Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched PathsObsoleted
September 2010
- RFC 6946Processing of IPv6 "Atomic" FragmentsCurrent
May 2013
- RFC 7499Support of Fragmentation of RADIUS PacketsCurrent
April 2015
- RFC 7588A Widely Deployed Solution to the Generic Routing Encapsulation (GRE) Fragmentation ProblemCurrent
July 2015
- RFC 8724SCHC: Generic Framework for Static Context Header Compression and FragmentationUpdated
April 2020
- RFC 8824Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)Current
June 2021
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?