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.

TLD  Two
Characters
 
Comments from GovernmentLast
updated
 
RO Mitigation PlanRO NameBRAND TLD
profitView Comments
2016-09-06
2016-09-06No
rsvpitView Comments
2016-09-06
2016-09-06No
searchitView Comments
2016-09-06
2016-09-06No
sfritView Comments
2016-09-06
2016-09-06Yes
showtimeitView Comments
2016-09-06
2016-09-06Yes
totalitView Comments
2016-09-06
2016-09-06Yes
watchesitView Comments
2016-09-06
2016-09-06No
wtcitView Comments
2016-09-06
2016-09-06Yes
xn--flw351eitView Comments
2016-09-06
2016-09-06Yes
xn--kpu716fitView Comments
2016-09-06
2016-09-06No
xn--pbt977citView Comments
2016-09-06
2016-09-06No
xn--qcka1pmcitView Comments
2016-09-06
2016-09-06Yes
zipitView Comments
2016-09-06
2016-09-06No
ablepkView Comments
2016-08-23
2016-08-23No
boopkView Comments
2016-08-23
2016-08-23No
bostikpkView Comments
2016-08-23
2016-08-23Yes
calpkView Comments
2016-08-23
2016-08-23No
campkView Comments
2016-08-23
2016-08-23No
cbspkView Comments
2016-08-23
2016-08-23Yes
channelpkView Comments
2016-08-23
2016-08-23No
chintaipkView Comments
2016-08-23
2016-08-23Yes
dadpkView Comments
2016-08-23
2016-08-23No
daypkView Comments
2016-08-23
2016-08-23No
dclkpkView Comments
2016-08-23
2016-08-23No
devpkView Comments
2016-08-23
2016-08-23No
doctorpkView Comments
2016-08-23
2016-08-23No
eatpkView Comments
2016-08-23
2016-08-23No
ecopkView Comments
2016-08-23
2016-08-23No
esqpkView Comments
2016-08-23
2016-08-23No
flypkView Comments
2016-08-23
2016-08-23No
fujixeroxpkView Comments
2016-08-23
2016-08-23Yes
gamespkView Comments
2016-08-23
2016-08-23No
gbizpkView Comments
2016-08-23
2016-08-23No
gdnpkView Comments
2016-08-23
2016-08-23No
glepkView Comments
2016-08-23
2016-08-23No
gugepkView Comments
2016-08-23
2016-08-23No
hangoutpkView Comments
2016-08-23
2016-08-23No
ikanopkView Comments
2016-08-23
2016-08-23Yes
jcppkView Comments
2016-08-23
2016-08-23Yes
mappkView Comments
2016-08-23
2016-08-23No
memepkView Comments
2016-08-23
2016-08-23No
movpkView Comments
2016-08-23
2016-08-23No
newpkView Comments
2016-08-23
2016-08-23No
phdpkView Comments
2016-08-23
2016-08-23No
prodpkView Comments
2016-08-23
2016-08-23No
profpkView Comments
2016-08-23
2016-08-23No
quebecpkView Comments
2016-08-23
2016-08-23No
rsvppkView Comments
2016-08-23
2016-08-23No
searchpkView Comments
2016-08-23
2016-08-23No
sfrpkView Comments
2016-08-23
2016-08-23Yes
showtimepkView Comments
2016-08-23
2016-08-23Yes
totalpkView Comments
2016-08-23
2016-08-23Yes
watchespkView Comments
2016-08-23
2016-08-23No
wtcpkView Comments
2016-08-23
2016-08-23Yes
xn--flw351epkView Comments
2016-08-23
2016-08-23Yes
xn--kpu716fpkView Comments
2016-08-23
2016-08-23No
xn--pbt977cpkView Comments
2016-08-23
2016-08-23No
xn--qcka1pmcpkView Comments
2016-08-23
2016-08-23Yes
zippkView Comments
2016-08-23
2016-08-23No
quebecukView Comments
2016-08-23
2016-08-23No
ableirView Comments
2016-08-17
2016-08-17No
booirView Comments
2016-08-17
2016-08-17No
bostikirView Comments
2016-08-17
2016-08-17Yes
calirView Comments
2016-08-17
2016-08-17No
camirView Comments
2016-08-17
2016-08-17No
cbsirView Comments
2016-08-17
2016-08-17Yes
channelirView Comments
2016-08-17
2016-08-17No
chintaiirView Comments
2016-08-17
2016-08-17Yes
dadirView Comments
2016-08-17
2016-08-17No
dayirView Comments
2016-08-17
2016-08-17No
dclkirView Comments
2016-08-17
2016-08-17No
devirView Comments
2016-08-17
2016-08-17No
doctorirView Comments
2016-08-17
2016-08-17No
eatirView Comments
2016-08-17
2016-08-17No
ecoirView Comments
2016-08-17
2016-08-17No
esqirView Comments
2016-08-17
2016-08-17No
flyirView Comments
2016-08-17
2016-08-17No
fujixeroxirView Comments
2016-08-17
2016-08-17Yes
gamesirView Comments
2016-08-17
2016-08-17No
gbizirView Comments
2016-08-17
2016-08-17No
gdnirView Comments
2016-08-17
2016-08-17No
gleirView Comments
2016-08-17
2016-08-17No
gugeirView Comments
2016-08-17
2016-08-17No
hangoutirView Comments
2016-08-17
2016-08-17No
ikanoirView Comments
2016-08-17
2016-08-17Yes
jcpirView Comments
2016-08-17
2016-08-17Yes
mapirView Comments
2016-08-17
2016-08-17No
memeirView Comments
2016-08-17
2016-08-17No
movirView Comments
2016-08-17
2016-08-17No
newirView Comments
2016-08-17
2016-08-17No
phdirView Comments
2016-08-17
2016-08-17No
prodirView Comments
2016-08-17
2016-08-17No
profirView Comments
2016-08-17
2016-08-17No
quebecirView Comments
2016-08-17
2016-08-17No
rsvpirView Comments
2016-08-17
2016-08-17No
searchirView Comments
2016-08-17
2016-08-17No
sfrirView Comments
2016-08-17
2016-08-17Yes
showtimeirView Comments
2016-08-17
2016-08-17Yes
totalirView Comments
2016-08-17
2016-08-17Yes
watchesirView Comments
2016-08-17
2016-08-17No

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

pk Comments

By Syed Iftikhar H Shah, Director IT, Ministry of IT, Government of Pakistan

With reference to subject matter our Pakistan’s instance is that we also have the same issue as some government has already raised to the concerned quarters. In this regard, the major issue is that such subject proposal will create confusion in the domain name system for the internet community particularly for out internet community due to lack of awareness and capacity building of our users for such domain name schemes of. So, it is suggested that ICANN, GAC and the relevant bodies, local communities of the world may further deliberate on the subject matter and then proceed accordingly In this regard, awareness program may also be launched by the ICANN globally and in developing countries as a special case.

In view of the above, it is recommended that GAC may take the subject matter with ICANN. In current situation we would ask ICANN not to proceed with releasing Pakistanis country code and names at 2nd level for all new gTLDs.


uk Comments

By Landcruise.COM, Diluted, Blurred & Infringed .COM Domain Name Registrant, N/A > Above can't be blank.

Hi ICANN & NTIAgov:

PointQuébec Inc with their .Quebec are intent on unfairly creating Consumer Confusion with CentralNic's .COM Based - Domain Name.

Quebec's mock Provincial .qc.COM has a Creation Date: 1998-05-21; and it's been well marketed too.

While Quebec based businesses predominantly use NTIA / US Law's ACPA Governed & Protected .COMs for Worldwide exposure, under RFC-1591, they also use Regional .CA identifier too.

The fact that CentralNic's racket is forcing .COM Registrants to purchase Defensive Registrations under the 2nd Level .COM Domain, at the 3rd .COM Level is irrelevant.

A dotQUEBEC is simply another example of ICANN exercising it's monopoly to generate more "not for profit" profit.

Regards
Landcruise Montreal.

ir Comments

By H.S.Shahhoseini, Advisor of Information Technology Organization of Iran, International Office

Please find following comment which is official statement of Iran ICT Deputy Minister and Head of Information Technology Organization of Iran. Also similar letter has been sent to GAC Secretariat by email.


Dear GAC Secretariat

Re: Requests for Release of Two-Letter Second-Level Domains in gTLDs

As Islamic Republic of IRAN GAC Representative, I would like to express our concerns about the likelihood of confusion between "ir" and the corresponding ccTLD. We, hereby, ask the related authorities to inform us of any request including "ir" and other possibly two character labels which are similar to "ir" in order to concluding an explicit agreement with us for releasing Two-Letter Second-Level Domains in gTLDs.
So again we categorically reject any such release unless our explicit agreement is obtained.

Sincerely yours,
Nasrollah Jahangard
I.R. Iran GAC Representative
Deputy Minister of ICT and
Head of Information Technology Organization of Iran


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