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 Government | Last updated | RO Mitigation Plan | RO Name | BRAND TLD |
---|---|---|---|---|---|---|
stada | su | View Comments 2016-03-22 | 2016-08-15 | Yes | ||
statefarm | su | View Comments 2016-03-22 | 2016-08-15 | Yes | ||
toray | su | View Comments 2016-03-22 | 2016-08-15 | Yes | ||
weber | su | View Comments 2016-03-22 | 2016-08-15 | Yes | ||
williamhill | su | View Comments 2016-03-22 | 2016-08-15 | Yes | ||
wolterskluwer | su | View Comments 2016-03-22 | 2016-08-15 | View Mitigationwolterskluwer MitigationBy Wolters Kluwer N.V. Proposed Measure to Avoid Confusion—Brand TLD (Specification 13) 2016-04-05 | Wolters Kluwer N.V. | Yes |
cam | su | View Comments 2016-08-15 | 2016-08-15 | No | ||
doctor | su | View Comments 2016-08-15 | 2016-08-15 | No | ||
fujixerox | su | View Comments 2016-08-15 | 2016-08-15 | Yes | ||
games | su | View Comments 2016-08-15 | 2016-08-15 | No | ||
gdn | su | View Comments 2016-08-15 | 2016-08-15 | No | ||
ikano | su | View Comments 2016-08-15 | 2016-08-15 | Yes | ||
jcp | su | View Comments 2016-08-15 | 2016-08-15 | Yes | ||
quebec | su | View Comments 2016-08-15 | 2016-08-15 | No | ||
total | su | View Comments 2016-08-15 | 2016-08-15 | Yes | ||
wtc | su | View Comments 2016-08-15 | 2016-08-15 | Yes | ||
able | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
boo | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
bostik | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
cal | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
cam | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
cbs | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
channel | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
chintai | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
dad | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
day | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
dclk | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
dev | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
doctor | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
eat | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
eco | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
esq | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
fly | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
fujixerox | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
games | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
gbiz | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
gdn | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
gle | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
guge | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
hangout | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
ikano | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
jcp | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
map | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
meme | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
mov | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
new | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
phd | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
prod | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
prof | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
quebec | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
rsvp | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
search | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
sfr | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
showtime | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
total | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
watches | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
wtc | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
xn--flw351e | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
xn--kpu716f | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
xn--pbt977c | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
xn--qcka1pmc | vn | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
zip | vn | View Comments 2016-08-17 | 2016-08-17 | No | ||
able | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
boo | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
bostik | mx | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
cal | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
cam | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
cbs | mx | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
channel | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
chintai | mx | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
dad | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
day | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
dclk | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
dev | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
doctor | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
eat | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
eco | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
esq | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
fly | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
fujixerox | mx | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
games | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
gbiz | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
gdn | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
gle | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
guge | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
hangout | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
ikano | mx | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
jcp | mx | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
map | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
meme | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
mov | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
new | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
phd | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
prod | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
prof | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
quebec | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
rsvp | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
search | mx | View Comments 2016-08-17 | 2016-08-17 | No | ||
sfr | mx | View Comments 2016-08-17 | 2016-08-17 | Yes | ||
showtime | mx | View Comments 2016-08-17 | 2016-08-17 | Yes |
su Comments
By Yulia Elanskaya, Deputy Director of International Cooperation Department, Ministry of Telecom and Mass Communications of the Russian Federation
Russia objects the release of Two-Character combination “.su” at the second level under any kind/all gTLD.
We are concerned that the deceptive similarity of these two-letter combinations with the country code ccTLD creates the risk of confusion and misleading of Internet users.
This requirement should apply to all current and future requests. However, we are prepared to discuss potential mitigation measures to avoid confusion and/or any unintended consequences with the corresponding country code if any to be proposed.
su Comments
By Yulia Elanskaya, Deputy Director of International Cooperation Department, Ministry of Telecom and Mass Communications of the Russian Federation
With regards to public consultation process to the draft criteria proposed by ICANN’s GDD Russia would like to use the opportunity to address our concerns about confusion with two-letter country/territory codes at the second level under New gTLDs.
First of all, we also have the same problem as some governments and had already pointed out that it may create confusion with particular ccTLDs and the risk of misleading of Internet users.
In order to avoid any unintended consequences in future, Russia would like to reiterates our request towards ICANN to put on hold any existing requests and not to proceed with releasing Russian country codes and names at the second level under all New gTLDs.
Secondly, we in general agree that there would be useful to establish a list of clear measures that a gTLD registry must implement in order to release from reservation currently reserved two-letter second-level domains and we are prepared to discuss potential mitigation measures to avoid confusion and/or any unintended consequences with the corresponding country code. However, we oppose to allow currently reserved two-letter second-level domains to be released for all gTLD registries at this particular stage.
Further study in all aspects on the advantages and disadvantages respectively is required. We believe that the proposed measures are not quite effective and adequate in addressing the issue of confusion with two-letter country/territory codes at the second level since do not consider the whole picture with corresponding risks and all possible concerns.
Last but not least, we cannot recognize that the proposed measures are consistent with appropriate GAC advice and proposed measures and the actions recommended by the GAC at its Helsinki Communiqué (30th June, 2016).
vn Comments
By Le Thi Ngoc Mo, Deputy Director General of Vietnam Telecommunications Authority (VNTA), Ministry of Information and Communication (MIC)
Dear ICANN,
In response to ICANN’s proposal of measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes, we do not agree with the Exclusive Availability Pre-Registration Period as a measure to avoid confusion. The proposed measure is not clear that whether names would be made available to governments at a fee or no charge. In case governments have to pay fees for the protection of their names, it is not resonable and it is impossible to developing countries.
We would like to ask ICANN to keep the reservation of the two character label strings specified in the ISO 3166-1 alpha-2 standard. Those strings are released only if the Registry Operator reaches a formal agreement with the related government or country-code manager. Moreover, we believe that every mitigation plan proposed to avoid confusion with the corresponding country code should be subjected to the approval by ICANN only after being approved by the respective government/ccTLD manager.
Best Regards,
Le Thi Ngoc Mo (Ms)
Deputy Director General,
Viet Nam Telecommunications Authority (VNTA)
Ministry of Information Communications (MIC), Viet Nam.
mx Comments
By Miguel Ángel Muñoz Petrichole, Deputy Director of International Affairs Telecommunications, Secretariat of Communications and Transport
Comments of the Mexican Administrations to the document “Proposed Measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes.”
Mexico considers that the proposed measures are not enough to avoid confusion with corresponding country codes. In contrast, we believe that the release of country codes in the Second Level Domain (SLD) could destabilize the domain name system.
Regarding the proposed measures, Mexico considers the following:
• To maintain the exclusivity of a country code for a 30-day period in favor of the related government does not necessarily contributes to consumer choice or competitiveness. Besides, it could produce additional costs to governments or country code managers who wish to obtain a country code under a new gTLD.
• Likewise, it will require additional efforts and resources to review each new policy that every new gTLD operator publishes.
Mexico considers that the protection of the country codes in the ISO-3166 list should not be released. Having the offer to register a country code as a SLD would foster combinations of domain name registrations in the third level of new gTLDs. This does not contribute to the objective of this round for new gTLDs, in which it sought to increase the available options only at the root level, taking into account that other options of registration already were available and covered by other top level domains (TLDs).
It is worth noting that the initial conception of the DNS, sought to foster the registration of new domain names with a specific orientation of diverse nature: some community-territorial, some other with technical or network orientation, military, commercial, among others*, and the new gTLDs were equally conceived in this sense.
Based on the principle of parsimony, which implicates that entities should not multiple needlessly and should use the available resources; given the existence of ccTLD, which purpose is the identification of a country or community, there would be no need to have it in the SLD under new gTLDs.
*See Postel, J. (1994). RFC1591, available on: https://www.ietf.org/rfc/rfc1591.txt , among other reference documents.