gTLD | Full Legal Name | E-mail suffix | Detail | .cern | European Organization for Nuclear Research (ʺCERNʺ) | cern.ch | View |
To the Applicant’s knowledge, there are no operational or rendering problems concerning the applied-for gTLD string.
Based on a decade of experience launching and operating new TLDs, Afilias, the back-end provider of registry services for the applied-for TLD, is confident the launch and operation of the applied-for TLD presents no known challenges. The rationale for this opinion includes:
- The string is not complex and is represented in standard ASCII characters and follows relevant technical, operational and policy standards;
- The string length is within lengths currently supported in the root and by ubiquitous Internet programs such as web browsers and mail applications;
- There are no new standards required for the introduction of the applied-for TLD;
- No onerous requirements are being made on registrars, registrants or Internet users, and;
- The existing secure, stable and reliable Afilias SRS, DNS, WHOIS and supporting systems and staff are amply provisioned and prepared to meet the needs of the applied-for TLD.
gTLD | Full Legal Name | E-mail suffix | Detail | .online | Namecheap Inc. | semantic.net | View |
Applicant 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 Applicant will mitigate 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, Applicant IDN policies are deliberately conservative and compliant with the ICANN Guidelines for the Implementation of IDN Version 3.0. Specifically, Applicant 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 behavior.
Applicant 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.
Applicant 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, Applicant 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.
Applicant 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;