metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3748: Extensible Authentication Protocol (EAP)

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

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

This document defines the Extensible Authentication Protocol (EAP), an authentication framework which supports multiple authentication methods. EAP typically runs directly over data link layers such as Point-to-Point Protocol (PPP) or IEEE 802, without requiring IP. EAP provides its own support for duplicate elimination and retransmission, but is reliant on lower layer ordering guarantees. Fragmentation is not supported within EAP itself; however, individual EAP methods may support this. This document obsoletes RFC 2284. A summary of the changes between this document and RFC 2284 is available in Appendix A. [STANDARDS-TRACK]

Document record

Document ID
RFC3748
Published
June 2004
Authors
B. Aboba; L. Blunk; J. Vollbrecht; J. Carlson; H. Levkowetz
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
67
Also known as
—
Obsoletes:
RFC 2284
Updated by:
RFC 5247, RFC 7057

Topics

Referenced by

2 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/3748-extensible-authentication-protocol-eap