Information on RFC 3748 » RFC Editor (original) (raw)

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 2284

Updated by:

RFC 5247, RFC 7057

Authors:

B. Aboba
L. Blunk
J. Vollbrecht
J. Carlson
H. Levkowetz, Ed.

Stream:

IETF

Source:

eap (int)

Cite this RFC: TXT | XML | BibTeX

DOI: https://doi.org/10.17487/RFC3748

Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org

Other actions:View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 3748

Abstract

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]

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.