Extensible Authentication Protocol (EAP)
draft-arkko-emu-rfc3748bis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Bernard D. Aboba , Larry Blunk , John Vollbrecht , James D. Carlson , Henrik Levkowetz , Jari Arkko , John Preuß Mattsson | ||
| Last updated | 2021-08-25 (Latest revision 2021-02-21) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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), IEEE 802, or 3GPP 5G 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 3748, which in turn obsoleted RFC 2284. This document updates some of the security considerations, terms, references, the IANA considerations, and few other minor updates. A summary of the changes between this document and RFC 3748 is in Appendix A, and the changes from RFC 2284 were listed in RFC 3748.
Authors
Dr. Bernard D. Aboba
Larry Blunk
John Vollbrecht
James D. Carlson
Henrik Levkowetz
Jari Arkko
John Preuß Mattsson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)