Standardizing on IDNA 2003 in the URL Standard

[Vint Cerf]

It seems to me that we would serve the community well if we work towards a
well-defined and timely transition to IDNA2008. It has a key property of
independence from any particular version of UNICODE (which was the primary
reason for moving in that direction). It also has a canonical
representation of domain labels which is also a powerful standardizing
element. We are all aware of the potential for some backward
incompatibility with IDNA2003 but the committee that developed IDNA2008
discussed these issues at length and obviously concluded that the features
of IDNA2008 were superior over all to the status quo. It is a disservice in
the long run to delay adoption of the newer design, especially given the
huge expansion of the TLD space - all these TLDs should be developed and
evolved on the IDNA2008 principles.

vint cerf



On Mon, Aug 19, 2013 at 11:33 AM, "Martin J. Dürst"
<duerst at it.aoyama.ac.jp>wrote:

> On 2013/08/19 21:37, Anne van Kesteren wrote:
>
>> http://lists.w3.org/Archives/**Public/www-archive/2013Aug/**0008.html<http://lists.w3.org/Archives/Public/www-archive/2013Aug/0008.html>
>> might be of interest to readers of these lists.
>>
>
> Also of interest to the IDNA list.
>
> Regards,   Martin.
> ______________________________**_________________
> Idna-update mailing list
> Idna-update at alvestrand.no
> http://www.alvestrand.no/**mailman/listinfo/idna-update<http://www.alvestrand.no/mailman/listinfo/idna-update>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.alvestrand.no/pipermail/idna-update/attachments/20130819/a227cd55/attachment.html>