FWIW, Kerberos has a similar problem (with different but similarly obscure origins); see Section 5.2.1 of RFC4120 for some background. The Kerberos WG is currently chartered to fix this, but there's not been much movement yet AFAIK.
It occurred that to me that EAP & Kerberos implementors might appreciate a common approach to both problems, if that were feasible. The techs are obviously very different, but within implementations their respective moving parts require careful choreography to provide users with a good experience. josh. > Some of the following may be needed to fix the problem: > > a. A document on NAI internationalization, updating RFC > 4282. This would address the (IMHO incorrect) punycode > encoding of the realm portion. > b. A document on EAP internationalization, updating RFC > 3748. This would cover the EAP-Response/Identity as well as > potentially giving advice on issues such as password > internationalization and internationalization of the EAP > Peer-Id and Server-Ids. > > > > > > > > > > > <http://im.live.com/Messenger/IM/Home/?source=EML_WLHM_GreaterGood> > > JANET(UK) is a trading name of The JNT Association, a company limited by guarantee which is registered in England under No. 2881024 and whose Registered Office is at Lumen House, Library Avenue, Harwell Science and Innovation Campus, Didcot, Oxfordshire. OX11 0SG _______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu