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

Prototypical answer:

gTLDFull Legal NameE-mail suffixDetail
.谷歌Charleston Road Registry Inc.google.comView

Charleston Road Registry (a wholly-owned subsidiary of Google Inc.) will use technology outsourced to Google to provide this registry solution. Details of Google’s implementation are discussed below.

Google limited its rendering⁄operational testing to the scope of domain names. That is, Google assumes the label is read left-to-right (LTR) and is used in conjunction with other LTR-read labels. As such, Google made no attempt to identify potential bidirectional (BIDI) or right-to-left (RTL) issues. With that said, Google did verify the string by:
1. Comparing the characters to the Unicode list of confusables [1] and RFC 5892 [2] and found no issues as RFC 5892 disallows the visible confusion identified by the confusable mapping.
2. Validating that the string has meaning only in Chinese and found that it means ʺvalley songʺ in Japanese and no Simplified Chinese version. Google finds the risk of confusion low as it plans on running a closed registry to promote the Google brand.

[1]. The Unicode Consortium, ʺRecommended confusable mapping for IDN, Version 2.1ʺ, April 2010, 〈http:⁄⁄www.unicode.org⁄Public⁄security⁄revision-04⁄confusables.txt〉.

[2]. P. Faltstrom, Ed. ʺThe Unicode Code Points and Internationalized Domain Names for Applications (IDNA)ʺ.RFC 5892. August 2010, http:⁄⁄tools.ietf.org⁄html⁄rfc5892

Similar gTLD applications: (0)

gTLDFull Legal NameE-mail suffixzDetail