Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- To: "Bernard Aboba" <bernard_aboba at hotmail.com>, <emu at ietf.org>
- Subject: Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- From: "Josh Howlett" <Josh.Howlett at ja.net>
- Date: Thu, 18 Sep 2008 10:26:19 +0100
- Cc: Josh Howlett <Josh.Howlett at ja.net>
- Delivered-to: ietfarch-emu-web-archive at core3.amsl.com
- Delivered-to: emu at core3.amsl.com
- In-reply-to: <BLU137-W152ECA2F73266AA051FBEB934F0 at phx.gbl>
- List-archive: <http://www.ietf.org/pipermail/emu>
- List-help: <mailto:emu-request@ietf.org?subject=help>
- List-id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
- List-post: <mailto:emu@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
- References: <BLU137-W152ECA2F73266AA051FBEB934F0 at phx.gbl>
- Sender: emu-bounces at ietf.org
- Thread-index: AckZOKFYfc+UhecySPCGP/6fUDunCQANb/6w
- Thread-topic: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
FWIW, Kerberos has a similar problem (with different but similarly
obscure origins); see Section 5.2.1 of RFC4120 for some background. The
Kerberos WG is currently chartered to fix this, but there's not been
much movement yet AFAIK.
It occurred that to me that EAP & Kerberos implementors might appreciate
a common approach to both problems, if that were feasible. The techs are
obviously very different, but within implementations their respective
moving parts require careful choreography to provide users with a good
experience.
josh.
> Some of the following may be needed to fix the problem:
>
> a. A document on NAI internationalization, updating RFC
> 4282. This would address the (IMHO incorrect) punycode
> encoding of the realm portion.
> b. A document on EAP internationalization, updating RFC
> 3748. This would cover the EAP-Response/Identity as well as
> potentially giving advice on issues such as password
> internationalization and internationalization of the EAP
> Peer-Id and Server-Ids.
>
>
>
>
>
>
>
>
>
>
> <http://im.live.com/Messenger/IM/Home/?source=EML_WLHM_GreaterGood>
>
>
JANET(UK) is a trading name of The JNT Association, a company limited
by guarantee which is registered in England under No. 2881024
and whose Registered Office is at Lumen House, Library Avenue,
Harwell Science and Innovation Campus, Didcot, Oxfordshire. OX11 0SG
_______________________________________________
Emu mailing list
Emu at ietf.org
https://www.ietf.org/mailman/listinfo/emu
- Prev by Date:
Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Next by Date:
Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Previous by thread:
Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Next by thread:
Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Index(es):
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.