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
.欧莱雅LʹOréalloreal.comView
L’Oréal has consulted various experts in the field of domain names, including its selected back-end registry operator, VeriSign, Inc. which has successfully launched a number of new gTLDs over the last decade and is currently managing various TLDs, including .COM. Furthermore, the applied-for .欧莱雅 string is a string that entirely consists of standard US ASCII characters, as is the case with most extensions currently available in the DNS. Therefore, to L’Oréal’s best knowledge and belief, no specific issues are to be expected as regards the operation and rendering of the .欧莱雅 gTLD. 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 Verisign 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
.KERASTASELʹOréalloreal.comView
L’Oréal has consulted various experts in the field of domain names, including its selected back-end registry operator, VeriSign, Inc. which has successfully launched a number of new gTLDs over the last decade and is currently managing various TLDs, including .COM. Furthermore, the applied-for .KERASTASE string is a string that entirely consists of standard US ASCII characters, as is the case with most extensions currently available in the DNS. Therefore, to L’Oréal’s best knowledge and belief, no specific issues are to be expected as regards the operation and rendering of the .KERASTASE gTLD. 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 Verisign 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.