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

RE: Implementation Survey: How does your EAP peer/RADIUS proxy handle internationalization?

To: "Nelson, David" <dnelson@enterasys.com>
Subject: RE: Implementation Survey: How does your EAP peer/RADIUS proxy handle internationalization?
From: Bernard Aboba <aboba@internaut.com>
Date: Wed, 11 May 2005 11:33:21 -0700 (PDT)
Cc: radiusext@ops.ietf.org
In-reply-to: <2A5E4540D4D5934D9A1E7E0B0FDB2D6901032329@MAANDMBX2.ets.enterasys.com>
References: <2A5E4540D4D5934D9A1E7E0B0FDB2D6901032329@MAANDMBX2.ets.enterasys.com>

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

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.

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

Follow-Ups:
- Re: Implementation Survey: How does your EAP peer/RADIUS proxy handle internationalization?
  - From: Jari Arkko <jari.arkko@piuha.net>

References:
- RE: Implementation Survey: How does your EAP peer/RADIUS proxy handle internationalization?
  - From: "Nelson, David" <dnelson@enterasys.com>

Prev by Date: RE: Implementation Survey: How does your EAP peer/RADIUS proxy handle internationalization?
Next by Date: Update on the IEEE 802 extensions document?
Previous by thread: RE: Implementation Survey: How does your EAP peer/RADIUS proxy handle internationalization?
Next by thread: Re: Implementation Survey: How does your EAP peer/RADIUS proxy handle internationalization?
Index(es):
- Date
- Thread