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
.amicaAmica Mutual Insurance Companyamica.comView
Amica foresees no known rendering issues in connection with the proposed .amica string which it is seeking to apply for as a gTLD. This answer is based upon consultation with Amicaʹs preferred 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 (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 during the last decade launching new gTLDs;
- Character type and length;
- ICANN supplemental notes to Question 16; and
- ICANN’s presentation during its Costa Rica regional meeting on TLD Universal Acceptance.
gTLDFull Legal NameE-mail suffixDetail
.FTRFrontier Communications Corporationftr.comView
Frontier Communications Corporation (“Frontier”) foresees no known rendering issues in connection with the proposed .FTR gTLD. This answer is based on Frontier’s research and consultation with Frontier’s selected back-end technical services provider, Neustar, Inc., which has successfully launched a number of new gTLDs over the last decade. In reaching this determination, a number of resources were consulted including the following:

1. ICANN’s Security Stability Advisory Committee (SSAC) entitled Alternative TLD Name Systems and Roots: Conflict, Control and Consequences (SAC009);
2. IAB - RFC3696 “Application Techniques for Checking and Transformation of Names”;
3. Known software issues that Neustar has encountered when launching new gTLDs;
Character type and length;
4. ICANN supplemental notes to Question 16 and materials linked from the supplemental notes; and
5. ICANN’s presentation during its Costa Rica regional meeting on TLD Universal Acceptance.