RFC 4187: Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)
In plain English — editorial summary, not part of the RFC
This document specifies an Extensible Authentication Protocol (EAP) mechanism for authentication and session key distribution that uses the Authentication and Key Agreement (AKA) mechanism. AKA is used in the 3rd generation mobile networks Universal Mobile Telecommunications System (UMTS) and CDMA2000. AKA is based on symmetric keys, and typically runs in a Subscriber Identity Module, which is a UMTS Subscriber Identity Module, USIM, or a (Removable) User Identity Module, (R)UIM, similar to a smart card. EAP-AKA includes optional identity privacy support, optional result indications, and an optional fast re-authentication procedure. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4187
- Published
- January 2006
- Authors
- J. Arkko; H. Haverinen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 79
- 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 4215Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) NetworksCurrent
October 2005
- RFC 3310Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)Current
September 2002
- RFC 7254A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)Current
May 2014
- RFC 7255Using the International Mobile station Equipment Identity (IMEI) Uniform Resource Name (URN) as an Instance IDCurrent
May 2014
- RFC 4186Extensible Authentication Protocol Method for Global System for Mobile Communications (GSM) Subscriber Identity Modules (EAP-SIM)Current
January 2006
- RFC 4281The Codecs Parameter for "Bucket" Media TypesObsoleted
December 2005
- RFC 4396RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed TextCurrent
February 2006
- RFC 4457The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-Header)Current
April 2006
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?