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
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
ablesgView Comments
2016-10-06
2016-10-06No
boosgView Comments
2016-10-06
2016-10-06No
bostiksgView Comments
2016-10-06
2016-10-06Yes
calsgView Comments
2016-10-06
2016-10-06No
cbssgView Comments
2016-10-06
2016-10-06Yes
channelsgView Comments
2016-10-06
2016-10-06No
chintaisgView Comments
2016-10-06
2016-10-06Yes
comcastsgView Comments
2016-10-06
2016-10-06Yes
dadsgView Comments
2016-10-06
2016-10-06No
daysgView Comments
2016-10-06
2016-10-06No
dclksgView Comments
2016-10-06
2016-10-06No
devsgView Comments
2016-10-06
2016-10-06No
dupontsgView Comments
2016-10-06
2016-10-06Yes
eatsgView Comments
2016-10-06
2016-10-06No
ecosgView Comments
2016-10-06
2016-10-06No
esqsgView Comments
2016-10-06
2016-10-06No
fidosgView Comments
2016-10-06
2016-10-06Yes
flysgView Comments
2016-10-06
2016-10-06No
gbizsgView Comments
2016-10-06
2016-10-06No
glesgView Comments
2016-10-06
2016-10-06No
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
devkaView Comments
2016-10-08
2016-10-08No
ablebnView Comments
2016-10-14
2016-10-14No
boobnView Comments
2016-10-14
2016-10-14No
bostikbnView Comments
2016-10-14
2016-10-14Yes
calbnView Comments
2016-10-14
2016-10-14No
cbsbnView Comments
2016-10-14
2016-10-14Yes
channelbnView Comments
2016-10-14
2016-10-14No
chintaibnView Comments
2016-10-14
2016-10-14Yes
comcastbnView Comments
2016-10-14
2016-10-14Yes
dadbnView Comments
2016-10-14
2016-10-14No
daybnView Comments
2016-10-14
2016-10-14No
dclkbnView Comments
2016-10-14
2016-10-14No
devbnView Comments
2016-10-14
2016-10-14No
dupontbnView Comments
2016-10-14
2016-10-14Yes
eatbnView Comments
2016-10-14
2016-10-14No
ecobnView Comments
2016-10-14
2016-10-14No
esqbnView Comments
2016-10-14
2016-10-14No
fidobnView Comments
2016-10-14
2016-10-14Yes
flybnView Comments
2016-10-14
2016-10-14No
gbizbnView Comments
2016-10-14
2016-10-14No

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”.

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).

cn Comments

By Chang Pan, Director of operations, ban ma xiu (Beijing) information technology co., LTD

We are a startup from China and we are eager to own a perfect domain name in line with our products. In the future, we will strive to promote our products and we sincerely hope that .pro can be well-received in China. To sum up, we hope that the domain name can be approved. (Thank you for your help)

bn Comments

By Haji Hairul Mohd Daud Bin Haji Abd Karim, Senior Assistant Chief Executive, Regulatory & Resource Management Group, Authority for Info-communications Technology Industry for Brunei Darussalam, Regulatory & Resource Management Group

As Brunei Darussalam GAC Representative, we hereby respectfully submit our comment with regards to the release of “bn” labels as second level domains.
Currently, we do not agree to the release of "bn" label at the second-level under New gTLDs.

We are concerned that the use of “bn” would create confusion in representing Brunei Darussalam. This applies to all Registry Operators who have requested or will be requesting for the release of “bn” labels at the second level domains.

Additionally, the use of “bn” at second level domain of any new gTLDs may inflict damaging or reputational harm to Brunei Darussalam if associated with illegal or objectionable content and the manner of its use. We wish to protect “bn” from such abuse.

To conclude, we wish to be notified of all Registry Operators request to use “bn” labels at the second level domains of all new gTLDs.

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."