Skip to main content
Resources

Two-Character Letter/Letter Label Comments and Mitigation Measures

As of 13 December 2016, this page is no longer active. Please visit here for more information.

For comments submitted before 6 October 2015, view the archive of comments received.

Download Excel
TLD  Two
Characters  		Comments from GovernmentLast
updated  		RO Mitigation PlanRO NameBRAND TLD
gugesgView Comments
2016-10-06
2016-10-06No
hangoutsgView Comments
2016-10-06
2016-10-06No
mapsgView Comments
2016-10-06
2016-10-06No
memesgView Comments
2016-10-06
2016-10-06No
movsgView Comments
2016-10-06
2016-10-06No
naturasgView Comments
2016-10-06
2016-10-06Yes
nbasgView Comments
2016-10-06
2016-10-06Yes
newsgView Comments
2016-10-06
2016-10-06No
pfizersgView Comments
2016-10-06
2016-10-06Yes
phdsgView Comments
2016-10-06
2016-10-06No
prodsgView Comments
2016-10-06
2016-10-06No
profsgView Comments
2016-10-06
2016-10-06No
pwcsgView Comments
2016-10-06
2016-10-06Yes
rogerssgView Comments
2016-10-06
2016-10-06Yes
rsvpsgView Comments
2016-10-06
2016-10-06No
searchsgView Comments
2016-10-06
2016-10-06No
sfrsgView Comments
2016-10-06
2016-10-06Yes
showtimesgView Comments
2016-10-06
2016-10-06Yes
watchessgView Comments
2016-10-06
2016-10-06No
xfinitysgView Comments
2016-10-06
2016-10-06Yes
xn--flw351esgView Comments
2016-10-06
2016-10-06Yes
xn--kpu716fsgView Comments
2016-10-06
2016-10-06No
xn--pbt977csgView Comments
2016-10-06
2016-10-06No
xn--qcka1pmcsgView Comments
2016-10-06
2016-10-06Yes
zipsgView Comments
2016-10-06
2016-10-06No
abletwView Comments
2016-09-22
2016-09-22No
bootwView Comments
2016-09-22
2016-09-22No
bostiktwView Comments
2016-09-22
2016-09-22Yes
caltwView Comments
2016-09-22
2016-09-22No
cbstwView Comments
2016-09-22
2016-09-22Yes
channeltwView Comments
2016-09-22
2016-09-22No
chintaitwView Comments
2016-09-22
2016-09-22Yes
dadtwView Comments
2016-09-22
2016-09-22No
daytwView Comments
2016-09-22
2016-09-22No
dclktwView Comments
2016-09-22
2016-09-22No
devtwView Comments
2016-09-22
2016-09-22No
duponttwView Comments
2016-09-22
2016-09-22Yes
eattwView Comments
2016-09-22
2016-09-22No
ecotwView Comments
2016-09-22
2016-09-22No
esqtwView Comments
2016-09-22
2016-09-22No
flytwView Comments
2016-09-22
2016-09-22No
gbiztwView Comments
2016-09-22
2016-09-22No
gdntwView Comments
2016-09-22
2016-09-22No
gletwView Comments
2016-09-22
2016-09-22No
gugetwView Comments
2016-09-22
2016-09-22No
hangouttwView Comments
2016-09-22
2016-09-22No
ikanotwView Comments
2016-09-22
2016-09-22Yes
jcptwView Comments
2016-09-22
2016-09-22Yes
maptwView Comments
2016-09-22
2016-09-22No
memetwView Comments
2016-09-22
2016-09-22No
movtwView Comments
2016-09-22
2016-09-22No
newtwView Comments
2016-09-22
2016-09-22No
pfizertwView Comments
2016-09-22
2016-09-22Yes
phdtwView Comments
2016-09-22
2016-09-22No
prodtwView Comments
2016-09-22
2016-09-22No
proftwView Comments
2016-09-22
2016-09-22No
rsvptwView Comments
2016-09-22
2016-09-22No
searchtwView Comments
2016-09-22
2016-09-22No
sfrtwView Comments
2016-09-22
2016-09-22Yes
showtimetwView Comments
2016-09-22
2016-09-22Yes
watchestwView Comments
2016-09-22
2016-09-22No
wtctwView Comments
2016-09-22
2016-09-22Yes
xn--flw351etwView Comments
2016-09-22
2016-09-22Yes
xn--kpu716ftwView Comments
2016-09-22
2016-09-22No
xn--pbt977ctwView Comments
2016-09-22
2016-09-22No
xn--qcka1pmctwView Comments
2016-09-22
2016-09-22Yes
ziptwView Comments
2016-09-22
2016-09-22No
zipreView Comments
2016-09-12
2016-09-12No
ableitView Comments
2016-09-06
2016-09-06No
booitView Comments
2016-09-06
2016-09-06No
bostikitView Comments
2016-09-06
2016-09-06Yes
calitView Comments
2016-09-06
2016-09-06No
camitView Comments
2016-09-06
2016-09-06No
cbsitView Comments
2016-09-06
2016-09-06Yes
channelitView Comments
2016-09-06
2016-09-06No
chintaiitView Comments
2016-09-06
2016-09-06Yes
daditView Comments
2016-09-06
2016-09-06No
dayitView Comments
2016-09-06
2016-09-06No
dclkitView Comments
2016-09-06
2016-09-06No
devitView Comments
2016-09-06
2016-09-06No
dupontitView Comments
2016-09-06
2016-09-06Yes
eatitView Comments
2016-09-06
2016-09-06No
ecoitView Comments
2016-09-06
2016-09-06No
esqitView Comments
2016-09-06
2016-09-06No
flyitView Comments
2016-09-06
2016-09-06No
fujixeroxitView Comments
2016-09-06
2016-09-06Yes
gbizitView Comments
2016-09-06
2016-09-06No
gdnitView Comments
2016-09-06
2016-09-06No
gleitView Comments
2016-09-06
2016-09-06No
gugeitView Comments
2016-09-06
2016-09-06No
hangoutitView Comments
2016-09-06
2016-09-06No
ikanoitView Comments
2016-09-06
2016-09-06Yes
jcpitView Comments
2016-09-06
2016-09-06Yes
mapitView Comments
2016-09-06
2016-09-06No
memeitView Comments
2016-09-06
2016-09-06No
movitView Comments
2016-09-06
2016-09-06No
newitView Comments
2016-09-06
2016-09-06No
pfizeritView Comments
2016-09-06
2016-09-06Yes
phditView Comments
2016-09-06
2016-09-06No
proditView Comments
2016-09-06
2016-09-06No

sg Comments

By Queh Ser Pheng, Deputy Director, Internet Resource Management, Policy & Competition Development Group, Infocomm Development Autority of Singapore

We hereby respectfully submit our comment regarding the release of letter/letter two-character labels as second level domains.

At this stage, we are unable to agree to the release of the two-character "sg" label at the second-level under gTLDs because of the concern that such use would create confusion with the ccTLD "sg" representing Singapore. Until further notice, this policy is to be applied to all gTLDs who have requested or will be requesting for the release of letter-letter two-character labels at the second level.

To elaborate further, we are open to considering the release of "sg" to registry operators who have robust framework in place to address concerns of government. We recognise there are legitimate and valid reasons for such use. However, we are of the view that it is prudent for ICANN to first put in place a holistic and robust framework before approvals can be given. More thoughts need to be given to the evaluation process and in particular the remedies available should a registry operator use the approved names in an undesirable manner. Besides possible confusion with the corresponding country code and/or country/territory name, we are also concerned with:

(a) The possible reputational harm if ".sg." is associated with illegal or objectionable content and/or manner-of-use; and

(b) The direct harm if ".sg." content or manner-of-use targets Singapore as a nation or Singapore entities (e.g., websites could masquerade as Singapore Government agencies).

ICANN's current policy focuses only on the "initial release" process. There needs to be considerations given to "post-release" issues. As such, the ICANN framework should include:

(a) A recourse for the government/country code manager to issue a notice to object to the content and/or manner-of-use that is misleading, questionable, objectionable or contrary to the country’s reputation and laws. There should be an effective and robust process acceptable by the government/country code manager for the registry operator to address the concern; and

(b) Provisions to require the registry operator to re-seek approval from government/country code manager should there be material changes in ownership or organisational control (for example merger with or acquisitions by another entity).

In addition, ICANN must be committed to take actions against the registry operator should they fail to comply with the framework (e.g. implement a process for country/territory to raise objections to ICANN and for ICANN to take appropriate remedial actions such as remove/delete/revoke affected names).

tw Comments

By Lin, Mao-Shong, Deputy Director, Ministry of Transportation and Communications

I’m writing hereby to submit Taiwan government’s comments on the release of the “tw” label under the New gTLDs.

We object to the release of “tw” as SLD under all the above-mentioned New gTLDs for their registration by the corresponding Registry operators. We reserve the right to change position in this regard in the future.

The rationale of our objections are below:
Since “tw” label is the country code for Taiwan, the use of “tw” as SLD under these diverse New gTLDs would create confusion or concerns at multiple levels on our part, which include, but not limited to, ”dwarfing national dignity”, “violation of public order or good social custom”, “affecting the rights of domestic enterprises”, and “being prone to produce perplexity to our disadvantage”.

re Comments

By Ross Dale, Senior Designer, Afnic

There should be no conflict with the use of .re, specifically the domain requested as mo.re, or any other two character domain in the reunion islands. With only a small population there should be minimum conflict whilst maximising profit opportunity.

lt Comments

By Rita Forsi, Italian GAC Representative, Ministry of Economic Development

By Rita Forsi, Italia GAC Representative, Ministry of Economic Development

With reference to the process for Considering Comments for Two-Character Letter/Letter Labels launched by ICANN on October 6, 2015, Italy restates its position expressed on March 25, 2015 (http://mm.icann.org/pipermail/twochar_comments/2015/000063.html) and on May 14, 2015 (email attached).

Italy does not object tout-court to the delegation of our ccSLD, but wants to exercise the right to evaluate the delegation of “it” as a SLD on a case-by-case basis.

The evaluation process takes into account not only the confusion risks, but also the national and international legal framework (e.g. IPR) and opportunity considerations (e.g. it.sucks).

We would like to recall that both the Singapore and Dublin GAC Communiqué advise the Board that comments submitted by the relevant Governments be fully considered regardless of the grounds for objection.

For the abovementioned reasons, we reiterate our position expressed in March 25 2015 for the release of the two‐character “it” label at the second level under new gTLDs.
In general, “it” label string may be released to the extent that the registry operator reaches a formal agreement with the Italian government (included our ccTLD registry “.it”) as per Specification 5 of the Registry Agreement.
This policy is to be applied to all new gTLDs, including, but not limited to, those falling within Category 1 and Category 2 of the Beijing Communiquè. who have requested for the release of “it” labels at the second level.
The authorization requests should be sent to the Italian GAC representatives.

Furthermore, we would like to underline that these “lines-to-take” are agreed with the “.it” Registry.

Rita Forsi

A note about our terms of service:

We have updated our electronic terms of service to provide greater transparency and align with laws applicable to us. Learn more.

This site uses cookies to deliver an efficient user experience and to help us see how the site is used. Learn more.OK

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."