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

Prototypical answer:

15.b.1 Introduction and Available IDNs

One of Google’s core goals in creating the registry is to allow for the creation and deployment of localized content to better serve the global Internet community.

Based on our research, we chose to use IDN tables only for written languages that are in current use by the native population of this TLD.

In keeping with this policy, we plan to support the following character sets:

- Japanese
- Latin

The IDN Tables covering these languages are in Q15a_IDNTables in a concatenated file. To create these tables, we reviewed the “Repository of IDN Practices - Procedures” section of the IANA web site [1] focusing on table requirements as well as the existing IDN tables for format. We chose to follow the IANA guidelines given that it is well known as the industry standard. In addition, we consulted a member of the Board of Directors at the Unicode Consortium.

We may implement a different language set in the future if language usage changes or in response to business and technical requirements.

15.b.2 Second Level Domain IDNs

Given that the IDN TLD is in a non-Latin language, we believe that there is no use case to support second level domains (SLD) in other languages other than the languages referenced in section 15.b.1

In conjunction with our goals mentioned in section 15.b.1, we believe this will minimize confusion and maximize safety for this TLD. We may implement a different language set for SLDs in the future if language usage changes or in response to business and technical requirements.

15.b.3 Footnotes

[1] IANA “Repository of IDN Practices - Procedures” web site http:⁄⁄www.iana.org⁄procedures⁄idn-repository.html

Similar gTLD applications: (2)