EAP shared key methods documentation template
draft-bersani-eap-sharedkeymethods-doctemplate-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Florent Bersani | ||
| Last updated | 2004-03-11 | ||
| 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 proposes a template for authors of EAP methods that rely on shared keys, to document their work. Since EAP methods have proliferated but only 4 are currently standardized and since no simple shared key EAP method seems to be widely available to replace EAP-MD5 that has been deprecated for security reasons, this template is the first step towards standardizing such an EAP method. This document is indeed intended to help gather information on the existing related work before requesting that a new work item be opened at IETF to standardize a replacement for EAP-MD5.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)