UpdatedPROPOSED STANDARDIETF stream

RFC 5247: Extensible Authentication Protocol (EAP) Key Management Framework

Still current, but amended. Parts of this document are changed or extended by RFC 8940. Read both.

In plain English — editorial summary, not part of the RFC

The Extensible Authentication Protocol (EAP), defined in RFC 3748, enables extensible network access authentication. This document specifies the EAP key hierarchy and provides a framework for the transport and usage of keying material and parameters generated by EAP authentication algorithms, known as "methods". It also provides a detailed system-level security analysis, describing the conditions under which the key management guidelines described in RFC 4962 can be satisfied. [STANDARDS-TRACK]

Document record

Document ID
RFC5247
Published
August 2008
Authors
B. Aboba; D. Simon; P. Eronen
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
79
Also known as
Updates:
RFC 3748
Updated by:
RFC 8940

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/5247-extensible-authentication-protocol-eap-key-management-framework