How various TLDs use IDN variants

[Paul Hoffman]

On Nov 7, 2012, at 11:10 AM, Yoshiro YONEYA <yoshiro.yoneya at jprs.co.jp> wrote:

> I noticed new version (-03) had been published and ccTLDs were included 
> in the document.  I checked JP section and had a few comments.  Please 
> see below.
> 
>> 5.7.  JP
>> 
>>   The .JP TLD (for Japan) publishes a policy page [JPPOLICY].  It has
>>   published an IDN table for the Japanese language in [IANAIDN].  The
>>   policy says that it will block registration of variants.
> 
> JP's IDN table does not define variants (i.e. each code point has no 
> variants) so it says nothing about variants.  

This may be a language issue, but the IANA table says:

   This document defines Japanese character variant table for .JP registry.

So, it says *something* about variants, but then (now that I read it) doesn't list any variants.

> The last sentence would be:
> 
>  Each code point in that table defines no variants, and therefore 
>  the policy says nothing about variants, which means there are no 
>  variants in registration or resolution.

So, that's not completely accurate. Instead, I believe that a statement that we can make from your IANA table is:

Each code point in that table defines no variants, which means there are no 
variants in registration or resolution.

Please let me know if this sentence is not acceptable.

>>   [JPPOLICY]
>>              JPNIC, "Technology bylaws regarding generic domain name
>>              registration JP", July 2012,
>>              <http://jprs.jp/doc/rule/saisoku-1-wideusejp.html>.
> 
> Owner and publisher of the policy document is JPRS, not JPNIC. 
> Please correct it as follows.
> 
>  JPRS, "Technical Specification of General-use JP Domain Name", 
>  July 2012, <http://jprs.jp/doc/rule/saisoku-1-wideusejp.html>.

Whoops, my fault. Fixed.

--Paul Hoffman