[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Implementation Survey: How does your EAP peer/RADIUS proxy handle internationalization?
Bernard Aboba wrote:
I concur with the sentiment, but I wonder if the text in the NAIbis
draft, that purports to add internationalization support, has already
awakened that particular canine? :-)
Based on the responses, sending NAIs in UTF-8 within the
EAP-Response/Identity will not awaken the canine.
But I'm still concerned that we are not doing any of
the normalization and mapping stuff that seems to
be necessary in order to get comparisons right.
I agree that it should not be done by proxies. But it
should be done at the time you enter the stuff to the
db, or type the NAI to the client machine. But it seemed
like implementations are not doing that either.
From what we've heard it sounds like RADIUS proxy implementations handle
the User-Name attribute as opaque octets, and that may be all we should
assume.
Avi's Issue 75 (leave the NAI in UTF-8) seems to be compatible with that
perspective.
I suppose the other alternative, assuming the realms are
idn-unaware name slots could also be argued to be compatible
with that. Except in the ! case but there we are not treating
the attribute as opaque octets anyway.
--Jari
--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>