Skip to main content
Resources

Two-Character Letter/Letter Label Comments and Mitigation Measures

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

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

Download Excel
TLD  Two
Characters  		Comments from GovernmentLast
updated  		RO Mitigation PlanRO NameBRAND TLD
bostikvnView Comments
2016-08-17
2016-08-17Yes
calvnView Comments
2016-08-17
2016-08-17No
camvnView Comments
2016-08-17
2016-08-17No
cbsvnView Comments
2016-08-17
2016-08-17Yes
channelvnView Comments
2016-08-17
2016-08-17No
chintaivnView Comments
2016-08-17
2016-08-17Yes
dadvnView Comments
2016-08-17
2016-08-17No
dayvnView Comments
2016-08-17
2016-08-17No
dclkvnView Comments
2016-08-17
2016-08-17No
devvnView Comments
2016-08-17
2016-08-17No
doctorvnView Comments
2016-08-17
2016-08-17No
eatvnView Comments
2016-08-17
2016-08-17No
ecovnView Comments
2016-08-17
2016-08-17No
esqvnView Comments
2016-08-17
2016-08-17No
flyvnView Comments
2016-08-17
2016-08-17No
fujixeroxvnView Comments
2016-08-17
2016-08-17Yes
gamesvnView Comments
2016-08-17
2016-08-17No
gbizvnView Comments
2016-08-17
2016-08-17No
gdnvnView Comments
2016-08-17
2016-08-17No
glevnView Comments
2016-08-17
2016-08-17No
gugevnView Comments
2016-08-17
2016-08-17No
hangoutvnView Comments
2016-08-17
2016-08-17No
ikanovnView Comments
2016-08-17
2016-08-17Yes
jcpvnView Comments
2016-08-17
2016-08-17Yes
mapvnView Comments
2016-08-17
2016-08-17No
memevnView Comments
2016-08-17
2016-08-17No
movvnView Comments
2016-08-17
2016-08-17No
newvnView Comments
2016-08-17
2016-08-17No
phdvnView Comments
2016-08-17
2016-08-17No
prodvnView Comments
2016-08-17
2016-08-17No
profvnView Comments
2016-08-17
2016-08-17No
quebecvnView Comments
2016-08-17
2016-08-17No
rsvpvnView Comments
2016-08-17
2016-08-17No
searchvnView Comments
2016-08-17
2016-08-17No
sfrvnView Comments
2016-08-17
2016-08-17Yes
showtimevnView Comments
2016-08-17
2016-08-17Yes
totalvnView Comments
2016-08-17
2016-08-17Yes
watchesvnView Comments
2016-08-17
2016-08-17No
wtcvnView Comments
2016-08-17
2016-08-17Yes
xn--flw351evnView Comments
2016-08-17
2016-08-17Yes
xn--kpu716fvnView Comments
2016-08-17
2016-08-17No
xn--pbt977cvnView Comments
2016-08-17
2016-08-17No
xn--qcka1pmcvnView Comments
2016-08-17
2016-08-17Yes
zipvnView Comments
2016-08-17
2016-08-17No
aarpsuView Comments
2015-12-07
2016-08-15View 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
abbsuView Comments
2015-12-07
2016-08-15View 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
abbottsuView Comments
2015-12-07
2016-08-15View 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
abogadosuView Comments
2015-12-07
2016-08-15View 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
academysuView Comments
2015-12-07
2016-08-15View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
accenturesuView Comments
2015-12-07
2016-08-15View 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
accountantsuView Comments
2015-12-07
2016-08-15View 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
accountantssuView Comments
2015-12-07
2016-08-15View Mitigation

accountants Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
acosuView Comments
2015-12-07
2016-08-15View Mitigation

aco Mitigation

By ACO Severin Ahlmann GmbH & Co. KG

.ACO mitigation measures apply across all two character labels

.ACO TLD is a closed Brand new gTLD operated by ACO Severin Ahlmann GmbH & Co. KG

Protections
ACO Severin Ahlmann GmbH & Co. KG for the .ACO TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that ACO Severin Ahlmann GmbH & Co. KG will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .ACO is identical to a qualifying registered trademark;

2. .ACO is not a Generic String, as this is defined in Specification 11;

3. .ACO TLD has developed and implemented a closed registration policy for .ACO that requires that all domain names in the .ACO TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;

4. As required under the Registry Agreement, the .ACO TLD is clearly publishing this registration policy;

5. .ACO TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

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


2016-04-19

ACO Severin Ahlmann GmbH & Co. KGYes
actorsuView Comments
2015-12-07
2016-08-15View 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
adultsuView Comments
2015-12-07
2016-08-15View 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
aegsuView Comments
2015-12-07
2016-08-15View 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
agencysuView Comments
2015-12-07
2016-08-15View Mitigation

agency Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
aigsuView Comments
2015-12-07
2016-08-15View 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
airforcesuView Comments
2015-12-07
2016-08-15View 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
allfinanzsuView Comments
2015-12-07
2016-08-15View 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
allysuView Comments
2015-12-07
2016-08-15Yes
amsterdamsuView Comments
2015-12-07
2016-08-15View 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
analyticssuView Comments
2015-12-07
2016-08-15View 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
androidsuView Comments
2015-12-07
2016-08-15View Mitigation

android 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)Yes
anzsuView Comments
2015-12-07
2016-08-15View 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
apartmentssuView Comments
2015-12-07
2016-08-15View Mitigation

apartments Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
applesuView Comments
2015-12-07
2016-08-15Yes
aquarellesuView Comments
2015-12-07
2016-08-15Yes
archisuView Comments
2015-12-07
2016-08-15View 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
armysuView Comments
2015-12-07
2016-08-15View 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
artesuView Comments
2015-12-07
2016-08-15View Mitigation

arte Mitigation

By Association Relative à la Télévision Européenne G.E.I.E.

Provide a brief explanation of the TLD:
Association Relative à la Télévision Européenne G.E.I.E. has applied for .ARTE to run a closed .brand environment.

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

Compliance with Specification 13 prohibits the .ARTE TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ARTE TLD is a proprietary space in which all second-level domains in the TLD are being operated by Association Relative à la Télévision Européenne G.E.I.E., its Affiliates and Trademark Licensees and not the government or the corresponding country code operator.
By this letter Association Relative à la Télévision Européenne G.E.I.E. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Association Relative à la Télévision Européenne G.E.I.E.Yes
associatessuView Comments
2015-12-07
2016-08-15View Mitigation

associates Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
attorneysuView Comments
2015-12-07
2016-08-15View 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
auctionsuView Comments
2015-12-07
2016-08-15View 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
audisuView Comments
2015-12-07
2016-08-15View Mitigation

audi Mitigation

By Audi Aktiengesellschaft

.audi is a closed Brand TLD for the sole and exclusive use of Audi Aktiengesellschaft.

Protections
Audi Aktiengesellschaft (Registry Operator) for the .audi TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Registry Operator will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

.audi is identical to a qualifying registered trademark;
.audi is not a Generic String, as this is defined in Specification 11;
Registry Operator has developed and implemented a closed registration policy for .audi that requires that all domain names in the .audi TLD be registered only by Audi Aktiengesellschaft, its Affiliates, and its Trademark Licensees.

As required under the Registry Agreement, the Registry Operator published this registration policy on its website.

Registry Operator will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the Registry Operator from registering domain names to unaffiliated third parties and thus clearly designate to the public that .audi TLD is a proprietary space in which all second-level domains in the TLD are being operated by the Registry Operator, its Affiliates and Trademark Licensees and not the governments or the corresponding country code operators.

By this submission Audi Aktiengesellschaft confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

Audi AktiengesellschaftYes
audiblesuView Comments
2015-12-07
2016-08-15View Mitigation

audible Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .Brand TLDs .AUDIBLE, .AWS, .FIRE, .IMDB, .KINDLE, .PRIME, .SILK, and .ZAPPOS (collectively, “the .Brand TLDs”) proposes release of the following 2-character letter-letter combinations: : ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw.

ARSI has executed Specification 13 to the Registry Agreement for each of the .Brand TLDs. Specification 13 contractually requires ARSI to apply measures which, in and of themselves, avoid confusion with the country codes corresponding to the 2-character letter-letter combinations listed above, namely:

1. Each of the .Brand TLDs is identical to a qualifying registered trademark;
2. Each of the .Brand TLDs is not a Generic String, as this is defined in Specification 11;
3. ARSI has developed and will implement a registration policy for each of the .Brand TLDs that requires all domain names in each such TLD be registered only by ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates;
4. ARSI will publish the registration policy for each of the .Brand TLDs upon delegation; and
5. ARSI has ensured, and will continue to ensure, its compliance with the registration policy through annual certification of qualification for Specification 13 for each of the .Brand TLDs.

Compliance with Specification 13 clearly designates to the public that the .Brand TLDs are proprietary spaces in which ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates use all second-level domain names. Accordingly, there will be no basis on which a letter-letter domain name registered in any of the .Brand TLDs could be confused with the country codes corresponding to the 2-character letter-letter combinations listed above.


2016-04-25

Amazon Registry Services, Inc.Yes
audiosuView Comments
2015-12-07
2016-08-15No
authorsuView Comments
2015-12-07
2016-08-15View Mitigation

author Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .AUTHOR, .BOT, .BUY, .CALL, .CIRCLE, .COUPON, .DEAL, .FAST, .GOT, .HOT, .JOT, .JOY, .LIKE, .MOI, .NOW, .PAY, .PIN, .READ, .ROOM, .SAFE, .SECURE, .SAVE, .SMILE, .SONG, .SPOT, .TALK, .TUNES, .TUSHU, .WANGGOU, and .xn--rovu88b.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes.

ARSI will commit to:
1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and
b. corresponds to that government’s country code; and
c. implies or represents that it is, or has the approval of, such government; and
2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion:
a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or
b. may cause the domain name’s records to be removed from the DNS; and
3. Provide a written response within a commercially reasonable time period.

ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above.


2016-04-25

Amazon Registry Services, Inc. No
autosuView Comments
2015-12-07
2016-08-15No
autossuView Comments
2015-12-07
2016-08-15View Mitigation

autos Mitigation

By DERAutos LLC, DERBoats LLC, DERHomes LLC, DERMotorcycles LLC, DERYachts LLC (collective Dominion Registries)

See attached document


View Documents
2016-04-26

DERAutos LLC, DERBoats LLC, DERHomes LLC, DERMotorcycles LLC, DERYachts LLC (collective Dominion Registries)No
awssuView Comments
2015-12-07
2016-08-15View Mitigation

aws Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .Brand TLDs .AUDIBLE, .AWS, .FIRE, .IMDB, .KINDLE, .PRIME, .SILK, and .ZAPPOS (collectively, “the .Brand TLDs”) proposes release of the following 2-character letter-letter combinations: : ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw.

ARSI has executed Specification 13 to the Registry Agreement for each of the .Brand TLDs. Specification 13 contractually requires ARSI to apply measures which, in and of themselves, avoid confusion with the country codes corresponding to the 2-character letter-letter combinations listed above, namely:

1. Each of the .Brand TLDs is identical to a qualifying registered trademark;
2. Each of the .Brand TLDs is not a Generic String, as this is defined in Specification 11;
3. ARSI has developed and will implement a registration policy for each of the .Brand TLDs that requires all domain names in each such TLD be registered only by ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates;
4. ARSI will publish the registration policy for each of the .Brand TLDs upon delegation; and
5. ARSI has ensured, and will continue to ensure, its compliance with the registration policy through annual certification of qualification for Specification 13 for each of the .Brand TLDs.

Compliance with Specification 13 clearly designates to the public that the .Brand TLDs are proprietary spaces in which ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates use all second-level domain names. Accordingly, there will be no basis on which a letter-letter domain name registered in any of the .Brand TLDs could be confused with the country codes corresponding to the 2-character letter-letter combinations listed above.


2016-04-25

Amazon Registry Services, Inc.Yes
azuresuView Comments
2015-12-07
2016-08-15View Mitigation

azure Mitigation

By Microsoft Corporation

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)

Provide a brief explanation of the TLD:

.AZURE TLD is a closed Brand new gTLD operated by Microsoft Corporation

Protections:

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

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

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


2016-04-05

Microsoft CorporationYes
bandsuView Comments
2015-12-07
2016-08-15View Mitigation

band Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
banksuView Comments
2015-12-07
2016-08-15View 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
barclaycardsuView Comments
2015-12-07
2016-08-15View Mitigation

barclaycard Mitigation

By Barclays Bank PLC

.barclaycard is a closed top-level domain name for the sole and exclusive use of Barclays Bank PLC.

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


2016-04-08

Barclays Bank PLCYes
barclayssuView Comments
2015-12-07
2016-08-15View Mitigation

barclays Mitigation

By Barclays Bank PLC

.barclays is a closed top-level domain name for the sole and exclusive use of Barclays Bank PLC.

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


2016-04-08

Barclays Bank PLCYes
bargainssuView Comments
2015-12-07
2016-08-15View Mitigation

bargains Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
bayernsuView Comments
2015-12-07
2016-08-15View Mitigation

bayern 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
bbcsuView Comments
2015-12-07
2016-08-15View Mitigation

bbc Mitigation

By British Broadcasting Corporation

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)

Provide a brief explanation of the TLD:

.BBC TLD is a closed Brand new gTLD operated by British Broadcasting Corporation

Protections:

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

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

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


2016-04-11

British Broadcasting CorporationYes
bbvasuView Comments
2015-12-07
2016-08-15View Mitigation

bbva Mitigation

By BANCO BILBAO VIZCAYA ARGENTARIA, S.A.

Provide a brief explanation of the TLD:
BANCO BILBAO VIZCAYA ARGENTARIA, S.A. has applied for .BBVA to run a closed .brand environment.


Protections

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

Compliance with Specification 13 prohibits the .BBVA TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .BBVA TLD is a proprietary space in which all second-level domains in the TLD are being operated by BANCO BILBAO VIZCAYA ARGENTARIA, S.A., its Affiliates and Trademark Licensees and not the [GOVERNMENT] or the corresponding country code operator.

By this [LETTER] BANCO BILBAO VIZCAYA ARGENTARIA, S.A. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-15

BANCO BILBAO VIZCAYA ARGENTARIA, S.A.Yes
beatssuView Comments
2015-12-07
2016-08-15Yes
beersuView Comments
2015-12-07
2016-08-15View 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
bentleysuView Comments
2015-12-07
2016-08-15View Mitigation

bentley Mitigation

By Bentley Motors Limited

Proposed measures to avoid confusion relating to all two-character labels

.Bentley
.Bentley TLD is a closed Brand new gTLD operated by Bentley Motors Limited. Within the .Bentley namespace, Internet traffic will be driven to sites that are a reflection of the brand and users will gain the full benefit of the Bentley experience, secure in the knowledge of its authentic, credible and reliable source. .Bentley will be positioned, promoted and deployed as the single, dependable and trustworthy domain for Internet users to access information relating to the brand.

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

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

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

By this notice Bentley Motors Limited confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-22

Bentley Motors LimitedYes
berlinsuView Comments
2015-12-07
2016-08-15View Mitigation

berlin Mitigation

By dotBERLIN GmbH & Co. KG

Proposed Measures to Avoid Confusion within the Community-based GeoTLD .BERLIN for ci, cn, eg, hk, il, in, it, me, pt, sg, tw

“.BERLIN is the top-level domain for the Community of Berliners in the Internet (the .BERLIN Community). The local domain names available with the .BERLIN top-level domain are concise and create an identity for citizens, companies and institutions. Those providing and looking for information, goods and services can thus intuitively come together. The .BERLIN domain names strengthen the feeling of community amongst Berliners, improve communication and make interaction easier, thus providing a stimulus for innovation and development. Both for Berliners and for non-Berliners, Berlin becomes more attractive as a place to visit, as a commercial location and as a place to live.”

Protections

To address the confusion concerns cited by the governments regarding the use of the second-level domains cited above in the .BERLIN, the Registry Operator dotBERLIN GmbH & Co. KG has implemented a restricted registration policy for .BERLIN that mitigates the potential confusion. To these ends, Registry Operator commits to the following (as mentioned in its application at https://gtldresult.icann.org/application-result/applicationstatus/applicationdetails:downloadapplication/1777?t:ac=1777):

dotBERLIN developed and implemented a restricted registration policy and enforces this restricted Registration Policy for .BERLIN including:

Eligibility Requirements: To meet the requirements of ICANN to a community-based designation of the application and to meet a sufficient reference to BERLIN, the group of registrants is limited. Exclusively eligible to register a domain name under the top-level domain .BERLIN is any natural person, legal person, organization or association of persons, if they can demonstrate that they have an economic, cultural, historical, social or any other connection to the German capital Berlin, verifiable by
-their residence or second home, office or place of business, a branch or permanent establishment in the City of BERLIN, or
-a contact listed in the Whois database with a domicile in the City of BERLIN, or
-other appropriate proof e.g. the certification by an employer to enroll at a school or college, or birth certificate.

With the registration of a .BERLIN domain name each registrant implicitly signs the registration policies and agrees with the fact that he acknowledges compliance with the registration guidelines. A review of whether the applicant meets the required eligibility, does not take place regularly on the date of registration, however, anyone can check compliance with the registration requirements by initiating an extrajudicial dispute resolution procedure (ʺ.BERLIN Eligibility Requirements Dispute Resolution Policyʺ) or an objection process.

Content and Use Requirements: To meet the requirements of ICANN to a community-based designation of the application, the registrant must satisfy the following criteria for the content and the use of .BERLIN domain names:
- The contents of the website under a domain name must be directly related to the eligibility requirements, and
- the domain must be in use within 12 months of registration.

Legal Safeguards, Enforcement and continued Compliance: To meet the requirements of ICANN to a community-based designation of the application, the registrant must use the .BERLIN domain in an economic, cultural, social or any other meaningful connection to the City of Berlin.

This designation of .BERLIN to the .BERLIN Community will be enforced by specific language in the Registry-Registrar-Agreement that holds gTLD registrars responsible to include the restrictions as outlined above in respective agreements with their gTLD registrants.

The .BERLIN Registry will, from time to time in its sole discretion or upon evidence or advice manually conduct continuing or recurring audits of domain names registered to ensure continued compliance with these requirements. Failure to comply will result in a notice providing 20-days to comply. Non-compliance following such a notice period may result in take-down of the relevant domain name, at the discretion of the Registry.

Those policies have been clearly publishing policy on Registry Operator’s homepage for .BERLIN.

This registration and usage policy would prevent governments from registering domains in the .BERLIN TLD. It would clearly designate to users that .BERLIN was a restricted space in which all second-level domains were registered by eligible Registrants.


2016-04-25

View Mitigation

berlin Mitigation

By dotBERLIN GmbH & Co. KG


Proposed Measures to Avoid Confusion within the Community-based GeoTLD .BERLIN for su, ru, uk, it, gb, ac, gi, tc, sh, ms, ky, io, bm, fk, ng, kr, il, sg, hk, pn, gs, tw, vn, ln, in, pt

“.BERLIN is the top-level domain for the Community of Berliners in the Internet (the .BERLIN Community). The local domain names available with the .BERLIN top-level domain are concise and create an identity for citizens, companies and institutions. Those providing and looking for information, goods and services can thus intuitively come together. The .BERLIN domain names strengthen the feeling of community amongst Berliners, improve communication and make interaction easier, thus providing a stimulus for innovation and development. Both for Berliners and for non-Berliners, Berlin becomes more attractive as a place to visit, as a commercial location and as a place to live.”

Protections

To address the confusion concerns cited by the governments regarding the use of the second-level domains cited above in the .BERLIN, the Registry Operator dotBERLIN GmbH & Co. KG has implemented a restricted registration policy for .BERLIN that mitigates the potential confusion. To these ends, Registry Operator commits to the following (as mentioned in its application at https://gtldresult.icann.org/application-result/applicationstatus/applicationdetails:downloadapplication/1777?t:ac=1777):

dotBERLIN developed and implemented a restricted registration policy and enforces this restricted Registration Policy for .BERLIN including:

Eligibility Requirements: To meet the requirements of ICANN to a community-based designation of the application and to meet a sufficient reference to BERLIN, the group of registrants is limited. Exclusively eligible to register a domain name under the top-level domain .BERLIN is any natural person, legal person, organization or association of persons, if they can demonstrate that they have an economic, cultural, historical, social or any other connection to the German capital Berlin, verifiable by
-their residence or second home, office or place of business, a branch or permanent establishment in the City of BERLIN, or
-a contact listed in the Whois database with a domicile in the City of BERLIN, or
-other appropriate proof e.g. the certification by an employer to enroll at a school or college, or birth certificate.

With the registration of a .BERLIN domain name each registrant implicitly signs the registration policies and agrees with the fact that he acknowledges compliance with the registration guidelines. A review of whether the applicant meets the required eligibility, does not take place regularly on the date of registration, however, anyone can check compliance with the registration requirements by initiating an extrajudicial dispute resolution procedure (ʺ.BERLIN Eligibility Requirements Dispute Resolution Policyʺ) or an objection process.

Content and Use Requirements: To meet the requirements of ICANN to a community-based designation of the application, the registrant must satisfy the following criteria for the content and the use of .BERLIN domain names:
- The contents of the website under a domain name must be directly related to the eligibility requirements, and
- the domain must be in use within 12 months of registration.

Legal Safeguards, Enforcement and continued Compliance: To meet the requirements of ICANN to a community-based designation of the application, the registrant must use the .BERLIN domain in an economic, cultural, social or any other meaningful connection to the City of Berlin.

This designation of .BERLIN to the .BERLIN Community will be enforced by specific language in the Registry-Registrar-Agreement that holds gTLD registrars responsible to include the restrictions as outlined above in respective agreements with their gTLD registrants.

The .BERLIN Registry will, from time to time in its sole discretion or upon evidence or advice manually conduct continuing or recurring audits of domain names registered to ensure continued compliance with these requirements. Failure to comply will result in a notice providing 20-days to comply. Non-compliance following such a notice period may result in take-down of the relevant domain name, at the discretion of the Registry.

Those policies have been clearly publishing policy on Registry Operator’s homepage for .BERLIN.

This registration and usage policy would prevent governments from registering domains in the .BERLIN TLD. It would clearly designate to users that .BERLIN was a restricted space in which all second-level domains were registered by eligible Registrants.


2016-04-25

dotBERLIN GmbH & Co. KGNo
bestsuView Comments
2015-12-07
2016-08-15No
betsuView Comments
2015-12-07
2016-08-15View 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
bhartisuView Comments
2015-12-07
2016-08-15Yes
biblesuView Comments
2015-12-07
2016-08-15View Mitigation

bible Mitigation

By American Bible Society

.BIBLE Proposed Measure to Avoid Confusion—Registry Operator with Open Registration

The .BIBLE TLD is owned and operated by the American Bible Society (Registry Operator). .BIBLE is a Top Level Domain with a vision to be the trusted online source for all things Bible. The .BIBLE TLD will make available .BIBLE domain names that are memorable, meaningful, and shorter to help people, organizations and communities come together online to engage with Scripture and share Bible-related content.
The mission of .BIBLE is to encourage Bible engagement, translation, innovation, and global partnerships so that all people may experience the life-changing message of the Bible

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 governments of Côte d'Ivoire, China, Egypt, Israel, India, Italy, Montenegro, Portugal and Singapore 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, contained within our Acceptable Use Policy for the .BIBLE TLD is the following text:

5.1.1.14 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 Acceptable Use Policy, the domain name 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.


View Documents
2016-04-15

American Bible SocietyNo
bidsuView Comments
2015-12-07
2016-08-15View 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
bikesuView Comments
2015-12-07
2016-08-15View Mitigation

bike Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No

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.

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 country codes ccTLDs creates the risk of confusion and misleading of Internet users.
This requirement should apply to all current and future requests.

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