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
.nycThe City of New York by and through the New York City Department of Information Technology & Telecommunicationsneustar.bizView
The City of New York (”the City”) foresees no know rendering issues in connection with the proposed  .NYC string which it is seeking to apply for as a gTLD. To date, ASCII TLD strings that are three characters long, like “.nyc”, have not encountered the types of issues that some of the other longer ASCII TLD strings have historically had. Unfortunately, as the City is aware, there are still certain Internet and software applications that “hard code” TLD lists rather than referring to the IANA list of TLDs. To the extent that the City becomes aware of applications that do in fact hard code, it is committed to working with the application developers to rectifying such issues and with the ICANN community’s outreach effort to address the Universal Acceptance of TLDs. This answer is based upon consultation with NYC’s preferred backend provider, Neustar, which has successful 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
.neustarNeuStar, Inc.neustar.bizView
Neustar foresees no known rendering issues in connection with the proposed .neustar string which it is seeking to apply for as a gTLD. Unfortunately, as Neustar is aware, there are still certain Internet and software applications that “hard code” TLD lists rather than referring to the IANA list of TLDs. To the extent that Neustar becomes aware of applications that do in fact hard code, it is committed to working with the application developers to rectifying such issues and with the ICANN community’s outreach effort to address the Universal Acceptance of TLDs. This answer is based upon consultation with our history in successfully launching 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.