A Container Type for the Extensible Authentication Protocol (EAP)
draft-hiller-eap-tlv-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tom Hiller , Ashwin Palekar , Glen Zorn | ||
| Last updated | 2003-05-29 | ||
| 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
The Extensible Authentication Protocol (EAP), defined in RFC 2284, provides for support of multiple authentication methods. While EAP was originally created for use with PPP, it has since been adopted for use with IEEE 802.1X 'Network Port Authentication'. Since its deployment, a number of weaknesses in EAP have become apparent. These include the lack of protection for, and acknowledgement of Success and Failure messages.
Authors
Tom Hiller
Ashwin Palekar
Glen Zorn
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)