Extensible Authentication Protocol (EAP)
draft-ietf-pppext-rfc2284bis-10
| Document | Type |
Expired Internet-Draft
(pppext WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Larry Blunk , John Vollbrecht , Dr. Bernard D. Aboba , James D. Carlson | ||
| Last updated | 2003-05-15 (Latest revision 2003-01-23) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Erik Nordmark | ||
| Send notices to | <karlfox@columbus.rr.com> |
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 mechanisms. EAP typically runs directly over the link layer without requiring IP, but is reliant on lower layer ordering guarantees as in PPP and IEEE 802. EAP does provide its own support for duplicate elimination and retransmission. Fragmentation is not supported within EAP itself; however, individual EAP methods may support this. While EAP was originally developed for use with PPP, it is also now in use with IEEE 802. This document obsoletes RFC 2284.
Authors
Larry Blunk
John Vollbrecht
Dr. Bernard D. Aboba
James D. Carlson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)