metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 5216: The EAP-TLS Authentication Protocol

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

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

The Extensible Authentication Protocol (EAP), defined in RFC 3748, provides support for multiple authentication methods. Transport Layer Security (TLS) provides for mutual authentication, integrity-protected ciphersuite negotiation, and key exchange between two endpoints. This document defines EAP-TLS, which includes support for certificate-based mutual authentication and key derivation. This document obsoletes RFC 2716. A summary of the changes between this document and RFC 2716 is available in Appendix A. [STANDARDS-TRACK]

Document record

Document ID
RFC5216
Published
March 2008
Authors
D. Simon; B. Aboba; R. Hurst
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
34
Also known as
—
Obsoletes:
RFC 2716
Updated by:
RFC 8996, RFC 9190, RFC 9965

Topics

Referenced by

3 later RFCs formally update or obsolete 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/5216-the-eap-tls-authentication-protocol