[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 75: Why Not UTF-8 For Realm, Too?

I think there's more to it than just the encoding.
Allowed characters, for instance. So if we use UTF-8
we'd be saying "everything that is allowed in an IDN
but represented in UTF-8 format". I'm not sure how
easy that is.

--jari

Bernard Aboba wrote:

Issue 75: Why Not UTF-8 For Realm, Too?
Submitter name: Avi Lior
Submitter email address: avi@bridgewatersystems.com
Date first submitted: March 6, 2005
Reference:
Document: RFC2486bis
Comment type: T
Priority: S
Section:  Various
Rationale/Explanation of issue:

When a RADIUS proxy undecorates the NAI, the current document may require
translation when a realm name moves between the userid portion and the
realm portion. For example, when intl_name.com!avi@idn_realm.com
is redecorated to avi@intl_name.com.  In the fomer construction,
intl_name.com is in UTF-8, and in the later, intl_name.com needs to
be translated to IDNA.

Why not just specify the entire NAI in UTF-8? Then, say that if a proxy
needs to utilize the realm name within DNS, it will convert it to an IDN.
Doesn't that make more sense? Existing link layers (e.g. EAP
Request/Response-Identity messages) can carry UTF-8 just fine.


--
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/>






--
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/>