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

["Bernard Aboba" <Bernard_Aboba@hotmail.com>]

Alan DeKok said:

"  Or, it was easier to say 'ASCII', and to avoid any unknowns that might
occur of 8-bit data is used.

  Given Stefan's test of MS-CHAP && ISO-8895-15 encodings, I think the
ASCII limitation in the spec is not matched by any similar limitations
in the code."

Unfortunately, in at least some implementations, this is not the case. 
However, I'd be interested if there exist implementations that handle
UTF-8 usernames.  That would provide a reference to test a fix against.  

"  The CUI is often created as "hash@example.com".  i.e. based off of the
User-Name.  So it's worth double-checking the effects of changing
User-Name on all down-stream uses."

Presumably the hash can be calculated on UTF-8 as well as ASCII, no? 


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