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
.streamdot Stream Limitedfamousfourmedia.comView
Q16
The Applicant has taken steps to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string (the “String”). The following has been undertaken:

a)The TLD label is valid as specified in relevant technical standards, including: Domain Names: Implementation and Specification (RFC 1035), and Clarifications to the DNS Specification (RFC 2181) and any updates thereto;

b)The TLD label, which is 6 characters long, is well short of the 63 character maximum length;

c) The TLD label is a valid host name, as specified IN: DOD Internet Host Table Specification (RFC 952), Requirements for Internet Hosts — Application and Support (RFC1123), and Application Techniques for Checking and Transformation of Names (RFC 3696), Internationalized Domain Names in Applications (IDNA)(RFCs 5890-5894), and any updates thereto;

d)The TLD label consists entirely of letters (a-z)

The Applicant has evaluated the risks of the TLD experiencing TLD Acceptance issues similar to problems reported in the “Evaluation of the New gTLDs: Policy and Legal Issues” (31⁄08⁄2004) which discussed acceptance issues associated with the year 2000 round of new gTLDs with more than three characters (i.e.,.aero,.coop,.info, .museum, .name). At that time, only one gTLD, .arpa, which is not widely used outside of limited circles – had four letters. As a result, the new gTLDs had compatibility problems with the software used by Internet infrastructure operators and application providers. Some users have recently been reporting issues with the use of .xxx names in applications such as Twitter and Skype where domain names entered from that TLD are not instantly recognized with a hyperlink as more established gTLDs are.

The Applicant’s registry backend services provider, Neustar Inc tested the String for potential rendering or operational problems; none were found.

As the String is not an IDN it does not contain characters that require mixed right-to-left or left-to-right functions. The applicant has familiarized itself with the requirements and components of the IDNA protocol by reviewing the RFCs and background information found on the ICANN IDN Wiki.

The Applicant tested the String using the ICANN SWORD String Similarity Assessment Tool algorithm. The result of this test is 53. The Applicant considers this to be below the level where issues might occur. Should Registrants experience any acceptance issues the Applicant will have a dedicated Operational and Rendering Team (“ORT”) on an on-going basis to assist with operational, rendering issues or any other problems that might arise. The ORT will be in place to assist Registrants with any additional problems that may arise out of new TLD that other applicants may be awarded during this process which could lead to unforeseen string confusion now and in the future.
-end-
gTLDFull Legal NameE-mail suffixDetail
.rundot Run Limitedfamousfourmedia.comView
Q16
The Applicant has taken steps to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string (the “String”). The following has been undertaken:

a)The TLD label is valid as specified in relevant technical standards, including: Domain Names: Implementation and Specification (RFC 1035), and Clarifications to the DNS Specification (RFC 2181) and any updates thereto;

b)The TLD label, which is 3 characters long, is well short of the 63 character maximum length;

c) The TLD label is a valid host name, as specified IN: DOD Internet Host Table Specification (RFC 952), Requirements for Internet Hosts — Application and Support (RFC1123), and Application Techniques for Checking and Transformation of Names (RFC 3696), Internationalized Domain Names in Applications (IDNA)(RFCs 5890-5894), and any updates thereto;

d)The TLD label consists entirely of letters (a-z)

The Applicant has evaluated the risks of the TLD experiencing TLD Acceptance issues similar to problems reported in the “Evaluation of the New gTLDs: Policy and Legal Issues” (31⁄08⁄2004) which discussed acceptance issues associated with the year 2000 round of new gTLDs with more than three characters (i.e.,.aero,.coop,.info, .museum, .name). At that time, only one gTLD, .arpa, which is not widely used outside of limited circles – had four letters. As a result, the new gTLDs had compatibility problems with the software used by Internet infrastructure operators and application providers. Some users have recently been reporting issues with the use of .xxx names in applications such as Twitter and Skype where domain names entered from that TLD are not instantly recognized with a hyperlink as more established gTLDs are.

The String has fewer characters than the current longest TLD which is (.museum).

The Applicant’s registry backend services provider, Neustar Inc tested the String for potential rendering or operational problems; none were found.

As the String is not an IDN it does not contain characters that require mixed right-to-left or left-to-right functions. The applicant has familiarized itself with the requirements and components of the IDNA protocol by reviewing the RFCs and background information found on the ICANN IDN Wiki.

The Applicant tested the String using the ICANN SWORD String Similarity Assessment Tool algorithm. The result of this test is 64. The Applicant considers this to be below the level where issues might occur. Should Registrants experience any acceptance issues the Applicant will have a dedicated Operational and Rendering Team (“ORT”) on an on-going basis to assist with operational, rendering issues or any other problems that might arise. The ORT will be in place to assist Registrants with any additional problems that may arise out of new TLD that other applicants may be awarded during this process which could lead to unforeseen string confusion now and in the future.
-end-