RFC 4186: Extensible Authentication Protocol Method for Global System for Mobile Communications (GSM) Subscriber Identity Modules (EAP-SIM)
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 using the Global System for Mobile Communications (GSM) Subscriber Identity Module (SIM). GSM is a second generation mobile network standard. The EAP-SIM mechanism specifies enhancements to GSM authentication and key agreement whereby multiple authentication triplets can be combined to create authentication responses and session keys of greater strength than the individual GSM triplets. The mechanism also includes network authentication, user anonymity support, result indications, and a fast re-authentication procedure. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4186
- Published
- January 2006
- Authors
- H. Haverinen; J. Salowey
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 92
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4187Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)Updated
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
- RFC 3601Text String Notation for Dial Sequences and Global Switched Telephone Network (GSTN) / E.164 AddressesCurrent
September 2003
- RFC 5002The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)Updated
August 2007
- RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 2002
- RFC 5279A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)Current
July 2008
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?