How various TLDs use IDN variants

Jiankang YAO yaojk at cnnic.cn
Fri Oct 12 11:00:49 CEST 2012


It is a very interesting and useful document.

it lists many Domain practices 
     4.1.  AERO . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     4.2.  ASIA . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     4.3.  BIZ  . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     4.4.  CAT  . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     4.5.  COM  . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     4.6.  COOP . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     4.7.  INFO . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     4.8.  JOBS . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.9.  MOBI . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.10. MUSEUM . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.11. NAME . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.12. NET  . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.13. ORG  . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.14. POST . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.15. PRO  . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.16. TEL  . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.17. TRAVEL . . . . . . . . . . . . . . . . . . . . . . . . . .  7
     4.18. XXX  . . . . . . . . . . . . . . . . . . . . . . . . . . .  7


are some conclusions in every practice gotten from the data analysis or from the registry's document?
It seems to be more authenticated if these conclusions can be verified confirmed from every registry.

Jiankang Yao

----- Original Message ----- 
From: "Paul Hoffman" <paul.hoffman at vpnc.org>
To: <idna-update at alvestrand.no>
Sent: Friday, October 12, 2012 6:45 AM
Subject: How various TLDs use IDN variants


> Of possible interest to this list. John Levine and I are putting together this catalog so that people talking about "variants" at the TLD level can see what is actually deployed. This is *not* an IETF effort, and will be submitted to the Independent Stream for RFC publication in the not-distant future. We're definitely interested in corrections and additions to the list of gTLD/sTLD practices.
> 
> --Paul Hoffman
> 
> Begin forwarded message:
> 
>> From: internet-drafts at ietf.org
>> Subject: I-D Action: draft-levine-tld-variant-01.txt
>> Date: October 11, 2012 3:26:13 PM PDT
>> To: i-d-announce at ietf.org
>> Reply-To: internet-drafts at ietf.org
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> 
>> 
>> Title           : Variants in Second-Level Names Registered in Top Level Domains
>> Author(s)       : John Levine
>>                          Paul Hoffman
>> Filename        : draft-levine-tld-variant-01.txt
>> Pages           : 10
>> Date            : 2012-10-11
>> 
>> Abstract:
>>   IDNA [RFC5890] provides a method to map a subset of names written in
>>   Unicode into the DNS.  Some languages allow a particular name to be
>>   written in multiple ways that are represented differently in IDNA,
>>   known as "variants".  This document surveys the approaches that
>>   ICANN-contracted top level domains have taken to the registration and
>>   provisioning of variant names.  This document is not (and will not
>>   be) a product of the IETF, and does not (and will not) propose any
>>   method to make variants work "correctly".
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-levine-tld-variant
>> 
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-levine-tld-variant-01
>> 
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-levine-tld-variant-01
> 
> _______________________________________________
> Idna-update mailing list
> Idna-update at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update


More information about the Idna-update mailing list