Considerations regarding the correct use of EAP-Response/Identity
draft-ietf-radext-populating-eapidentity-01

Document Type Expired Internet-Draft (radext WG)
Last updated 2017-01-09 (latest revision 2016-07-08)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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-ietf-radext-populating-eapidentity-01.txt

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. One of these workarounds is a new requirement for EAP peers that the use of UTF-8 is required for the content of EAP-Response/Identity (which updates RFC3748).

Authors

Stefan Winter (stefan.winter@restena.lu)

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