Back

15(b) Describe the process used for development of the IDN tables submitted, including consultations and sources used

gTLDFull Legal NameE-mail suffixDetail
.닷넷VeriSign Sarlverisign.comView
Verisign will leverage its mature shared registration system to provide services for the KOREAN_TRANSLITERATION_OF_NET gTLD. Verisign’s registration software is in compliance with all current IDN standards, including ICANN’s IDN Guidelines, as well as The Internationalized Domain Names in Applications (IDNA 2008) specification, published by the IETF as RFC 5891.

The IDN tables provided herein represent Unicode characters allowed for registration by Verisign’s software. The data in these tables come from three categories of source material.

1. Openly available language standards, published in RFC and other formats, by appropriate authorities.
2. The Unicode Standard, specifically definitions of written scripts as defined by this well-known specification.
3. ICANN’s own IDN Implementation Guidelines, which provide some special rules for domain registration, especially code points not appropriate for the DNS.

Attached IDN Tables

Per ICANN’s requirement, “IDN tables should be submitted in a machine-readable format. The model format described in Section 5 of RFC 4290 would be ideal.” Of the formats that the TAS tool accepts, there are no machine readable formats available for upload. The best format for machine readable, RFC 4290 compliant, text would be the open standard ASCII text format of .txt. Upon inquiring with ICANN applicants were told to submit the IDN tables in an .xls or .pdf format. All of the IDN tables attached to this application are available in the machine readable open standard ASCII text format of .txt. In order to meet the 5 attachment per question limit and the 5MB size per file, we have divided the Language and Script files into five files that accommodate the size of the tables. As such we have attached 4 .pdf files, and one .xls file. The single Excel file contains the one script file for Han which far exceeded the 5MB limit in .pdf but is offered here in .xls format. Again, all IDN tables are available for ICANN’s review in the required RFC 4290 compliant machine readable open standard ASCII text format of .txt outlined in the application; however, due to limitations in the TAS tool accommodations have been made.
gTLDFull Legal NameE-mail suffixDetail
.大拿VeriSign Sarlverisign.comView
Verisign will leverage its mature shared registration system to provide services for the CHINESE_SIMPLIFIED_TRANSLITERATION_OF_NET gTLD. Verisign’s registration software is in compliance with all current IDN standards, including ICANN’s IDN Guidelines, as well as The Internationalized Domain Names in Applications (IDNA 2008) specification, published by the IETF as RFC 5891.

The IDN tables provided herein represent Unicode characters allowed for registration by Verisign’s software. The data in these tables come from three categories of source material.

1. Openly available language standards, published in RFC and other formats, by appropriate authorities.
2. The Unicode Standard, specifically definitions of written scripts as defined by this well-known specification.
3. ICANN’s own IDN Implementation Guidelines, which provide some special rules for domain registration, especially code points not appropriate for the DNS.

Attached IDN Tables

Per ICANN’s requirement, “IDN tables should be submitted in a machine-readable format. The model format described in Section 5 of RFC 4290 would be ideal.” Of the formats that the TAS tool accepts, there are no machine readable formats available for upload. The best format for machine readable, RFC 4290 compliant, text would be the open standard ASCII text format of .txt. Upon inquiring with ICANN applicants were told to submit the IDN tables in an .xls or .pdf format. All of the IDN tables attached to this application are available in the machine readable open standard ASCII text format of .txt. In order to meet the 5 attachment per question limit and the 5MB size per file, we have divided the Language and Script files into five files that accommodate the size of the tables. As such we have attached 4 .pdf files, and one .xls file. The single Excel file contains the one script file for Han which far exceeded the 5MB limit in .pdf but is offered here in .xls format. Again, all IDN tables are available for ICANN’s review in the required RFC 4290 compliant machine readable open standard ASCII text format of .txt outlined in the application; however, due to limitations in the TAS tool accommodations have been made.