Considerations regarding the correct use of EAP-Response/Identity
draft-winter-radext-populating-eapidentity-01
Document | Type |
Expired Internet-Draft
(candidate for radext WG)
Expired & archived
|
|
---|---|---|---|
Author | Stefan Winter | ||
Last updated | 2015-10-14 (Latest revision 2014-10-27) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Call For Adoption By WG Issued | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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
There are some subtle considerations for an EAP peer regarding the content of the EAP-Response/Identity packet when authenticating with EAP to an EAP server. This document describes two such considerations and suggests workarounds to the associated problems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)