Extensible Authentication Protocol (EAP)
draft-ietf-pppext-rfc2284bis-10
| Document | Type | Expired Internet-Draft (pppext WG) | |
|---|---|---|---|
| Authors | Larry Blunk , John Vollbrecht , Bernard Aboba , James Carlson | ||
| Last updated | 2003-05-15 (latest revision 2003-01-23) | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Erik Nordmark | ||
| Send notices to | <karlfox@columbus.rr.com> | ||
https://www.ietf.org/archive/id/draft-ietf-pppext-rfc2284bis-10.txt
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
(ljb@merit.edu)
John Vollbrecht
(jrv@merit.edu pam@merit.edu)
Bernard Aboba
(Bernard_Aboba@hotmail.com)
James Carlson
(james.d.carlson@sun.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)