16 Describe the applicant's efforts to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string

Prototypical answer:

Amazon EU S.à r.l. (AEU) foresees no known rendering issues in connection with the .書籍 TLD. This is based upon consultation with AEU’s backend provider, Neustar, which has successfully launched a number of new gTLDs over the last decade. In reaching this determination, the following data points were analyzed:
• ICANN’s Security Stability Advisory Committee DSV009, Alternative TLD Name Systems and Roots: Conflict, Control & Consequences
• IAB - RFC3696 Application Techniques for Checking & Transformation of Names
• Known software issues which Neustar has encountered from launching new gTLDs
• Character type and length
• ICANN supplemental notes to Q16
• ICANN presentation during its Costa Rica regional meeting on TLD Universal Acceptance;

The following sections discuss the potential operational or rendering problems that can arise, and how mitigated.

Compliance & Interoperability
The applied-for string conforms to all relevant RFCs, as well as the string requirements set forth in s2.2.1.3.2 Applicant Guidebook.

Mixing Scripts
A domain name label with characters from different scripts has a higher likelihood of encountering rendering issues. If the mixing of scripts occurs within the top-level label, any rendering issue would affect all domain names registered under it. If occurring within second level labels, its ill-effects are confined to the domain names with such labels.
All characters in the applied-for gTLD string are taken from a single script. The IDN policies are conservative and compliant with ICANN Guidelines for the Implementation of IDN V3.0. Specifically, mixed-script labels may not be registered at the 2nd level, except for languages with established orthographies and conventions that require the commingled use of multiple scripts, e.g. Japanese.

Interaction between Labels
Even with the above issue appropriately restricted, it is possible that a domain name composed of labels with different properties such as script and directionality may introduce unintended rendering behavior.
Only scripts and characters that would not pose a risk when combined with the top level label will be offered.

Immature Scripts
Scripts or characters added in Unicode versions newer than 3.2 (on which IDNA2003 was based) may encounter interoperability issues due to the lack of software support.
We have no current plans to offer registration of labels containing such scripts or characters.

Other Issues
We are not offering the registration of domains that includes combining characters or characters that require IDNA contextual rules handling.
The following may be construed as operational or rendering issues, but consider them out of the scope of this question. Nevertheless, we will take reasonable steps to protect registrants and Internet users by working with vendors and relevant language communities to mitigate such issues.
• missing fonts causing string to fail to render correctly
• universal acceptance of the TLD

Similar gTLD applications: (310)