Hello,
I'm currently trying to figure out what would happen if a AAA roaming
consortium (802.1X based, using EAP and RADIUS) were to use IDNs in its
NAIs, i.e. a user name like [EMAIL PROTECTED]
I was kindof expecting to see UTF-8 encoded User-Name attributes showing
up at the RADIUS server, s
Hi,
> RFC 3748 Section 5.1 allows additional data to be transmitted after
> the NUL in an Identity Request. This could perhaps be leveraged to send
> a string such as "UTF-8", which could indicate to the supplicant that
> the server is requesting UTF-8 encoding.
Hmm... In 802.1X, the EAP-Reque
Stefan Winter wrote:
> I'm currently trying to figure out what would happen if a AAA roaming
> consortium (802.1X based, using EAP and RADIUS) were to use IDNs in its
> NAIs, i.e. a user name like [EMAIL PROTECTED]
On a related note, there was discussion in Dublin about updating RFC
4282 for i
Stefan Winter wrote:
> Hmm... In 802.1X, the EAP-Request/Identity is sent by the authenticator,
> which, in a scenario with multiple home authentication servers and
> realms, does not necessarily know which home server expects which
> encoding. A negotiation would be very nice, but I doubt it can w
Hi,
> The alternative is for supplicants to simply start using UTF-8. It's
> likely a good idea, in any case.
>
Yes, I'd be very happy if supplicants did that. Obviously some refrained
from doing it so far, and I don't think there is a lot of incentive to
make them change their code if we
