RFC 5295: Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)
In plain English — editorial summary, not part of the RFC
The Extensible Authentication Protocol (EAP) defined the Extended Master Session Key (EMSK) generation, but reserved it for unspecified future uses. This memo reserves the EMSK for the sole purpose of deriving root keys. Root keys are master keys that can be used for multiple purposes, identified by usage definitions. This document also specifies a mechanism for avoiding conflicts between root keys by deriving them in a manner that guarantees cryptographic separation. Finally, this document also defines one such root key usage: Domain-Specific Root Keys are root keys made available to and used within specific key management domains. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5295
- Published
- August 2008
- Authors
- J. Salowey; L. Dondeti; V. Narayanan; M. Nakhjiri
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6696EAP Extensions for the EAP Re-authentication Protocol (ERP)Current
July 2012
- RFC 5296EAP Extensions for EAP Re-authentication Protocol (ERP)Obsoleted
August 2008
- RFC 5289TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)Updated
August 2008
- RFC 5288AES Galois Counter Mode (GCM) Cipher Suites for TLSUpdated
August 2008
- RFC 5280Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileUpdated
May 2008
- RFC 5275CMS Symmetric Key Management and DistributionCurrent
June 2008
- RFC 5274Certificate Management Messages over CMS (CMC): Compliance RequirementsObsoleted
June 2008
- RFC 5273Certificate Management over CMS (CMC): Transport ProtocolsObsoleted
June 2008
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?