Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare

2008-09-19 Thread Alan DeKok
Bernard Aboba wrote: > [BA] RFC 4282 actually proposes that the realm portion of the NAI be > encoded in punycode, not UTF-8. That's just wrong. No AAA client or server does that. At the last IETF, I had proposed in a hallway conversation, to update portions RFC 4282 to describe what impleme

Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare

2008-09-19 Thread Bernard Aboba
Alan DeKok said: "> [BA] RFC 4282 actually proposes that the realm portion of the NAI be > encoded in punycode, not UTF-8. That's just wrong. [BA] I agree. I don't know of any EAP peers that encode the NAI this way (although, based on Stefan's tests, they may not use UTF-8 either). > ...it

Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare

2008-09-19 Thread Alan DeKok
Bernard Aboba wrote: > [BA] I agree. I don't know of any EAP peers that encode the NAI this way > (although, based on Stefan's tests, they may not use UTF-8 either). I think the correct term is "memcpy". > [BA] Interesting. NAIs and e-mail addresses are similar; ... Often the same. Lever