EAP-LDAP Protocol
draft-mancini-pppext-eap-ldap-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Helena Mancini | ||
| Last updated | 2003-06-26 | ||
| 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 specifies an Extensible Authentication Protocol (EAP) mechanism for a challenge-based authentication using MD5 in conjunction with the hash algorithm used to store the password within an identity store. This document defines the EAP-LDAP method, which provides one-way authentication and MD5 key generation. As a result, the EAP-LDAP method, when used by it self, is only appropriate for use on networks where physical security can be assumed. These methods SHOULD NOT be used on wireless networks, or over the Internet, unless the EAP conversation is protected. This can be accomplished using technologies such as IPsec or TLS.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)