Standardizing on IDNA 2003 in the URL Standard

Gervase Markham gerv at
Thu Aug 22 14:59:55 CEST 2013

On 22/08/13 13:17, Anne van Kesteren wrote:
> On Thu, Aug 22, 2013 at 12:38 PM, Mark Davis ☕ <mark at> wrote:
>> There are three major options for clients:
>> 1 Move immediately to IDNA2008.
>> 2 Stay on IDNA2003.
>> 3 Move to TR46+IDNA2008 as a transition to IDNA2008.
>> Recent history has shown that the major clients are reluctant to do #1
>> because of compatibility concerns. I don't think anyone really wants #2,
>> because it has an archaic Unicode version, but people are sticking with that
>> if they see #1 as the only other choice.
>> That effectively leaves #3. And certainly major players like IE have shown
>> that it can be deployed effectively.
> 2 as deployed is not stuck on an archaic Unicode version.

Are you sure that "as deployed" is interoperable, or have different
browsers done the "add new Unicode to IDNA2003" step differently?

Have you been arguing for 2 because you don't want 1? I'm not sure
anyone's been arguing for 1. It's always been about 3.


More information about the Idna-update mailing list