Skip to main content

Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA')
RFC 5448

Revision differences

Document history

Date By Action
2021-05-20
Jenny Bui Posted related IPR disclosure Qualcomm Incorporated's Statement about IPR related to RFC 5448
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This specification defines a new EAP method, EAP-AKA', which is a small revision of the EAP-AKA …
Received changes through RFC Editor sync (changed abstract to 'This specification defines a new EAP method, EAP-AKA', which is a small revision of the EAP-AKA (Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement) method. The change is a new key derivation function that binds the keys derived within the method to the name of the access network. The new key derivation mechanism has been defined in the 3rd Generation Partnership Project (3GPP). This specification allows its use in EAP in an interoperable manner. In addition, EAP-AKA' employs SHA-256 instead of SHA-1.

This specification also updates RFC 4187, EAP-AKA, to prevent bidding down attacks from EAP-AKA'. This memo provides information for the Internet community.')
2015-10-14
(System) Notify list changed from jari.arkko@piuha.net, pasi.eronen@nokia.com, vesa.lehtovirta@ericsson.com, draft-arkko-eap-aka-kdf@ietf.org to (None)
2009-05-26
Cindy Morgan State Changes to RFC Published from RFC Ed Queue by Cindy Morgan
2009-05-26
Cindy Morgan [Note]: 'RFC 5448' added by Cindy Morgan
2009-05-22
(System) RFC published