RFC 3310: Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)
In plain English — editorial summary, not part of the RFC
The Hypertext Transfer Protocol (HTTP) Authentication Framework includes two authentication schemes: Basic and Digest. Both schemes employ a shared secret based mechanism for access authentication. The Authentication and Key Agreement (AKA) mechanism performs user authentication and session key distribution in Universal Mobile Telecommunications System (UMTS) networks. AKA is a challenge- response based mechanism that uses symmetric cryptography. This memo specifies an AKA based one-time password generation mechanism for HTTP Digest access authentication.
Document record
- Document ID
- RFC3310
- Published
- September 2002
- Authors
- A. Niemi; J. Arkko; V. Torvinen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 18
- 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 4215Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) NetworksCurrent
October 2005
- 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 3311The Session Initiation Protocol (SIP) UPDATE MethodCurrent
October 2002
- RFC 3312Integration of Resource Management and Session Initiation Protocol (SIP)Updated
October 2002
- RFC 3313Private Session Initiation Protocol (SIP) Extensions for Media AuthorizationCurrent
January 2003
- RFC 3319Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) ServersCurrent
July 2003
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?