Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)

Joseph Salowey, Lakshminath Dondeti, Vijaykrishnan Narayanan, Madjid Nakhjiri2008 · DOI

Abstract

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements.

Introduction

Extensible Authentication Protocol (EAP) is a foundational security framework used across diverse networking environments, from enterprise Wi-Fi (WPA2/3) to cellular networks. During an EAP exchange, two primary keys are typically generated: the Master Session Key (MSK), used for immediate network access, and the Extended Master Session Key (EMSK). Historically, the EMSK remained an underutilized resource. However, as network architectures evolved to require seamless hand-offs and application-layer authentication, a standardized method for deriving secondary keys from the EMSK became necessary.

RFC 5295 addresses this need by establishing a formal framework for deriving specialized "root keys" from the EMSK. This framework prevents key collisions and ensures cryptographic separation, protecting the master secret even if a derived key is compromised.

The EMSK Key Root Derivation Framework

The core of the specification is a standardized Key Derivation Function (KDF) designed to safely "slice" the EMSK for various applications. The general derivation formula is defined as:

USRK = KDF(EMSK, key label | "\0" | optional data | length)

While the framework is algorithm-agnostic, it designates HMAC-SHA-256 (specifically the PRF+ construction from IKEv2) as the default KDF. This choice provides a robust mechanism for expanding the master secret into a secure key stream.

Basic USRK derivation from EMSK

Cryptographic Principles and Hierarchy

A central tenet of RFC 5295 is cryptographic separation. It must be computationally infeasible to derive the EMSK from any sub-key, or to derive one sub-key from another. This is achieved through several strategic design choices:

  1. Unique Key Labels: Every application must use a unique ASCII string (e.g., [email protected]). This ensures that identical inputs to different applications result in distinct keys.
  2. The NULL Octet: Including a \0 (NULL octet) after the key label prevents "prefix attacks," where an attacker might use a label that is a substring of another to force a collision.
  3. Hierarchical Delegation: The framework introduces a hierarchy that supports both general Usage-Specific Root Keys (USRKs) and Domain-Specific Root Keys (DSRKs).
Hierarchical derivation including Domain-Specific Root Keys (DSRKs)

As shown in the hierarchy, DSRKs allow a home network to delegate a "branch" key to a visited domain. This local domain can then derive its own Domain-Specific Usage-Specific Root Keys (DSUSRKs) without ever gaining access to the master EMSK, facilitating secure roaming.

Impact and Standardization

The formalization of this derivation process has had a significant impact on internet security standards:

  • Standardized KDF: HMAC-SHA-256 PRF+ became the gold standard for EAP key expansion.
  • Security Baselines: The RFC recommends a minimum key length of 512 bits (64 octets) to ensure long-term cryptographic resilience.
  • Centralized Coordination: It established an IANA registry for USRK Key Labels and PRF Numbers, preventing namespace conflicts between different protocol developers.

Limitations and Future Work

While RFC 5295 provides a robust derivation mechanism, it does not address key transport. The delivery of these keys to the relevant entities must be handled by separate protocols, such as AAA (Authentication, Authorization, and Accounting) frameworks. Additionally, the derived keys are pair-wise (between a specific peer and server) and are not directly applicable to multicast or group-keying scenarios without further distribution logic. Finally, the security of the entire hierarchy remains dependent on the strength of the initial EAP method used to generate the EMSK.

Summary updated

Abstract

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements.
BibTeX
@misc{salowey2008specification,
  author = {Joseph Salowey and Lakshminath Dondeti and Vijaykrishnan Narayanan and Madjid Nakhjiri},
  title = {{Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)}},
  year = {2008},
  doi = {10.17487/rfc5295},
}
Figure