RFC - 3748
Extensible Authentication Protocol (EAP)
| Original: | ftp://ftp.isi.edu/in-notes/rfc3748.txt |
|---|---|
| Authors: | B. Aboba [Microsoft], L. Blunk [Merit Network, Inc], J. Vollbrecht [Vollbrecht Consulting LLC], J. Carlson [Sun], H. Levkowetz [ipUnplugged] |
| Date: | June 2004 |
| Category: | Proposed Standard |
| Obsoletes: | |
|---|---|
| RFC-2284 | PPP Extensible Authentication Protocol (EAP) (Obsoleted by RFC-3748prop) (Updated by RFC-2484prop) |
| Referred by: | 22 RFC |
| Refers to: | 27 RFC |
Status
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2004).
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.
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry
