| gTLD | Full Legal Name | E-mail suffix | Detail | | .点看 | VeriSign Sarl | verisign.com | View |
2 BENEFIT TO REGISTRANTS, INTERNET USERS, AND OTHERS
As of this writing, more than 800,000 internationalized second-level domain names are registered in .com,
including approximately 400,000 in Han (Simplified). The
CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM gTLD, along with the other proposed IDN
transliterations of .com, provide an immediate benefit to registrants of those names by giving them the
opportunity to register IDN second-level domain names as “IDN.IDN” domain names. That is, registrants
can use their preferred script in both the second-level domain name and the gTLD name. Doing so
improves these domain names’ functionality and accessibility to speakers of non-Latin-based languages.
We anticipate that the availability of the CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM will
greatly increase the appeal and value of internationalized addresses in Mainland China. Expanding the
accessibility and functionality of these domain names to users worldwide is the primary benefit of all
internationalized transliterations of .com.
Finally, we anticipate that CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM will increase choice
and competition in Mainland China and elsewhere by giving local users the option of registering their
domain name with an established, trusted gTLD in their own language. Potential registrants in Mainland
China currently have limited choices if they want to register an IDN.IDN domain name in a gTLD that is
recognized across Chinese-speaking regions. The
CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM gTLD creates an attractive new option for these
users.
More specifically, the CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM gTLD benefits the
following groups:
Registrants: As discussed above, current .com registrants with second-level .com IDNs in Han
(Simplified) can greatly expand the functionality and reach of their existing registered addresses by the
availability of IDN.IDN domain names entirely in Han (Simplified) script. In addition, new registrants,
whether in Mainland China or elsewhere, who seek entirely Han (Simplified) addresses, have the option
of registering their IDN.IDN domain names in a globally recognized domain.
Internet Users: The CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM gTLD significantly
increases the ubiquity and functionality of .com for users around the world, particularly those in Mainland
China. For the first time, Chinese speakers could access a transliteration of .com addresses entirely in
their native script. Verisign is committed to ensuring that the domain name experience remains consistent
to all users, in every major script, everywhere in the world. This commitment supports the vision of “One
World. One Internet.” that infuses ICANN’s global efforts.
2.1 Business Goals
Our goal is for CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM to operate as a best-in-class
IDN registry. Although the CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM gTLD is distinct
from the .com gTLD in the DNS, we plan to provide a similar high quality of service that users of .com
have come to expect.
The first step in this process is to ensure that, like .com,
CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM operates at the highest level of availability,
stability, and security. The CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM gTLD is rooted in
the same world-class infrastructure that supports .com and .net at the highest level of operational
excellence. Users and registrants have extremely high expectations of .com, and we leverage the full
capability of our infrastructure and operational expertise to ensure that
CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM meets these expectations from the moment of
its launch.
The initial target audience for CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM is the registrants
of the approximately 400,000 IDN second-level addresses in .com. These registrants will have the
opportunity to register their IDN.com addresses as IDN.
CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM addresses.
The secondary target market for CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM is the current
registrants of ASCII domain name addresses who may be doing business in Mainland China or other
regions with a high number of Chinese speakers. The
CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM gTLD provides these registrants a ready-made
solution to localize their online identity while still maintaining the continuity of their .com addresses.
Finally, we are committed to working with registrars to perform outreach in Mainland China and elsewhere
to reach potential new registrants who are interested in establishing a new
CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM domain name.
2.2. Competition, Differentiation, and Innovation Goals
Chinese speakers currently have limited options for registering IDN.IDN domain names. The
CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM gTLD introduces competition and choice for
registrants in Mainland China by providing them with an option that—while new—also carries the trust,
reliability, and accessibility of an established global brand.
What differentiates CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM from other potential market
entrants for Han (Simplified) IDN gTLDs is that it represents a localized representation of a domain that
many users already know and trust, .com. In addition,
CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM is the best available phonetic representation of
“.com” inthe Chinese that uses Han (Simplified) script. The IDN’s brand is the brand of a globally
recognized domain, operated by a globally recognized provider.
2.3 User Experience Goals
Verisign’s goal for CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM is to deliver a user
experience as similar to the current experience of .com as possible. Verisign operates the
CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM gTLD at the same high level of security,
stability, and availability as .com, allowing registrars to enjoy the same high service levels that Verisign
provides for all of the domains we operate.
We helped organize and are deeply involved in the IDN Software Developers Consortium (IDNSDC),
which is committed to improving the functionality and accessibility of IDNs to users. We continue to
engage significantly in the IDNSDC to complement the IDN initiatives being driven by ICANN and to help
drive adoption of IDN capabilities in standard client software.
2.4 Registration Policies
The registration policies for CHINESE_SIMPLIFIED_TRANSLITERATION_OF_.COM follow closely the
existing IDN registration policies for .com. The Verisign Shared Registration System (SRS) allows the
creation of IDNs that contain Unicode supported non-ASCII scripts. We have developed a policy for IDN
registrations specifying permissible and prohibited code points. The policy is implemented in the following
five rules. IDNs that adhere to these five rules are considered valid registrations.
2.4.1. Internet Engineering Task Force (IETF) Standards
The IDNA2008 specification defines rules and algorithms that permit⁄prohibit Unicode points in IDN
registrations. We comply with all of the RFC documents that comprise the IDNA2008 standard.
2.4.2. Restrictions on Specific Languages
All IDN registrations require a three-letter Language Tag. CHI, for instance, is for the Chinese language. If
the Language Tag associated with the registration is in our Language Tag Table, we have a List of
Included Characters for that language. The requested IDN must be entirely contained within this List of
Included Characters. If even one code point from the IDN is not a valid character for this language, the
registration is rejected.
2.4.3. Restriction on Commingling of Scripts
If the Language Tag specified in the IDN registration is not in the approved list of Language Tags located
on our website, and so does not have a List of Included Characters, then we apply an alternate restriction
to prevent commingling of different scripts in a single domain.
The Unicode Standard defines a set of Unicode Scripts
(http:⁄⁄www.unicode.org⁄Public⁄6.0.0⁄ucd⁄Scripts.txt) by assigning each code point exactly one Unicode
script value. As a rule, Verisign rejects the commingling of code points from different Unicode scripts.
That is, if an IDN contains code points from two or more Unicode scripts, then that IDN registration is
rejected. For example, a character from the Latin script cannot be used in the same IDN with any Cyrillic
character. All code points within an IDN must come from the same Unicode script. This is done to prevent
confusable code points from appearing in the same IDN.
Again, this rule only applies to languages for which there is not a strictly defined List of Included
Characters. For example, the FRE Language Tag, indicating the French language, does not have a strict
List of Included Characters, and so the commingling rule applies. All code points in a French domain must
come from a single script.
2.4.4. The Verisign SRS also adheres to ICANN’s Guidelines for the Implementation of Internationalized
Domain Names. Section 5 of the document outlines characters that are allowed by the IETF standard, but
should be prohibited for IDN registration.
2.4.5. Special Characters
There are two (Unicode characters whose latest definitions are not backward compatible with previous
versions of the IDNA Standard. The Latin Sharp S and Greek Final Sigma were previously mapped to
alternate characters. Clients and registries that comply with the older standard would, for instance, map a
Latin Sharp S into two lowercase Latin letter S characters. This mapping is irreversible. The latest version
of the IDNA standard does not apply this mapping. So, whereas the Latin Sharp S was previously
prohibited (mapped into other characters), the latest standard allows registries to accept this character at
their own discretion.
Because these changes are not backward compatible, Verisign has elected to continue to disallow these
two characters until a clear and fair approach to their registration has been reached and communicated.
Additional information about our registration policies and approach to rights protection is available in our
response to Question 29, Rights Protection Mechanisms.
2.5 Measures to Protect Privacy and Confidentiality
We limit information collection from registrants to ICANN mandated data points required in the registration
of a domain name, and use this data solely for the purpose of publishing to the publicly available Whois
service. Whois Terms of Use are available on our website.
2.6 Outreach and Communications
Registrar Outreach
Many of our registrars have marketed and supported IDNs at the second-level of the .com TLD for more
than ten years. Well-established registrars have provided IDN communications and customer service in
markets where IDNs provide the highest level of benefit. We have sought advice from registrars and
actively communicated the planned approach for launching IDNs at the top-level in regular meetings with
the registrar channel. We continue to work closely with registrars not only to prepare for the Sunrise,
Trademark Claims service, and general launch periods, but also to reach existing and prospective
registrants who are interested in realizing the benefits of IDNs.
Registrant and End-User Outreach
We augment our existing IDN web content with launch planning information and additional online
resources for the IDN.IDN transliterations of .com. This web content includes details on the benefits of
IDNs, and our approach to protect intellectual property and enhance end-user ubiquity. The full launch
plan addresses Sunrise and Trademark Claims services, general launch through the registrar channel,
and localized content for the initial launch markets.
The IDN Software Developerʹs Consortium (IDNSDC)
To complement the IDN initiatives being driven by ICANN, we have organized a consortium to facilitate
adoption of IDN capabilities in standard client software. The IDNSDC works with domain name industry
stakeholders and application developers to bring greater awareness to existing client-side application
challenges so that registrars in communication with their domain name registrants may fully understand
usability issues.
| gTLD | Full Legal Name | E-mail suffix | Detail | | .닷넷 | VeriSign Sarl | verisign.com | View |
2 BENEFIT TO REGISTRANTS, INTERNET USERS, AND OTHERS
As of this writing, more than 800,000 internationalized second-level domain names are registered
in .net, including approximately 23,000 in Hangul. The KOREAN_TRANSLITERATION_OF_.NET
gTLD, along with the other proposed IDN transliterations of .net, provide an immediate benefit to
registrants of those names by giving them the opportunity to register IDN second-level domain
names as “IDN.IDN” domain names. That is, registrants can use their preferred script in both the
second-level domain name and the gTLD name. Doing so improves these domain names’
functionality and accessibility to speakers of non-Latin-based languages.
We anticipate that the availability of the KOREAN_TRANSLITERATION_OF_.NET will greatly
increase the appeal and value of internationalized addresses in Korea. Expanding the
accessibility and functionality of these domain names to users worldwide is the primary benefit of
all internationalized transliterations of .net.
Finally, we anticipate that KOREAN_TRANSLITERATION_OF_.NET will increase choice and
competition in Korea and elsewhere by giving local users the option of registering their domain
name with an established, trusted gTLD in their own language. Potential registrants in Korea
currently have limited choices if they want to register an IDN.IDN domain name in a gTLD that is
recognized across Korean-speaking regions. The KOREAN_TRANSLITERATION_OF_.NET
gTLD creates an attractive new option for these users.
More specifically, the KOREAN_TRANSLITERATION_OF_.NET gTLD benefits the following
groups:
Registrants: As discussed above, current .net registrants with second-level .net IDNs in Hangul
can greatly expand the functionality and reach of their existing registered addresses by the
availability of IDN.IDN domain names entirely in Hangul script. In addition, new registrants,
whether Korea or elsewhere, who seek entirely Hangul addresses, have the option of registering
their IDN.IDN domain names in a globally recognized domain.
Internet Users: The KOREAN_TRANSLITERATION_OF_.NET gTLD significantly increases the
ubiquity and functionality of .net for users around the world, particularly those in Korea. For the
first time, Korean speakers could access a transliteration of .net addresses entirely in their native
script. Verisign is committed to ensuring that the domain name experience remains consistent to
all users, in every major script, everywhere in the world. This commitment supports the vision of
“One World. One Internet.” that infuses ICANN’s global efforts.
2.1 Business Goals
Our goal is for KOREAN_TRANSLITERATION_OF_.NET to operate as a best-in-class IDN
registry. Although the KOREAN_TRANSLITERATION_OF_.NET gTLD is distinct from the .net
gTLD in the DNS, we plan to provide a similar high quality of service that users of .net have come
to expect.
The first step in this process is to ensure that, like .net,
KOREAN_TRANSLITERATION_OF_.NET operates at the highest level of availability, stability,
and security. The KOREAN_TRANSLITERATION_OF_.NET gTLD is rooted in the same world-
class infrastructure that supports .com and .net at the highest level of operational excellence.
Users and registrants have extremely high expectations of .net, and we leverage the full
capability of our infrastructure and operational expertise to ensure that
KOREAN_TRANSLITERATION_OF_.NET meets these expectations from the moment of its
launch.
The initial target audience for KOREAN_TRANSLITERATION_OF_.NET is the registrants of the
approximately 23,000 IDN second-level addresses in .net. These registrants will have the
opportunity to register their IDN.net addresses as IDN. KOREAN_TRANSLITERATION_OF_.NET
addresses.
The secondary target market for KOREAN_TRANSLITERATION_OF_.NET is the current
registrants of ASCII domain name addresses who may be doing business in Korea or other
regions with a high number of Korean speakers. The KOREAN_TRANSLITERATION_OF_.NET
gTLD provides these registrants a ready-made solution to localize their online identity while still
maintaining the continuity of their .net addresses.
Finally, we are committed to working with registrars to perform outreach in Korea and elsewhere
to reach potential new registrants who are interested in establishing a new
KOREAN_TRANSLITERATION_OF_.NET domain name.
2.2. Competition, Differentiation, and Innovation Goals
Korean speakers currently have limited options for registering IDN.IDN domain names. The
KOREAN_TRANSLITERATION_OF_.NET gTLD introduces competition and choice for
registrants in Korea by providing them with an option that—while new—also carries the trust,
reliability, and accessibility of an established global brand.
What differentiates KOREAN_TRANSLITERATION_OF_.NET from other potential market
entrants for Hangul IDN gTLDs is that it represents a localized representation of a domain that
many users already know and trust, .net. In addition, KOREAN_TRANSLITERATION_OF_.NET
is the best available phonetic representation of “.net” in Korean. The IDN’s brand is the brand of a
globally recognized domain, operated by a globally recognized provider.
2.3 User Experience Goals
Verisign’s goal for KOREAN_TRANSLITERATION_OF_.NET is to deliver a user experience as
similar to the current experience of .net as possible. Verisign operates the
KOREAN_TRANSLITERATION_OF_.NET gTLD at the same high level of security, stability, and
availability as .net, allowing registrars to enjoy the same high service levels that Verisign provides
for all of the domains we operate.
We helped organize and are deeply involved in the IDN Software Developers Consortium
(IDNSDC), which is committed to improving the functionality and accessibility of IDNs to users.
We continue to engage significantly in the IDNSDC to complement the IDN initiatives being driven
by ICANN and to help drive adoption of IDN capabilities in standard client software.
2.4 Registration Policies
The registration policies for KOREAN_TRANSLITERATION_OF_.NET follow closely the existing
IDN registration policies for .net. The Verisign Shared Registration System (SRS) allows the
creation of IDNs that contain Unicode supported non-ASCII scripts. We have developed a policy
for IDN registrations specifying permissible and prohibited code points. The policy is implemented
in the following five rules. IDNs that adhere to these five rules are considered valid registrations.
2.4.1. Internet Engineering Task Force (IETF) Standards
The IDNA2008 specification defines rules and algorithms that permit⁄prohibit Unicode points in
IDN registrations. We comply with all of the RFC documents that comprise the IDNA2008
standard.
2.4.2. Restrictions on Specific Languages
All IDN registrations require a three-letter Language Tag. KOR, for instance, is for the Korean
language. If the Language Tag associated with the registration is in our Language Tag Table, we
have a List of Included Characters for that language. The requested IDN must be entirely
contained within this List of Included Characters. If even one code point from the IDN is not a
valid character for this language, the registration is rejected.
2.4.3. Restriction on Commingling of Scripts
If the Language Tag specified in the IDN registration is not in the approved list of Language Tags
located on our website, and so does not have a List of Included Characters, then we apply an
alternate restriction to prevent commingling of different scripts in a single domain.
The Unicode Standard defines a set of Unicode Scripts
(http:⁄⁄www.unicode.org⁄Public⁄6.0.0⁄ucd⁄Scripts.txt) by assigning each code point exactly one
Unicode script value. As a rule, Verisign rejects the commingling of code points from different
Unicode scripts. That is, if an IDN contains code points from two or more Unicode scripts, then
that IDN registration is rejected. For example, a character from the Latin script cannot be used in
the same IDN with any Cyrillic character. All code points within an IDN must come from the same
Unicode script. This is done to prevent confusable code points from appearing in the same IDN.
Again, this rule only applies to languages for which there is not a strictly defined List of Included
Characters. For example, the FRE Language Tag, indicating the French language, does not have
a strict List of Included Characters, and so the commingling rule applies. All code points in a
French domain must come from a single script.
2.4.4. The Verisign SRS also adheres to ICANN’s Guidelines for the Implementation of
Internationalized Domain Names. Section 5 of the document outlines characters that are allowed
by the IETF standard, but should be prohibited for IDN registration.
2.4.5. Special Characters
There are two (Unicode characters whose latest definitions are not backward compatible with
previous versions of the IDNA Standard. The Latin Sharp S and Greek Final Sigma were
previously mapped to alternate characters. Clients and registries that comply with the older
standard would, for instance, map a Latin Sharp S into two lowercase Latin letter S characters.
This mapping is irreversible. The latest version of the IDNA standard does not apply this
mapping. So, whereas the Latin Sharp S was previously prohibited (mapped into other
characters), the latest standard allows registries to accept this character at their own discretion.
Because these changes are not backward compatible, Verisign has elected to continue to
disallow these two characters until a clear and fair approach to their registration has been
reached and communicated.
Additional information about our registration policies and approach to rights protection is available
in our response to Question 29, Rights Protection Mechanisms.
2.5 Measures to Protect Privacy and Confidentiality
We limit information collection from registrants to ICANN mandated data points required in the
registration of a domain name, and use this data solely for the purpose of publishing to the
publicly available Whois service. Whois Terms of Use are available on our website.
2.6 Outreach and Communications
Registrar Outreach
Many of our registrars have marketed and supported IDNs at the second-level of the .net TLD for
more than ten years. Well-established registrars have provided IDN communications and
customer service in markets where IDNs provide the highest level of benefit. We have sought
advice from registrars and actively communicated the planned approach for launching IDNs at the
top-level in regular meetings with the registrar channel. We continue to work closely with
registrars not only to prepare for the Sunrise, Trademark Claims service, and general launch
periods, but also to reach existing and prospective registrants who are interested in realizing the
benefits of IDNs.
Registrant and End-User Outreach
We augment our existing IDN web content with launch planning information and additional online
resources for the IDN.IDN transliterations of .net. This web content includes details on the
benefits of IDNs, and our approach to protect intellectual property and enhance end-user ubiquity.
The full launch plan addresses Sunrise and Trademark Claims services, general launch through
the registrar channel, and localized content for the initial launch markets.
The IDN Software Developerʹs Consortium (IDNSDC)
To complement the IDN initiatives being driven by ICANN, we have organized a consortium to
facilitate adoption of IDN capabilities in standard client software. The IDNSDC works with domain
name industry stakeholders and application developers to bring greater awareness to existing
client-side application challenges so that registrars in communication with their domain name
registrants may fully understand usability issues.