EAP Re-authentication Protocol

Description

The EAP Re-authentication Protocol (ERP) is a security protocol defined within the Extensible Authentication Protocol (EAP) framework, standardized by the IETF and adopted by 3GPP. Its primary function is to perform a lightweight re-authentication of an already authenticated peer (e.g., a UE) when it moves between access points or needs to refresh its security context, without executing the computationally intensive and time-consuming full EAP method again. ERP achieves this by leveraging cryptographic material derived from the initial, full EAP authentication, specifically the Master Session Key (MSK) and Extended Master Session Key (EMSK). From these keys, a Re-authentication Root Key (rRK) and subsequently a Re-authentication Integrity Key (rIK) and Re-authentication Encryption Key (rEK) are derived, forming a secure basis for the abbreviated exchange.

Architecturally, ERP involves three entities: the peer (UE), the authenticator (e.g., an access point or eNodeB/gNodeB), and the backend authentication server (e.g., an AAA server). The protocol operates by the peer initiating a re-authentication request using a dedicated EAP method, EAP-Initiate/Re-auth. This request is processed locally by the authenticator if it holds the necessary rIK, or is forwarded to the backend server. The exchange involves a minimal number of messages, typically just a request and a response, which include cryptographically protected sequence numbers and identifiers to prevent replay attacks. Successful completion results in the derivation of fresh keying material (a new MSK) for the new session, ensuring forward secrecy.

ERP's role in the 3GPP ecosystem is integral to enabling secure and fast handovers, particularly in scenarios involving non-3GPP access (like Wi-Fi) interworking with the 3GPP core, as defined in Access Network Discovery and Selection Function (ANDSF) and Non-3GPP InterWorking Function (N3IWF) architectures. It is a key component for optimizing the performance of authentication, authorization, and accounting (AAA) procedures during mobility events. By drastically reducing the authentication latency from potentially hundreds of milliseconds to tens of milliseconds, ERP directly contributes to improved user experience for latency-sensitive applications and supports the seamless mobility requirements of 5G and beyond systems.

Purpose & Motivation

ERP was created to address the significant performance bottleneck posed by full EAP authentication during frequent mobility events. In mobile networks, especially with the proliferation of heterogeneous access (e.g., switching between cellular and Wi-Fi), a device may need to re-authenticate often. A full EAP exchange involves multiple round-trips to a potentially distant AAA server, introducing substantial latency and signaling load on both the radio and core networks. This could severely degrade service continuity, causing perceptible interruptions in voice or video calls during handovers.

The motivation stemmed from the need for a standardized, cryptographically sound method to re-establish trust and session keys quickly. Prior to ERP, solutions were often vendor-specific or relied on stateful context transfer between network nodes, which had scalability and security limitations. ERP provides a stateless, protocol-based solution where the security of the re-authentication is rooted in the keys from the initial authentication. Its development was driven by requirements from 3GPP's work on System Architecture Evolution (SAE) and later 5G, which mandate efficient secure mobility across multiple access technologies.

By solving the re-authentication latency problem, ERP enables practical implementation of features like seamless offload to trusted and untrusted non-3GPP networks, fast reconnection after brief disconnections, and efficient support for massive numbers of IoT devices that may frequently sleep and wake. It is a foundational element for achieving the low-latency and high-reliability goals of modern cellular systems.

Key Features

• Enables cryptographically secure re-authentication without full EAP method execution
• Derives fresh session keys (MSK) from a Re-authentication Root Key (rRK)
• Utilizes the EAP-Initiate/Re-auth protocol for the exchange
• Minimizes authentication latency and signaling overhead during handovers
• Supports mobility between 3GPP and non-3GPP access networks
• Provides replay protection through sequence numbers and cryptographic binding

Evolution Across Releases

Defining Specifications