Extensible Authentication Protocol

Description

The Extensible Authentication Protocol (EAP) is an authentication framework, originally defined in IETF RFC 3748 and widely incorporated into 3GPP standards, that provides a flexible mechanism for securely authenticating a client (or UE) to a network. It operates as a lock-step request-response protocol carried within a lower-layer transport protocol, such as PPP, IEEE 802.1X (EAP over LAN - EAPOL), or directly within 3GPP-specific signaling like NAS (Non-Access Stratum) or DIAMETER. The core architecture involves three entities: the EAP peer (the client requesting access), the EAP authenticator (the network access point, e.g., a WLAN AP or 3GPP AAA Proxy), and the EAP server (the backend authentication server, often an AAA server like HSS/UDM or a separate RADIUS server).

EAP works by allowing the authenticator to act as a pass-through. The authenticator receives an EAP-Start or EAP-Response/Identity from the peer, encapsulates it, and forwards it to the EAP server. The EAP server then selects an appropriate EAP method (e.g., EAP-AKA, EAP-AKA', EAP-TLS, EAP-SIM) based on policy and the peer's identity. The subsequent EAP conversation—a series of method-specific request/response messages—occurs directly between the peer and the server, transparently relayed by the authenticator. This conversation performs the mutual authentication and derives session keys. Upon successful authentication, the EAP server sends an EAP-Success message to the authenticator, along with the derived Master Session Key (MSK) and Extended MSK (EMSK). The authenticator uses the MSK to derive necessary link-layer encryption keys.

In 3GPP networks, EAP's role is pivotal, especially for integrating non-3GPP access networks (like WLAN, Wi-Fi, and fixed access) with the 3GPP core. It forms the basis for authentication in trusted and untrusted non-3GPP access to the EPS and 5GC, as defined in S2a, S2b, and N3IWF interfaces. Within the core, the Authentication Server Function (AUSF) in 5GC often acts as the EAP server, interacting with the UDM for credential verification. EAP methods like EAP-AKA and EAP-AKA' are used for authentication leveraging USIM credentials, providing seamless mobility and security consistency across different access technologies. EAP thus provides a unified, extensible security layer that is independent of the underlying link technology.

Purpose & Motivation

EAP was created to solve the problem of having multiple, incompatible authentication mechanisms for different network access technologies. Prior to its adoption, each link-layer technology (e.g., dial-up PPP, wired Ethernet, wireless LAN) often had its own proprietary or limited authentication scheme. This fragmentation hindered seamless roaming and consistent security policy enforcement across heterogeneous networks. The IETF developed EAP as a general framework to decouple the authentication method from the specific physical and link-layer protocols, enabling a single, flexible authentication process to run over any link layer capable of carrying EAP frames.

3GPP adopted EAP to address the critical need for secure, unified authentication mechanisms, particularly for interworking with non-3GPP access networks (e.g., WLAN hotspots). As cellular operators began offering seamless access across cellular and Wi-Fi networks, they required an authentication method that could leverage the strong credentials stored in the USIM/SIM card. EAP-AKA (and later EAP-AKA') was developed within the IETF/3GPP collaboration to meet this need, allowing a UE to authenticate to a non-3GPP network using its 3GPP subscription identity and keys. This solved the problem of secure credential reuse and provided a standardized, extensible foundation for future authentication methods, supporting the evolution towards converged access in 4G and 5G.