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
.工行Industrial and Commercial Bank of China Limitedhichina.comView
Afilias has reviewed and tested the TLD in the ICANN IDN wiki and determined that no additional operational, rendering or other general usability issues exist. Also, as no additional issues were found as it relates to IDN Tables, variant management, and string confusability against existing TLD⁄ISO3166⁄IDN-ccTLDs, we have established that this TLD will be a trusted and secure extension for Internet addresses.
Yet, given the method used in developing and implementing IDNs, some known operational, usability and rendering problems are to be expected. The three issues include:
1. Application-level implementation: End-users expect to see the U-label version of the IDN; however this is not always the case. Due to security problems discovered in early IDN implementations, applications insert protection mechanisms for users typing or clicking on IDN links. As such, sometimes the A-label is displayed in the browser address-bars and some online forms will not accept U-label strings.
From an operational perspective, the IDN will resolve and e.g. the webpage for the domain will be displayed for the user, making the IDNs functional as web-addresses.
It is generally agreed that display of the U-label is the best possible result. To reach that result, Afilias will expand on existing relationships with application developers to ensure least possible impact for the TLD launch. Afilias will continue working with all major browser developers to streamline and assist in user-friendly IDN implementation and support ICANN’s work on Universal TLD Acceptance.
2. Email usage issue: Afilias has been a pioneer in implementing support for IDN TLDs in email software. Afilias staff is chair of the Email Address Internationalization (EAI) working group and has been leading standardization efforts since 2006. The protocol for internationalized email is in its last stages of development; recently, core components have been standardized such as RFCs 6530, 6531, 6532, and 6533. As a result, not all email software providers have implemented support for IDN TLDs at this stage. Afilias will continue to conduct registrar training programs and supply information to facilitate in their outreach, marketing, and informational material to registrants.
3. Jumping the digit issue: A known rendering issue with IDN TLDs is referred to as the jumping digit. This is a problem that occurs in certain situations where right-to-left directional scripts are used in conjunction with a digit placed in a string before the separator (dot) will at resolution “jump” to the other side of the separator. As a result, the resolving domain name is a completely different domain name than originally intended.
No such issue will take place with domains under this TLD as no right-to-left scripts are supported.
gTLDFull Legal NameE-mail suffixDetail
.通用电气公司GE GTLD Holdings LLCreedsmith.comView
Applicant and Afilias has reviewed the TLD and tested it in the ICANN IDN wiki and determined that no additional operational, rendering or other general usability issues exist. Also, as no additional issues were found as it relates to IDN Tables, variant management, and string confusability against existing TLD⁄IO3166⁄IDN-ccTLDs, we have established that this TLD will be a trusted and secure extension for Internet addresses.
Yet, given the method used in developing and implementing IDNs, some known operational, usability and rendering problems are to be expected. The three issues include:
1. Application-level implementation: End-users expect to see the U-label version of the IDN; however this is not always the case. Due to security problems discovered in early IDN implementations, applications insert protection mechanisms for users typing or clicking on IDN links. As such, sometimes the A-label is displayed in the browser address-bars and some online forms will not accept U-label strings.
From an operational perspective, the IDN will resolve and e.g. the webpage for the domain will be displayed for the user, making the IDNs functional as web-addresses.
It is generally agreed that display of the U-label is the best possible result. To reach that result, Afilias will expand on existing relationships with application developers to ensure least possible impact for the TLD launch. Afilias will continue working with all major browser developers to streamline and assist in user-friendly IDN implementation and support ICANN’s work on Universal TLD Acceptance.
2. Email usage issue: Afilias has been a pioneer in implementing support for IDN TLDs in email software. Afilias staff is chair of the Email Address Internationalization (EAI) working group and has been leading standardization efforts since 2006. The protocol for internationalized email is in its last stages of development; recently, core components have been standardized such as RFCs 6530, 6531, 6532, and 6533. As a result, not all email software providers have implemented support for IDN TLDs at this stage. Afilias will continue to conduct registrar training programs and supply information to facilitate in their outreach, marketing, and informational material to registrants.
3. Jumping the digit issue: A known rendering issue with IDN TLDs is referred to as the jumping digit. This is a problem that occurs in certain situations where right-to-left directional scripts are used in conjunction with a digit placed in a string before the separator (dot) will at resolution “jump” to the other side of the separator. As a result, the resolving domain name is a completely different domain name than originally intended. No such issue will take place with domains under this TLD as no right-to-left scripts are supported.