Hi, > RFC 3748 Section 5.1 allows additional data to be transmitted after > the NUL in an Identity Request. This could perhaps be leveraged to send > a string such as "UTF-8", which could indicate to the supplicant that > the server is requesting UTF-8 encoding.
Hmm... In 802.1X, the EAP-Request/Identity is sent by the authenticator, which, in a scenario with multiple home authentication servers and realms, does not necessarily know which home server expects which encoding. A negotiation would be very nice, but I doubt it can work that way in a 802.1X deployment. Greetings, Stefan -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473 _______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
