A Container Type for the Extensible Authentication Protocol (EAP)
draft-hiller-eap-tlv-01

Document Type Expired Internet-Draft (individual)
Last updated 2003-05-29
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hiller-eap-tlv-01.txt

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 (tom.hiller@lucent.com)
Ashwin Palekar (ashwinp@microsoft.com)
Glen Zorn (glenzorn@hotmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)