Hi,
> Section 3:
>
>... EAP-
>Response/Identity does not carry encoding information itself, so a
>conversion between a non-UTF-8 encoding and UTF-8 is not possible for
>the AAA entity doing the EAP-Response/Identity to User-Name copying.
>
> I'm unsure about this. The EAP-Resp
Stefan Winter wrote:
> Unfortunately, that is not how I read the EAP spec. RFC3748 section 5.1
> on the "Identity" packet does not mention UTF-8 for the *Response* at all.
>
> It mentions that the *request* MAY contain displayable text, which needs
> to be UTF-8 if present.
That's worse than I
>
>> Interesting thought, and a bit complex. I suggest we discuss this when
>> the draft gets adopted in ... "some" working group. Suggestions welcome
>>:-)
>
> I'd support a "roaming inter-operations" WG. Some of the documents
>now in RADEXT could move there, and maybe DIME. This document could
