Back

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

gTLDFull Legal NameE-mail suffixDetail
.珠宝Richemont DNS Inc.valideus.comView
Richemont DNS foresees no known rendering issues with .珠宝.This answer is based upon consultation with Richemont DNS’s backend provider, Neustar, which has successfully launched a number of new gTLDs. Richemont DNS has analyzed: ICANN’s Security Stability Advisory Committee (SSAC) entitled Alternative TLD Name Systems and Roots: Conflict, Control and Consequences(SAC009); IAB - RFC3696 “Application Techniques for Checking and Transformation of Names”; Known software issues which Neustar has encountered when launching new gTLDs; Character type and length; ICANN supplemental notes to Question 16; and ICANN’s presentation on TLD Universal Acceptance (Costa Rica regional meeting).
Compliance and Interoperability-The applied-for string conforms to all relevant RFCs, as well as the string requirements set forth in Section 2.2.1.3.2 of the Applicant Guidebook.
Mixing Scripts-If a domain name label contains characters from different scripts, it 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. In addition, the IDN policies are deliberately conservative and compliant with the ICANN Guidelines for the Implementation of IDN Version 3.0. Specifically,mixed-script labels are not permitted to be registered at the second-level, except for languages with established orthographies and conventions that require the commingled use of multiple scripts, e.g. Japanese.
Interaction between Labels-It is possible that a domain name composed of labels with different properties such as script and directionality may introduce unintended rendering behaviour. A conservative strategy is adopted when offering IDN registrations. In particular, it ensures that any IDN language tables used for offering IDN second level registrations involve only scripts and characters that would not pose a risk when combined with the top-level label.
Immature Scripts-Scripts or characters added in Unicode versions newer than 3.2 (on which IDNA2003 was based) may encounter interoperability issues due to a lack of software support. We have no current plans to offer registration of labels containing such scripts⁄characters.
Other Issues-To further contain the risks of operation or rendering problems, we are not offering the registration of domains that includes combining characters or characters that require IDNA contextual rules handling.These are considered as 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 issues such as missing fonts causing string to fail to render correctly; and enabling universal acceptance of the TLD.
gTLDFull Legal NameE-mail suffixDetail
.phoneWild Frostbite, LLCdonuts.coView
Donuts has conducted technical analysis on the applied-for string, and concluded that there are no known potential operational or rendering issues associated with the string.

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

## Compliance and Interoperability

The applied-for string conforms to all relevant RFCs, as well as the string requirements set forth in Section 2.2.1.3.2 of the Applicant Guidebook.


## Mixing Scripts

If a domain name label contains characters from different scripts, it 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. In addition, Donutsʹs IDN policies are deliberately conservative and compliant with the ICANN Guidelines for the Implementation of IDN Version 3.0. Specifically, Donuts does not allow mixed-script labels to be registered at the second 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 behaviour.

Donuts adopts a conservative strategy when offering IDN registrations. In particular, it ensures that any IDN language tables used for offering IDN second level registrations involve only scripts and characters that would not pose a risk when combined with the top level label.


## 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.

Donuts does not currently plan to offer registration of labels containing such scripts or characters.


## Other Issues

To further contain the risks of operation or rendering problems, Donuts currently does not offer registration of labels containing combining characters or characters that require IDNA contextual rules handling. It may reconsider this decision in cases where a language has a clear need for such characters.

Donuts understands that the following may be construed as operational or rendering issues, but considers them out of the scope of this question. Nevertheless, it 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; and
- universal acceptance of the TLD;