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
academyytView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
accountantytView Comments
2015-12-04
2015-12-04View Mitigation

accountant Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:

1. Registry Operator will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant governments, and provide a written report in response; and

b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants.

3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, locked, placed on hold, transferred or deleted. Thus, all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-25

Famous Four Media LimitedNo
accountantsytView Comments
2015-12-04
2015-12-04View Mitigation

accountants Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
agencyytView Comments
2015-12-04
2015-12-04View Mitigation

agency Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
airforceytView Comments
2015-12-04
2015-12-04View Mitigation

airforce Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
archiytView Comments
2015-12-04
2015-12-04View Mitigation

archi Mitigation

By Starting Dot

The proposed measure to avoid confusion for .ARCHI applies across all two-character labels.

The proposed measure can be found in the file attached.


View Documents
2016-04-25

Starting DotNo
armyytView Comments
2015-12-04
2015-12-04View Mitigation

army Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
attorneyytView Comments
2015-12-04
2015-12-04View Mitigation

attorney Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
auctionytView Comments
2015-12-04
2015-12-04View Mitigation

auction Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
bankytView Comments
2015-12-04
2015-12-04View Mitigation

bank Mitigation

By fTLD Registry Services, LLC

Please see the attached file that details fTLD Registry Services' implementation plan for .BANK and .INSURANCE to avoid confusion with corresponding country codes.


View Documents
2016-04-20

fTLD Registry Services, LLCNo
beerytView Comments
2015-12-04
2015-12-04View Mitigation

beer Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
betytView Comments
2015-12-04
2015-12-04View Mitigation

bet Mitigation

By Afilias

Afilias has reviewed the comments submitted for the release of certain 2 character labels. We have taken these comments into consideration and will will continue to block the respective labels at the second level until further notice to avoid confusion.


2016-04-20

AfiliasNo
bidytView Comments
2015-12-04
2015-12-04View Mitigation

bid Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:

1. Registry Operator will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant governments, and provide a written report in response; and

b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants.

3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, locked, placed on hold, transferred or deleted. Thus, all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-25

Famous Four Media LimitedNo
bingoytView Comments
2015-12-04
2015-12-04View Mitigation

bingo Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
bioytView Comments
2015-12-04
2015-12-04View Mitigation

bio Mitigation

By Starting Dot

This response applies across all two-character labels.

PROPOSED MEASURE TO AVOID CONFUSION – .BIO

StartingDot is the Registry Operator of the .BIO generic Top Level Domain string (gTLD) since June 2, 2014.

The .BIO gTLD is generally available to all Registrants, and among others, to actors in the fields of agriculture, food and farming. The .BIO gTLD intends to serve all of these topics and areas, while ensuring that national and international organic standards are respected.

The .BIO gTLD is established on the basis of the core organic agriculture principles that have been formulated by the International Federation of Organic Agriculture Movements (“IFOAM – Organics International”). IFOAM – Organics International is an official Partner of the .BIO Registry Operator.

The Principles of Organic Agriculture (“POA”) aim to inspire the organic movement in its full diversity, and to help steer the development of positions, programs and standards in the organic community. They are used as the principal framework for defining the .BIO registration policies. In order to apply for a .BIO domain name, the registrant is required to comply with specific requirements related to organic agriculture compliance mechanisms.

To address the confusion concerns cited by the relevant governments regarding the use of second-level domains (SLDs) in .BIO, StartingDot, has (i) implemented a registration policy for .BIO and (ii) established an Anti-Abuse Policy that mitigates the potential confusion addressed by the governments. Based on the above, StartingDot has:

• Developped and implemented a restricted registration policy for .BIO included in the .BIO Domain Name Policy (“.BIO DNP”). According to the .BIO DNP, although a .BIO domain name can be registered by anyone, specific terms of use apply to Registrants who are producers, transformers and retailers, or otherwise involved in the field of agriculture, food and farming when there is:

- A nexus with the European Union (i.e.: selling, exporting to or trading agricultural or food product in the European Union) or other relevant markets where the word “bio” may be used to refer to legally labeled and marketed organic, biological, ecological, biodynamic, or similarly named goods or intending to do so (“nexus with the European Union”); and

- No nexus with the European Union.

b. The Registrant who has no nexus with the European Union must commit to abiding by the POA.

c. The Registrant who has a nexus with the European Union must commit to abiding by both:

- The POA; and

- The Council Regulation (EC) No 834/2007 of 28 June 2007 on organic production and labeling and its derived legislation, or any regulations in force in other relevant markets (the “E.C Regulations”).

• Made public on StartingDot’s website (www.startingdot.com) the abovementioned .BIO DNP;

• Included the .BIO Domain Name Policy in the StartingDot Registry – Registrar Agreement (RRA) signed with all the appointed registrars for .BIO;

• Enforced the .BIO Domain Name Policy by monitoring registrations on a random basis. StartingDot performs quarterly controls of .BIO registrations together with IFOAM – Organics International and ensures that registrants meet the eligibility criteria established in the .BIO DNP. StartingDot has also developped an Anti-Abuse Policy published on its website, which establishes StartingDot’s actions in case of an abuse of the .BIO domain space.

• Made public on StartingDot’s website (www.startingdot.com) the abovementioned Anti-Abuse Policy which contains specific text with regards to domain names that correspond to a country code described in the ISO 3166-1 alpha-2 standard.

The .BIO Domain Name Policy would not prevent governments from registering domains in the .BIO TLD. However, if the latter register a .BIO domain name they must abide by the principles established under the .BIO DNP .

Finally, as stated in the Anti-Abuse Policy, should a Registrant fail to comply with the Anti-Abuse Policy, the domain name may be subject to cancellation or other penalty measures (domain being locked, placed on hold, transferred or deleted). Thus all Registrants in the .BIO gTLD, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


View Documents
2016-04-25

Starting DotNo
brokerytView Comments
2015-12-04
2015-12-04View Mitigation

broker Mitigation

By dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]

Please find attached a document which outlines the Registry's plans to avoid confusion in respect of the below TLDs:

.Markets
.Trading
.Forex
.Broker
.Spreadbetting
.CFD


View Documents
2016-04-21

dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]No
casinoytView Comments
2015-12-04
2015-12-04View Mitigation

casino Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
clinicytView Comments
2015-12-04
2015-12-04No
cliniqueytView Comments
2015-12-04
2015-12-04View Mitigation

clinique Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.Yes
cloudytView Comments
2015-12-04
2015-12-04View Mitigation

cloud Mitigation

By Aruba PEC SpA

.cloud proposal for Mitigation Measures to Avoid Confusion in the use of domain names corresponding to ccTLDs

Protections

Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:
1. Registry Operator will commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the government of a related country code, and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

Furthermore, the Registry Operator considers the issue of domain name used in a way that generates confusion to be already covered in its Registration Policies (available for review at https://www.get.cloud/policies.aspx), for example in:

9.1 [...] Without limiting any other agreement or policy, by submitting an Application for a domain name an Applicant will be deemed to have warranted that:
[...]
d) it is not submitting the Application or Domain Name Registration request and, upon registration, will not use the Domain Name for an unlawful purpose, contrary to public policy or morality, for offensive purposes, to mislead the public and/or contrary to good and fair business practices;

Should a Registrant fail to comply with the .cloud Registration Policies, the domain name may be canceled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLD, have an obligation to avoid misleading the public by generating confusion also with two letter country codes and there are clear penalties for any failure to do so.

Registry Operator is however also open to further clarify this point by including in its Registration Policies a specific requirement for Registrants of domain names that are two letter Labels that correspond to a country code described in the ISO 3166-1 alpha-2 standard not to use them in a manner that generates confusion with the corresponding country code.



2016-04-25

Aruba PEC SpANo
collegeytView Comments
2015-12-04
2015-12-04No
dentalytView Comments
2015-12-04
2015-12-04View Mitigation

dental Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
dentistytView Comments
2015-12-04
2015-12-04View Mitigation

dentist Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
docsytView Comments
2015-12-04
2015-12-04View Mitigation

docs Mitigation

By Charleston Road Registry Inc. (d/b/a Google Registry)

Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes.


View Documents
2016-04-22

Charleston Road Registry Inc. (d/b/a Google Registry)No
domainsytView Comments
2015-12-04
2015-12-04View Mitigation

domains Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
educationytView Comments
2015-12-04
2015-12-04View Mitigation

education Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
financeytView Comments
2015-12-04
2015-12-04View Mitigation

finance Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
helpytView Comments
2015-12-04
2015-12-04No
lawyerytView Comments
2015-12-04
2015-12-04View Mitigation

lawyer Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
lottoytView Comments
2015-12-04
2015-12-04View Mitigation

lotto Mitigation

By Afilias

Afilias has reviewed the comments submitted for the release of certain 2 character labels. We have taken these comments into consideration and will will continue to block the respective labels at the second level until further notice to avoid confusion.


2016-04-20

AfiliasNo
navyytView Comments
2015-12-04
2015-12-04View Mitigation

navy Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
pharmacyytView Comments
2015-12-04
2015-12-04View Mitigation

pharmacy Mitigation

By National Association of Boards of Pharmacy

Background

The National Association of Boards of Pharmacy® (NABP®), the impartial professional organization that supports state boards of pharmacy in protecting public health, is the exclusive Registry Operator for the .pharmacy Top-Level Domain (TLD). The .pharmacy TLD was established to provide a secure, verified, and trustworthy TLD where consumers around the globe can be sure the medications they buy online are safe. To that end, a global coalition of stakeholders, including NABP and the International Pharmaceutical Federation, developed policies and maintains standards to govern the .pharmacy TLD, ensuring those websites with a .pharmacy domain are safe and legal.

Implementation Plan to Avoid Confusion

To respond to the confusion concerns cited by several governments regarding the use of the second-level domains (SLDs) in the .pharmacy TLD, NABP notes that it currently implements a restricted registration policy for .pharmacy that recognizes the ongoing and critical need for patients’ medications to be managed by a licensed pharmacist and for their medications to be appropriately sourced in accordance with applicable standards of care. A copy of the policy can be found at http://safe.pharmacy/standards-policies. The very fact that .pharmacy verifies that each entity acquiring a .pharmacy SLD meets all applicable regulatory standards, including those addressing pharmacy licensure and valid prescription requirements, prior to allowing that entity to register a .pharmacy domain name avoids any potential confusion between the .pharmacy registration and a country code.

In order to ensure that there will be no confusion between any two character registrations and a country code sharing the same two letters, NABP will administer its verified registry operation in a manner that avoids potential confusion by:
• Continuing to implement a restricted registration policy for .pharmacy that verifies that each entity acquiring a .pharmacy SLD is an eligible member of the pharmacy community and meets all applicable regulatory standards to conduct pharmacy-related business.
• Continuing to implement a restricted registration policy that ensures website content is relevant to pharmacy services and drug information, which provides the opportunity for NABP to proactively identify any potential confusing use of the domain name with a corresponding country code.
• Maintaining, and continuing to create, ongoing “working relationship[s] with the relevant regulatory, or industry self-regulatory, bodies, including developing a strategy to mitigate as much as possible the risks of fraudulent, and other illegal, activities.” See Beijing GAC Communique. NABP will not issue a .pharmacy domain name in a given country until it has created a relationship with the appropriate health care regulators for a jurisdiction.
• Clearly publishing this registration policy on .pharmacy’s registry homepage.
• Including this registration policy in NABP’s Registry-Registrar Agreement with all accredited registrars for the .pharmacy TLD.
• Enforcing this registration policy and ensuring continued compliance. The process for obtaining a .pharmacy domain name is described here: http://www.safe.pharmacy/apply. More detailed instructions and information are available here: http://www.safe.pharmacy/apply/application-instructions.

NABP’s use of .pharmacy two-character domains would not, in and of itself and absent a verification process, cause any confusion with the corresponding two-letter country codes; nonetheless, NABP further contends that it avoids any potential confusion through its strenuous verification requirements and registration policies, which ensure only licensed and verified pharmacy-related entities are permitted to register and use .pharmacy domains.

Request to ICANN in Accordance With Specification 5 of the Registry Agreement

Based on public comments received, no government objecting to the release of its country code offered a specific explanation for the potential confusion arising from the use of a two-character SLD within a verified registry operation (as defined herein); therefore, based on the aforementioned proposal to avoid confusion as a verified registry operation and in accordance with Specification 5 of its Registry Agreement, NABP respectfully requests that Internet Corporation for Assigned Names and Numbers release the remainder of all second-level two-character country code domain names.


View Documents
2016-04-25

National Association of Boards of PharmacyNo
propertiesytView Comments
2015-12-04
2015-12-04View Mitigation

properties Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
propertyytView Comments
2015-12-04
2015-12-04No
sarlytView Comments
2015-12-04
2015-12-04View Mitigation

sarl Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
servicesytView Comments
2015-12-04
2015-12-04View Mitigation

services Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
theatreytView Comments
2015-12-04
2015-12-04No
travelersinsuranceytView Comments
2015-12-04
2015-12-04No
universityytView Comments
2015-12-04
2015-12-04View Mitigation

university Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
voteytView Comments
2015-12-04
2015-12-04No
academywfView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
accountantwfView Comments
2015-12-04
2015-12-04View Mitigation

accountant Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:

1. Registry Operator will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant governments, and provide a written report in response; and

b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants.

3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, locked, placed on hold, transferred or deleted. Thus, all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-25

Famous Four Media LimitedNo
accountantswfView Comments
2015-12-04
2015-12-04View Mitigation

accountants Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
agencywfView Comments
2015-12-04
2015-12-04View Mitigation

agency Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
airforcewfView Comments
2015-12-04
2015-12-04View Mitigation

airforce Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
archiwfView Comments
2015-12-04
2015-12-04View Mitigation

archi Mitigation

By Starting Dot

The proposed measure to avoid confusion for .ARCHI applies across all two-character labels.

The proposed measure can be found in the file attached.


View Documents
2016-04-25

Starting DotNo
armywfView Comments
2015-12-04
2015-12-04View Mitigation

army Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
attorneywfView Comments
2015-12-04
2015-12-04View Mitigation

attorney Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
auctionwfView Comments
2015-12-04
2015-12-04View Mitigation

auction Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
bankwfView Comments
2015-12-04
2015-12-04View Mitigation

bank Mitigation

By fTLD Registry Services, LLC

Please see the attached file that details fTLD Registry Services' implementation plan for .BANK and .INSURANCE to avoid confusion with corresponding country codes.


View Documents
2016-04-20

fTLD Registry Services, LLCNo
beerwfView Comments
2015-12-04
2015-12-04View Mitigation

beer Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
betwfView Comments
2015-12-04
2015-12-04View Mitigation

bet Mitigation

By Afilias

Afilias has reviewed the comments submitted for the release of certain 2 character labels. We have taken these comments into consideration and will will continue to block the respective labels at the second level until further notice to avoid confusion.


2016-04-20

AfiliasNo
bidwfView Comments
2015-12-04
2015-12-04View Mitigation

bid Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:

1. Registry Operator will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant governments, and provide a written report in response; and

b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants.

3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, locked, placed on hold, transferred or deleted. Thus, all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-25

Famous Four Media LimitedNo
bingowfView Comments
2015-12-04
2015-12-04View Mitigation

bingo Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
biowfView Comments
2015-12-04
2015-12-04View Mitigation

bio Mitigation

By Starting Dot

This response applies across all two-character labels.

PROPOSED MEASURE TO AVOID CONFUSION – .BIO

StartingDot is the Registry Operator of the .BIO generic Top Level Domain string (gTLD) since June 2, 2014.

The .BIO gTLD is generally available to all Registrants, and among others, to actors in the fields of agriculture, food and farming. The .BIO gTLD intends to serve all of these topics and areas, while ensuring that national and international organic standards are respected.

The .BIO gTLD is established on the basis of the core organic agriculture principles that have been formulated by the International Federation of Organic Agriculture Movements (“IFOAM – Organics International”). IFOAM – Organics International is an official Partner of the .BIO Registry Operator.

The Principles of Organic Agriculture (“POA”) aim to inspire the organic movement in its full diversity, and to help steer the development of positions, programs and standards in the organic community. They are used as the principal framework for defining the .BIO registration policies. In order to apply for a .BIO domain name, the registrant is required to comply with specific requirements related to organic agriculture compliance mechanisms.

To address the confusion concerns cited by the relevant governments regarding the use of second-level domains (SLDs) in .BIO, StartingDot, has (i) implemented a registration policy for .BIO and (ii) established an Anti-Abuse Policy that mitigates the potential confusion addressed by the governments. Based on the above, StartingDot has:

• Developped and implemented a restricted registration policy for .BIO included in the .BIO Domain Name Policy (“.BIO DNP”). According to the .BIO DNP, although a .BIO domain name can be registered by anyone, specific terms of use apply to Registrants who are producers, transformers and retailers, or otherwise involved in the field of agriculture, food and farming when there is:

- A nexus with the European Union (i.e.: selling, exporting to or trading agricultural or food product in the European Union) or other relevant markets where the word “bio” may be used to refer to legally labeled and marketed organic, biological, ecological, biodynamic, or similarly named goods or intending to do so (“nexus with the European Union”); and

- No nexus with the European Union.

b. The Registrant who has no nexus with the European Union must commit to abiding by the POA.

c. The Registrant who has a nexus with the European Union must commit to abiding by both:

- The POA; and

- The Council Regulation (EC) No 834/2007 of 28 June 2007 on organic production and labeling and its derived legislation, or any regulations in force in other relevant markets (the “E.C Regulations”).

• Made public on StartingDot’s website (www.startingdot.com) the abovementioned .BIO DNP;

• Included the .BIO Domain Name Policy in the StartingDot Registry – Registrar Agreement (RRA) signed with all the appointed registrars for .BIO;

• Enforced the .BIO Domain Name Policy by monitoring registrations on a random basis. StartingDot performs quarterly controls of .BIO registrations together with IFOAM – Organics International and ensures that registrants meet the eligibility criteria established in the .BIO DNP. StartingDot has also developped an Anti-Abuse Policy published on its website, which establishes StartingDot’s actions in case of an abuse of the .BIO domain space.

• Made public on StartingDot’s website (www.startingdot.com) the abovementioned Anti-Abuse Policy which contains specific text with regards to domain names that correspond to a country code described in the ISO 3166-1 alpha-2 standard.

The .BIO Domain Name Policy would not prevent governments from registering domains in the .BIO TLD. However, if the latter register a .BIO domain name they must abide by the principles established under the .BIO DNP .

Finally, as stated in the Anti-Abuse Policy, should a Registrant fail to comply with the Anti-Abuse Policy, the domain name may be subject to cancellation or other penalty measures (domain being locked, placed on hold, transferred or deleted). Thus all Registrants in the .BIO gTLD, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


View Documents
2016-04-25

Starting DotNo
brokerwfView Comments
2015-12-04
2015-12-04View Mitigation

broker Mitigation

By dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]

Please find attached a document which outlines the Registry's plans to avoid confusion in respect of the below TLDs:

.Markets
.Trading
.Forex
.Broker
.Spreadbetting
.CFD


View Documents
2016-04-21

dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]No
casinowfView Comments
2015-12-04
2015-12-04View Mitigation

casino Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
clinicwfView Comments
2015-12-04
2015-12-04No
cliniquewfView Comments
2015-12-04
2015-12-04View Mitigation

clinique Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.Yes
cloudwfView Comments
2015-12-04
2015-12-04View Mitigation

cloud Mitigation

By Aruba PEC SpA

.cloud proposal for Mitigation Measures to Avoid Confusion in the use of domain names corresponding to ccTLDs

Protections

Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:
1. Registry Operator will commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the government of a related country code, and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

Furthermore, the Registry Operator considers the issue of domain name used in a way that generates confusion to be already covered in its Registration Policies (available for review at https://www.get.cloud/policies.aspx), for example in:

9.1 [...] Without limiting any other agreement or policy, by submitting an Application for a domain name an Applicant will be deemed to have warranted that:
[...]
d) it is not submitting the Application or Domain Name Registration request and, upon registration, will not use the Domain Name for an unlawful purpose, contrary to public policy or morality, for offensive purposes, to mislead the public and/or contrary to good and fair business practices;

Should a Registrant fail to comply with the .cloud Registration Policies, the domain name may be canceled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLD, have an obligation to avoid misleading the public by generating confusion also with two letter country codes and there are clear penalties for any failure to do so.

Registry Operator is however also open to further clarify this point by including in its Registration Policies a specific requirement for Registrants of domain names that are two letter Labels that correspond to a country code described in the ISO 3166-1 alpha-2 standard not to use them in a manner that generates confusion with the corresponding country code.



2016-04-25

Aruba PEC SpANo
collegewfView Comments
2015-12-04
2015-12-04No
dentalwfView Comments
2015-12-04
2015-12-04View Mitigation

dental Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
dentistwfView Comments
2015-12-04
2015-12-04View Mitigation

dentist Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
docswfView Comments
2015-12-04
2015-12-04View Mitigation

docs Mitigation

By Charleston Road Registry Inc. (d/b/a Google Registry)

Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes.


View Documents
2016-04-22

Charleston Road Registry Inc. (d/b/a Google Registry)No
domainswfView Comments
2015-12-04
2015-12-04View Mitigation

domains Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
educationwfView Comments
2015-12-04
2015-12-04View Mitigation

education Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
financewfView Comments
2015-12-04
2015-12-04View Mitigation

finance Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
helpwfView Comments
2015-12-04
2015-12-04No
lawyerwfView Comments
2015-12-04
2015-12-04View Mitigation

lawyer Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
lottowfView Comments
2015-12-04
2015-12-04View Mitigation

lotto Mitigation

By Afilias

Afilias has reviewed the comments submitted for the release of certain 2 character labels. We have taken these comments into consideration and will will continue to block the respective labels at the second level until further notice to avoid confusion.


2016-04-20

AfiliasNo
navywfView Comments
2015-12-04
2015-12-04View Mitigation

navy Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
pharmacywfView Comments
2015-12-04
2015-12-04View Mitigation

pharmacy Mitigation

By National Association of Boards of Pharmacy

Background

The National Association of Boards of Pharmacy® (NABP®), the impartial professional organization that supports state boards of pharmacy in protecting public health, is the exclusive Registry Operator for the .pharmacy Top-Level Domain (TLD). The .pharmacy TLD was established to provide a secure, verified, and trustworthy TLD where consumers around the globe can be sure the medications they buy online are safe. To that end, a global coalition of stakeholders, including NABP and the International Pharmaceutical Federation, developed policies and maintains standards to govern the .pharmacy TLD, ensuring those websites with a .pharmacy domain are safe and legal.

Implementation Plan to Avoid Confusion

To respond to the confusion concerns cited by several governments regarding the use of the second-level domains (SLDs) in the .pharmacy TLD, NABP notes that it currently implements a restricted registration policy for .pharmacy that recognizes the ongoing and critical need for patients’ medications to be managed by a licensed pharmacist and for their medications to be appropriately sourced in accordance with applicable standards of care. A copy of the policy can be found at http://safe.pharmacy/standards-policies. The very fact that .pharmacy verifies that each entity acquiring a .pharmacy SLD meets all applicable regulatory standards, including those addressing pharmacy licensure and valid prescription requirements, prior to allowing that entity to register a .pharmacy domain name avoids any potential confusion between the .pharmacy registration and a country code.

In order to ensure that there will be no confusion between any two character registrations and a country code sharing the same two letters, NABP will administer its verified registry operation in a manner that avoids potential confusion by:
• Continuing to implement a restricted registration policy for .pharmacy that verifies that each entity acquiring a .pharmacy SLD is an eligible member of the pharmacy community and meets all applicable regulatory standards to conduct pharmacy-related business.
• Continuing to implement a restricted registration policy that ensures website content is relevant to pharmacy services and drug information, which provides the opportunity for NABP to proactively identify any potential confusing use of the domain name with a corresponding country code.
• Maintaining, and continuing to create, ongoing “working relationship[s] with the relevant regulatory, or industry self-regulatory, bodies, including developing a strategy to mitigate as much as possible the risks of fraudulent, and other illegal, activities.” See Beijing GAC Communique. NABP will not issue a .pharmacy domain name in a given country until it has created a relationship with the appropriate health care regulators for a jurisdiction.
• Clearly publishing this registration policy on .pharmacy’s registry homepage.
• Including this registration policy in NABP’s Registry-Registrar Agreement with all accredited registrars for the .pharmacy TLD.
• Enforcing this registration policy and ensuring continued compliance. The process for obtaining a .pharmacy domain name is described here: http://www.safe.pharmacy/apply. More detailed instructions and information are available here: http://www.safe.pharmacy/apply/application-instructions.

NABP’s use of .pharmacy two-character domains would not, in and of itself and absent a verification process, cause any confusion with the corresponding two-letter country codes; nonetheless, NABP further contends that it avoids any potential confusion through its strenuous verification requirements and registration policies, which ensure only licensed and verified pharmacy-related entities are permitted to register and use .pharmacy domains.

Request to ICANN in Accordance With Specification 5 of the Registry Agreement

Based on public comments received, no government objecting to the release of its country code offered a specific explanation for the potential confusion arising from the use of a two-character SLD within a verified registry operation (as defined herein); therefore, based on the aforementioned proposal to avoid confusion as a verified registry operation and in accordance with Specification 5 of its Registry Agreement, NABP respectfully requests that Internet Corporation for Assigned Names and Numbers release the remainder of all second-level two-character country code domain names.


View Documents
2016-04-25

National Association of Boards of PharmacyNo
propertieswfView Comments
2015-12-04
2015-12-04View Mitigation

properties Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
propertywfView Comments
2015-12-04
2015-12-04No
sarlwfView Comments
2015-12-04
2015-12-04View Mitigation

sarl Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
serviceswfView Comments
2015-12-04
2015-12-04View Mitigation

services Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
theatrewfView Comments
2015-12-04
2015-12-04No
travelersinsurancewfView Comments
2015-12-04
2015-12-04No
universitywfView Comments
2015-12-04
2015-12-04View Mitigation

university Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
votewfView Comments
2015-12-04
2015-12-04No
aarpvnView Comments
2015-12-02
2015-12-02View Mitigation

aarp Mitigation

By AARP

.AARP gTLD Confusion Avoidance Plan

AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

1. .AARP is identical to a qualifying registered trademark;
2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement;
3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and
5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement.

Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator.

With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13.


View Documents
2016-04-25

AARPYes
abbvnView Comments
2015-12-02
2015-12-02View Mitigation

abb Mitigation

By ABB Ltd

Provide a brief explanation of the TLD:
ABB Ltd has applied for .ABB to run a closed .brand environment.

Protections
ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .ABB is identical to a qualifying registered trademark;
2. .ABB is not a Generic String, as this is defined in Specification 11;
3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy;
5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator.
By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

ABB LtdYes
abbottvnView Comments
2015-12-02
2015-12-02View Mitigation

abbott Mitigation

By Abbott Laboratories, Inc.

Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

1. .ABBOTT is identical to a qualifying registered trademark;
2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement;
3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and
5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement.

Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator.

With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13.


2016-04-22

Abbott Laboratories, Inc.Yes
abogadovnView Comments
2015-12-02
2015-12-02View Mitigation

abogado Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
academyvnView Comments
2015-12-02
2015-12-02View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
accenturevnView Comments
2015-12-02
2015-12-02View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

Accenture plc for the .ACCENTURE TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Accenture plc will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .ACCENTURE is identical to a qualifying registered trademark;
2. .ACCENTURE is not a Generic String, as this is defined in Specification 11;
3. .ACCENTURE TLD has developed and will implement a closed registration policy for .ACCENTURE that requires that all domain names in the .ACCENTURE TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .ACCENTURE TLD will clearly publish this registration policy;
5. .ACCENTURE TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.
Compliance with Specification 13 prohibits the .ACCENTURE TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ACCENTURE TLD is a proprietary space in which all second-level domains in the TLD are being operated by Accenture plc - its Affiliates and Trademark Licensees and not the Government or the corresponding country code operator.
By this letter, Accenture plc confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-20

Accenture plcYes
accountantvnView Comments
2015-12-02
2015-12-02View Mitigation

accountant Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:

1. Registry Operator will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant governments, and provide a written report in response; and

b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants.

3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, locked, placed on hold, transferred or deleted. Thus, all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-25

Famous Four Media LimitedNo
accountantsvnView Comments
2015-12-02
2015-12-02View Mitigation

accountants Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
actorvnView Comments
2015-12-02
2015-12-02View Mitigation

actor Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
adultvnView Comments
2015-12-02
2015-12-02View Mitigation

adult Mitigation

By ICM Registry

Protections

Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:

1. Registry Operator will commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any governments, and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

Furthermore, we have the following Anti-Abuse Policy:

Registry has the right, pursuant to its Registry-Registrant Agreement, to immediately deny, cancel, terminate, suspend, lock, hold, or transfer any domain name and/or registration to ensure registrant’s compliance with the following Anti-Abuse Policy.

1. Accurate Registration Information
Registrant represents and warrants to have provided current, complete, and accurate information in connection with its registration and agrees to correct and update this information to ensure that it remains current, complete, and accurate throughout the term of any resulting registration in a TLD. Registrant’s obligation to provide current, accurate, and complete information is a material element of the Registry-Registrant Agreement, and the registry reserves the right to immediately deny, cancel, terminate, suspend, lock, or transfer any registration if it determines, in its sole discretion, that the information is materially inaccurate.

2. Child Protection Labeling
Registrant understands that Registry Operator may label the sites in the TLD and any site to which such sites are automatically redirected irrespective of the top-level domain for child protection purposes; registrant consents to such labeling.

3. Prohibition on Child Abuse Images and Conduct or Content Designed to Suggest the Presence of Child Abuse Images
The term “child abuse images” is defined as any photograph, film, video, picture, or computer or computer-generated image or picture, whether made or produced by electronic, mechanical, or other means, depicting child sexual abuse as stated in the United Nations Convention on the Rights of the Child. Registrant’s sites in the TLD shall not display any child abuse images. Registrant’s sites in the TLD shall not engage in practices that are designed to suggest the presence of child abuse images, including, without limitation, the use of meta-tags for that purpose. Registry Operator will refer any sites in a TLD that are reported to the Registry Operator to be in violation of this policy to child safety hotlines like the National Center for Missing and Exploited Children (NCMEC), the Internet Watch Foundation (IWF), or the International Association of Internet Hotlines (INHOPE).

4. Prohibition on Abusive Registrations
No registrant may register an abusive second-level domain name in the TLD including, without limitation, domain names that infringe the intellectual property rights of a third party, including common law trademark rights; domain names that are obvious variants of well-known trademarks not belonging to the registrant; or domain names that suggest the presence of child abuse images.

5. Prohibition on Malicious Conduct
No registrant shall use or permit use of a domain name in the TLD for or in connection with email spoofing, phishing, spam, or other forms of malicious behavior.

6. Ongoing Best Practices Policies
Registry Operator will revise this Anti-Abuse Policy or the Registry-Registrant Agreement to include commercially reasonable best practices policies developed by the International Foundation for Online Responsibility (IFFOR) that are designed to promote responsible business practices related to (i) combating online child abuse images, (ii) facilitating user choice and parental control regarding access to online adult entertainment, (iii) protecting free expression rights, and/or (iv) protecting the privacy, security, and consumer rights of consenting adult consumers of online adult entertainment goods and services; registrant consents to adhere to such policies.

The Registrant of a domain name, as recorded in the Registry Service, will be responsible for:
a. the use of their domain name;
b. ensuring that the use of the domain name, where that domain name is a two letter Label that corresponds to a country code described in the ISO 3166-1 alpha-2 standard, avoids confusion with the corresponding country code;”

Should a Registrant fail to comply with the Anti-Abuse Policy, the domain name may be cancelled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLD, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-19

ICM Registry No
aegvnView Comments
2015-12-02
2015-12-02View Mitigation

aeg Mitigation

By Aktiebolaget Electrolux

Provide a brief explanation of the TLD:
Aktiebolaget Electrolux has applied for .[TLD] to run a closed .brand environment.

Protections
Aktiebolaget Electrolux for the .[TLD] TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Aktiebolaget Electrolux will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .[TLD] is identical to a qualifying registered trademark;
2. .[TLD] is not a Generic String, as this is defined in Specification 11;
3. .[TLD] TLD has developed and will implement a closed registration policy for .[TLD] that requires that all domain names in the .[TLD] TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .[TLD] TLD will clearly publish this registration policy;
5. .[TLD] TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .[TLD] TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .[TLD] TLD is a proprietary space in which all second-level domains in the TLD are being operated by Aktiebolaget Electrolux, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator.
By this letter Aktiebolaget Electrolux confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Aktiebolaget ElectroluxYes
agencyvnView Comments
2015-12-02
2015-12-02View Mitigation

agency Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
aigvnView Comments
2015-12-02
2015-12-02View Mitigation

aig Mitigation

By American International Group, Inc.

Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment.
Protections
American International Group, Inc. for the .AIG TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the American International Group, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .AIG is identical to a qualifying registered trademark;
2. .AIG is not a Generic String, as this is defined in Specification 11;
3. .AIG TLD has developed and will implement a closed registration policy for .AIG that requires that all domain names in the .AIG TLD be registered ONLY by American International Group, Inc., its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .AIG TLD will clearly publish this registration policy;
5. .AIG TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.
Compliance with Specification 13 prohibits the .AIG TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .AIG TLD is a proprietary space in which all second-level domains in the TLD are being operated by American International Group, Inc., its Affiliates and Trademark Licensees and not the [GOVERNMENT] or the corresponding country code operator.
By this [LETTER] American International Group, Inc. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-20

American International Group, Inc.Yes
airforcevnView Comments
2015-12-02
2015-12-02View Mitigation

airforce Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
allfinanzvnView Comments
2015-12-02
2015-12-02View Mitigation

allfinanz Mitigation

By Allfinanz Deutsche Vermögensberatung Aktiengesellschaft

Please find Allfinanz Deutsche Vermögensberatung Aktiengesellschaft's "Mitigation Measures to Avoid Confusion" (concerning 2-letter labels in general) for the “.ALLFINANZ” attached.


View Documents
2016-04-23

Allfinanz Deutsche Vermögensberatung AktiengesellschaftNo
allyvnView Comments
2015-12-02
2015-12-02Yes
amsterdamvnView Comments
2015-12-02
2015-12-02View Mitigation

amsterdam Mitigation

By City of Amsterdam

For the top level domain .AMSTERDAM we would like to use two letter domains and we propose the following measures to avoid confusion.

A brief explanation of the TLD:
.amsterdam is a geographic TLD for the City of Amsterdam; the City of Amsterdam is the designated Registry Operator. The toplevel domain is open, anyone in the world can register domain names.

Proposed measures to avoid confusion
The proposed protections to avoid confusion with country codes at the second level outlined below specifically apply to: ci, cn, eg, hk, il, in, it, me, pt and sg.

Protections
The Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:
• Registry Operator will commit to investigate any reports of misuse, including misleading or deceptive conduct, including those from the government of a related country code, and provide a written report in response; and
• where, in Registry Operator's sole opinion, misuse has occurred, cause the domain name's records to be removed from the DNS.

Policy measures
Contained within our Acceptable Use Policy for .amsterdam is the following text:
".Abuse in the context of this Policy shall be defined as an action that causes actual and substantial harm, or is a material predicate of such harm, or is illegal, illegitimate, or otherwise contrary to this Policy, including, but not limited to, the following:
...
h. Violation of any applicable local, state, national or international law or regulation by use of a Domain Name;
i . The confusing use of a 2character domain name that corresponds to a country code as described in the ISO 3166 alpha 2 standard with the corresponding country code...”

Should a Registrant fail to comply with the Acceptable Use Policy, the registry has the right to lock, transfer or cancel any offending domain name. Thus all Registrants in the TLDs, have an obligation to avoid confusion with two letter country codes and the City of Amsterdam has clear penalties for any failure to do so.


View Documents
2016-05-09

City of AmsterdamNo
analyticsvnView Comments
2015-12-02
2015-12-02View Mitigation

analytics Mitigation

By Karen L. Day

Please see the attached documents outlining our registry's plans to avoid confusion with certain 2 character labels as previously requested.


View Documents
2016-05-06

Karen L. DayNo
anzvnView Comments
2015-12-02
2015-12-02View Mitigation

anz Mitigation

By Australia and New Zealand Banking Group Limited

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Australia and New Zealand Banking Group Limited has applied for .ANZ to run a closed .brand environment.
Protections
Australia and New Zealand Banking Group Limited for the .ANZ TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Australia and New Zealand Banking Group Limited will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .ANZ is identical to a qualifying registered trademark;
2. .ANZ is not a Generic String, as this is defined in Specification 11;
3. .ANZ has developed and will implement a closed registration policy for .ANZ that requires that all domain names in the .ANZ TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .ANZ TLD will clearly publish this registration policy;
5. .ANZ TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.
Compliance with Specification 13 prohibits the .ANZ TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ANZ TLD is a proprietary space in which all second-level domains in the TLD are being operated by Australia and New Zealand Banking Group Limited - its Affiliates and Trademark Licensees and not the Government or the corresponding country code operator.
By this letter, Australia and New Zealand Banking Group Limited confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13


2016-04-22

Australia and New Zealand Banking Group LimitedYes
apartmentsvnView Comments
2015-12-02
2015-12-02View Mitigation

apartments Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

vn Comments

By Le Thi Ngoc Mo, Deputy Director General of Vietnam Telecommunications Authority (VNTA), Ministry of Information and Communication (MIC)

Dear ICANN,
“vn” is the country code for Viet Nam. The release of the two-character ".vn" label at the second-level under new gTLDs would create confusion with the ccTLD ".vn". On behalf of Viet Nam government, I would like to submit an objection to the release of the “.vn” at the second level under all new gTLDs.
Viet Nam is seting up the accurate criteria for releasing this two character at the second level domain names under new gTLDs . This is sensitive issue for government so it is taking some time for government to consider.
To reiterate, our objections are applied to all new gTLDs who have requested or will be requesting for the release of “.vn” at the second level until we set up the accurate criteria for releasing and send notice to ICANN.
Thank you and best regards,

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