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
allytwView Comments
2015-10-14
2015-12-02Yes
amsterdamtwView Comments
2015-10-14
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
analyticstwView Comments
2015-10-14
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
anztwView Comments
2015-10-14
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
appletwView Comments
2015-10-14
2015-12-02Yes
architwView Comments
2015-10-14
2015-12-02View 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
armytwView Comments
2015-10-14
2015-12-02View 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
artetwView Comments
2015-10-14
2015-12-02View 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
audibletwView Comments
2015-10-14
2015-12-02View 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
autotwView Comments
2015-10-14
2015-12-02No
awstwView Comments
2015-10-14
2015-12-02View 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
banktwView Comments
2015-10-14
2015-12-02View 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
bayerntwView Comments
2015-10-14
2015-12-02View 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
beatstwView Comments
2015-10-14
2015-12-02Yes
berlintwView Comments
2015-10-14
2015-12-02View 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
bettwView Comments
2015-10-14
2015-12-02View 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
bingotwView Comments
2015-10-14
2015-12-02View Mitigation

bingo Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
biotwView Comments
2015-10-14
2015-12-02View 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
boehringertwView Comments
2015-10-14
2015-12-02View Mitigation

boehringer Mitigation

By Boehringer Ingelheim International GmbH

Provide a brief explanation of the TLD:
Boehringer Ingelheim International GmbH has applied for .BOEHRINGER to run a closed .brand environment.
Protections

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

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


2016-04-25

Boehringer Ingelheim International GmbHYes
booktwView Comments
2015-10-14
2015-12-02View Mitigation

book Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .BOOK TLD, proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, es, 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, es, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code:
a. the use in the .BOOK TLD 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 .BOOK TLD will require registrants of a domain name in the .BOOK TLD 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
bootstwView Comments
2015-10-14
2015-12-02View Mitigation

boots Mitigation

By THE BOOTS COMPANY PLC

.boots is a closed top-level domain name for the sole and exclusive use of THE BOOTS COMPANY PLC.

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


2016-04-25

THE BOOTS COMPANY PLCYes
bridgestonetwView Comments
2015-10-14
2015-12-02View Mitigation

bridgestone Mitigation

By Bridgestone Corporation

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

Provide a brief explanation of the TLD:

.bridgestone is a closed Brand new gTLD operated by Bridgestone Corporation

Protections:

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

1. .bridgestone is identical to a qualifying registered trademark;

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

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

4. As required under the Registry Agreement, the .bridgestone TLD will clearly publish this registration policy;

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

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


2016-04-25

Bridgestone CorporationYes
brokertwView Comments
2015-10-14
2015-12-02View 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
budapesttwView Comments
2015-10-14
2015-12-02View Mitigation

budapest 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
bzhtwView Comments
2015-10-14
2015-12-02No
cafetwView Comments
2015-10-14
2015-12-02View Mitigation

cafe Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cartwView Comments
2015-10-14
2015-12-02No
carstwView Comments
2015-10-14
2015-12-02No
casinotwView Comments
2015-10-14
2015-12-02View Mitigation

casino Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cbatwView Comments
2015-10-14
2015-12-02View Mitigation

cba Mitigation

By Commonwealth Bank of Australia

Refer measures in attached PDF document


View Documents
2016-04-13

Commonwealth Bank of AustraliaYes
cerntwView Comments
2015-10-14
2015-12-02View Mitigation

cern Mitigation

By European Organization for Nuclear Research ("CERN")

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

Provide a brief explanation of the TLD:

.cern is a closed top-level domain name for the sole and exclusive use of THE EUROPEAN ORGANIZATION FOR NUCLEAR RESEARCH (“CERN”).

Protections

THE EUROPEAN ORGANIZATION FOR NUCLEAR RESEARCH (“CERN”) is the Registry Operator for the .cern TLD and has executed Specification 13 of the Registry Agreement. Specification 13 already contractually requires that CERN will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

1. .cern is identical to a qualifying registered trademark;

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

3. .cern TLD has developed and will implement a closed registration policy for .cern that requires that all domain names in the .cern TLD be registered ONLY by Registry Operator and its Affiliates;

4. As required under the Registry Agreement, the .cern TLD will clearly publish this registration policy;

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

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

By this text CERN confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

European Organization for Nuclear Research ("CERN")Yes
cfdtwView Comments
2015-10-14
2015-12-02View Mitigation

cfd 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
chaneltwView Comments
2015-10-14
2015-12-02View Mitigation

chanel Mitigation

By Chanel International B.V.

CHANEL INTERNATIONAL B.V., the Registry Operator for the .CHANEL TLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that CHANEL INTERNATIONAL B.V. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .CHANEL is identical to a qualifying registered trademark;
2. .CHANEL is not a Generic String, as this is defined in Specification 11 of the Registry Agreement;
3. CHANEL INTERNATIONAL B.V. has developed and will implement a closed registration policy for .CHANEL that requires that all domain names in the .CHANEL TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, CHANEL INTERNATIONAL B.V. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and
5. CHANEL INTERNATIONAL B.V. 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 .CHANEL TLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .CHANEL TLD is a proprietary space in which all second-level domains in the TLD are being operated by CHANEL INTERNATIONAL B.V., its Affiliates and Trademark Licensees and not the Government or the corresponding country-code operator.
By this letter, CHANEL INTERNATIONAL B.V. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13.


2016-04-22

Chanel International B.V.Yes
circletwView Comments
2015-10-14
2015-12-02View Mitigation

circle 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
citytwView Comments
2015-10-14
2015-12-02View Mitigation

city Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cliniquetwView Comments
2015-10-14
2015-12-02View Mitigation

clinique Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.Yes
cloudtwView Comments
2015-10-14
2015-12-02View 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
clubmedtwView Comments
2015-10-14
2015-12-02View Mitigation

clubmed Mitigation

By Club Méditerranée S.A.

Provide a brief explanation of the TLD:
Club Méditerranée S.A. has applied for .CLUBMED to run a closed .brand environment.

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

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


2016-04-25

Club Méditerranée S.A.Yes
collegetwView Comments
2015-10-14
2015-12-02No
commbanktwView Comments
2015-10-14
2015-12-02View Mitigation

commbank Mitigation

By Commonwealth Bank of Australia

Refer measures in attached PDF document


View Documents
2016-04-13

Commonwealth Bank of AustraliaYes
countrytwView Comments
2015-10-14
2015-12-02View Mitigation

country 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
couponstwView Comments
2015-10-14
2015-12-02View Mitigation

coupons Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cuisinellatwView Comments
2015-10-14
2015-12-02View Mitigation

cuisinella Mitigation

By SALM S.A.S.

.cuisinella is a closed top-level domain name for the sole and exclusive use of Salm S.A.S.

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


2016-04-25

SALM S.A.S.Yes
dealtwView Comments
2015-10-14
2015-12-02View Mitigation

deal 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
deloittetwView Comments
2015-10-14
2015-12-02View Mitigation

deloitte Mitigation

By Deloitte Touche Tohmatsu

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

Provide a brief explanation of the TLD: The .deloitte TLD is a .brand TLD as defined in Schedule 13 to ICANN’s registry agreement. It is used by Deloitte Touche Tohmatsu Limited (“DTTL”), the member firms of DTTL, and their related entities to register various domain names related to their business operations. “Deloitte” is the brand under which tens of thousands of dedicated professionals in these entities throughout the world collaborate to provide audit, consulting, financial advisory, risk management, tax and related services to select clients. The .deloitte TLD supports these business, providing for brand enhancement and protection by creating a single ecosystem where Deloitte stakeholders know that they are an “official” Deloitte website.

Protections:

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

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

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

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


View Documents
2016-04-18

Deloitte Touche TohmatsuYes
deltatwView Comments
2015-10-14
2015-12-02View Mitigation

delta Mitigation

By Delta Air Lines, Inc.

The .DELTA TLD is a closed, single-registrant TLD as defined by Specification 13 of the Registry Agreement (“RA”). Domain registrations, renewals and maintenance will be available only to authorized users and members of Delta Air Lines, Inc. and its subsidiaries. The .DELTA TLD sets to optimize customer service, communicate corporate and consumer information and promote security as follows:

• A consistently structured and authenticated system of Internet and Intranet communication.
• An authenticated brand that enhances consumer confidence in communication from and to .DELTA.

Eligibility
All second-level domains and subsequent sub-domains will be generated solely for the communication structure and strategy of Delta Air Lines, Inc. and its subsidiaries. Accordingly, .DELTA registrations will not be freely available to the market.
Registry Operator will comply with all requirements of Specification 5 of the Registry Agreement.

Rights Protection
Registry Operator will adhere to rights protection mechanisms mandated by ICANN, including all mechanisms included in Specification 7 of the Registry Agreement.

Acceptable Use
Registry Operator will take all reasonable steps to protect personal data from loss, misuse, unauthorized disclosure, alteration or destruction. Registry Operator will also comply, in accordance with the Registry Agreement, with all existing and future consensus policies as formally adopted by ICANN. Registry Operator will only use ICANN-accredited registrars established under the 2013 Registrar Accreditation Agreement. As a single-registrant TLD eligible for Specification 13, Registry Operator will implement all policies and procedures established within the Registry Agreement.


2016-04-25

Delta Air Lines, Inc.Yes
desitwView Comments
2015-10-14
2015-12-02No
docstwView Comments
2015-10-14
2015-12-02View 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
dogtwView Comments
2015-10-14
2015-12-02View Mitigation

dog Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
dunloptwView Comments
2015-10-14
2015-12-02View Mitigation

dunlop Mitigation

By The Goodyear Tire & Rubber Company

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


2016-04-21

The Goodyear Tire & Rubber CompanyYes
expresstwView Comments
2015-10-14
2015-12-02View Mitigation

express Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
familytwView Comments
2015-10-14
2015-12-02View Mitigation

family Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
fanstwView Comments
2015-10-14
2015-12-02No
filmtwView Comments
2015-10-14
2015-12-02View Mitigation

film Mitigation

By Motion Picture Domain Registry

.film Mitigation

Proposed Measure to Avoid Confusion
.film is a generic TLD for the film industry. While .film is an open TLD, registration of domain names is limited to members of the film community as described in the Registration Policy.

The proposed protections to avoid confusion with country codes at the second level outlined below specifically apply to: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw

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, contained within our Acceptable Use Policy for the .film TLD is the following text:
“…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 Acceptable Use Policy, the domain name may be cancelled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLDs, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-14

Motion Picture Domain RegistryNo
firetwView Comments
2015-10-14
2015-12-02View Mitigation

fire 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
firestonetwView Comments
2015-10-14
2015-12-02View Mitigation

firestone Mitigation

By Bridgestone Corporation

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

Provide a brief explanation of the TLD:

.firestone is a closed Brand new gTLD operated by Bridgestone Corporation

Protections:

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

1. .firestone is identical to a qualifying registered trademark;

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

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

4. As required under the Registry Agreement, the .firestone TLD will clearly publish this registration policy;

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

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


2016-04-25

Bridgestone CorporationYes
forextwView Comments
2015-10-14
2015-12-02View Mitigation

forex 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
fyitwView Comments
2015-10-14
2015-12-02View Mitigation

fyi Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
galluptwView Comments
2015-10-14
2015-12-02View Mitigation

gallup Mitigation

By Gallup, Inc.

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: [Registry Operator] has applied for .[TLD] to run a closed .brand environment.
Protections
[REGISTRY OPERATOR] for the .[TLD] 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:
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 [REGISTRY OPERATOR], its Affiliates and Trademark Licensees and not the [GOVERNMENT] or the corresponding country code operator.
By this [LETTER] [REGISTRY OPERATOR] confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-18

Gallup, Inc.Yes
gentingtwView Comments
2015-10-14
2015-12-02Yes
goldtwView Comments
2015-10-14
2015-12-02View Mitigation

gold Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
golftwView Comments
2015-10-14
2015-12-02View Mitigation

golf Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
goodyeartwView Comments
2015-10-14
2015-12-02View Mitigation

goodyear Mitigation

By The Goodyear Tire & Rubber Company

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


2016-04-21

The Goodyear Tire & Rubber CompanyYes
hamburgtwView Comments
2015-10-14
2015-12-02View Mitigation

hamburg Mitigation

By Hamburg Top-Level-Domain GmbH

Proposed Measures to Avoid Confusion within the Community-based GeoTLD .HAMBURG 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

“.HAMBURG is the top-level domain of the Community of Hamburg in the Internet. The local domain names available with the .HAMBURG 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 .HAMBURG domain names strengthen the feeling of community amongst Hamburgers, improve communication and make interaction easier, thus providing a stimulus for innovation and development. Both for Hamburgers and for non-Hamburgers, Hamburg 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 .HAMBURG, the Registry Operator Hamburg Top-Level-Domain GmbH has implemented a restricted registration policy for .HAMBURG 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/1351?t:ac=1351):

Registry Operator developed and implemented a restricted registration policy and enforces this restricted Registration Policy for .HAMBURG including:

Eligibility Requirements: .HAMBURG is intended to serve the community of the Hamburgers in general, the group of eligible registrants is limited. Exclusively eligible to register a domain name under the top-level domain .HAMBURG 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 metropolitan area of Hamburg, verifiable by

- their residence or second home, office or place of business, a branch or permanent establishment in the metropolitan area of Hamburg, or
- a contact listed in the Whois database with a domicile in the metropolitan area of Hamburg, 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 .HAMBURG 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.

Content and Use Requirements: The contents of websites under .HAMBURG must be accessible under a domain directly related to the registration criteria of .HAMBURG.

The Registry has in its discretion developed restrictions on the content and use of any domain name. Such restrictions apply to any domain name registration that occurs after such restrictions come into effect.

Each domain name must, within one year following the date of registration, and thereafter throughout the term of the domain name, be used as the domain name for a website displaying Hamburg Community related content relevant to the domain name, or in such other manner (such as email) that the Registry may approve after review. Domain names used as contemplated above may resolve directly to the relevant website or be forwarded or redirected to another domain name displaying content relevant to the domain name.

Legal Safeguards, Enforcement and continued Compliance: This designation of .HAMBURG to the .HAMBURG 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 Registry Operator will, from time to time in its sole discretion or upon evidence or advice, but at least once a year, 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 a timeframe 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. The Registry is entitled to lock, cancel, initiate the gTLD-deletion cycle or transfer domain names that do not meet the registration criteria if certain circumstances appear.

Those policies have been clearly published on Registry Operator’s homepage for .HAMBURG.

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


2016-04-25

Hamburg Top-Level-Domain GmbHNo
hermestwView Comments
2015-10-14
2015-12-02View Mitigation

hermes Mitigation

By HERMES INTERNATIONAL

.hermes is a closed top-level domain name for the sole and exclusive use of HERMES INTERNATIONAL.

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


2016-04-11

HERMES INTERNATIONALYes
hockeytwView Comments
2015-10-14
2015-12-02View Mitigation

hockey Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
hottwView Comments
2015-10-14
2015-12-02View Mitigation

hot 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
hyundaitwView Comments
2015-10-14
2015-12-02View Mitigation

hyundai Mitigation

By Hyundai Motor Company

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

Provide a brief explanation of the TLD: .hyundai is a closed Brand new gTLD operated by Hyundai Motor Company

Protections:

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

1. .hyundai is identical to a qualifying registered trademark;

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

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

4. As required under the Registry Agreement, the .hyundai TLD will clearly publish this registration policy;

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

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


2016-04-25

Hyundai Motor Company Yes
imdbtwView Comments
2015-10-14
2015-12-02View Mitigation

imdb 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
itvtwView Comments
2015-10-14
2015-12-02View Mitigation

itv Mitigation

By ITV Services Limited

.ITV TLD is a closed Brand new gTLD operated by ITV Services Limited

Protections:

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

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

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


2016-04-12

ITV Services LimitedYes
javatwView Comments
2015-10-14
2015-12-02Yes
jewelrytwView Comments
2015-10-14
2015-12-02View Mitigation

jewelry Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
jlltwView Comments
2015-10-14
2015-12-02Yes
jmptwView Comments
2015-10-14
2015-12-02View Mitigation

jmp 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. DayYes
kerryhotelstwView Comments
2015-10-14
2015-12-02No
kerrylogisticstwView Comments
2015-10-14
2015-12-02No
kerrypropertiestwView Comments
2015-10-14
2015-12-02No
kfhtwView Comments
2015-10-14
2015-12-02No
kiatwView Comments
2015-10-14
2015-12-02View Mitigation

kia Mitigation

By KIA MOTORS CORPORATION

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

Provide a brief explanation of the TLD:

.kia is a closed Brand new gTLD operated by KIA MOTORS CORPORATION

Protections:

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

1. .kia is identical to a qualifying registered trademark;

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

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

4. As required under the Registry Agreement, the .kia TLD will clearly publish this registration policy;

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

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


2016-04-25

KIA MOTORS CORPORATION Yes
kindletwView Comments
2015-10-14
2015-12-02View Mitigation

kindle 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
kpmgtwView Comments
2015-10-14
2015-12-02View Mitigation

kpmg Mitigation

By KPMG International Cooperative

.KPMG TLD is a closed Brand new gTLD operated by KPMG International Cooperative

Protections:

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

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

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


2016-04-04

KPMG International CooperativeYes
krdtwView Comments
2015-10-14
2015-12-02No
kuokgrouptwView Comments
2015-10-14
2015-12-02No
lamertwView Comments
2015-10-14
2015-12-02Yes
lasalletwView Comments
2015-10-14
2015-12-02No
lawtwView Comments
2015-10-14
2015-12-02View Mitigation

law 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
lindetwView Comments
2015-10-14
2015-12-02View Mitigation

linde Mitigation

By Linde Aktiengesellschaft

Provide a brief explanation of the TLD:
Linde Aktiengesellschaft has applied for .LINDE to run a closed .brand environment.

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

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


2016-04-25

Linde AktiengesellschaftYes
livetwView Comments
2015-10-14
2015-12-02View Mitigation

live Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
londontwView Comments
2015-10-14
2015-12-02No
lottetwView Comments
2015-10-14
2015-12-02View Mitigation

lotte Mitigation

By Lotte Holdings Co., Ltd.

.lotte 2 Letter Codes Mitigation Plan

To address the confusion concerns cited by governments regarding the use of the second-level domains in the .lotte TLD, Lotte Holdings Co., Ltd. will implement a closed registration policy for .lotte that mitigates the potential confusion. To these ends, Lotte Holdings Co., Ltd. commits to the following:

・Developing and implementing a closed registration policy for .lotte that requires that all domains name in the TLD be registered and used by Lotte Holding Co., Ltd., its affiliates, or its trademark licensees;

・Clearly publishing this registration policy on Registry Operator`s homepage for the .lotte TLD at “nic.lotte”.

・Referring to this registration policy in registry Operator`s Registry-Registrar Agreement with all appointed preferred registrars for the .lotte TLD.

・Enforcing of this registration policy and ensuring continued compliance, including through annual recertification of .lotte`s qualification for Specification 13; and

・Using all domain names in the .lotte TLD in association with Lotte`s brand products, and services.

This publicly available registration and usage policy would prevent Governments from registering domains in the .lotte TLD. It would therefore clearly designate to the public that .lotte was a proprietary space in which all second-level domains in the TLD were being operated by Lotte Holdings Co., Ltd. and not governments.


2016-04-25

Lotte Holdings Co., Ltd.Yes
mantwView Comments
2015-10-14
2015-12-02View Mitigation

man Mitigation

By MAN SE

.man is a closed Brand TLD for the sole and exclusive use of MAN SE.

Protections
MAN SE (Registry Operator) for the .man 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:

.man is identical to a qualifying registered trademark;
.man is not a Generic String, as this is defined in Specification 11;
Registry Operator has developed and implemented a closed registration policy for .man that requires that all domain names in the .man TLD be registered only by MAN SE, 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 .man 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 text MAN SE confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

MAN SEYes
marketstwView Comments
2015-10-14
2015-12-02View Mitigation

markets 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
mbatwView Comments
2015-10-14
2015-12-02View Mitigation

mba Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
melbournetwView Comments
2015-10-14
2015-12-02View Mitigation

melbourne Mitigation

By The Crown in right of the State of Victoria, represented by its Department of State Development, Business and Innovation

Proposed Measure to Avoid Confusion

A brief explanation of the TLD:

.melbourne is a geographic TLD for the city of Melbourne, Australia and the the State Government of Victoria is the designated ‘Registry Operator’. While .melbourne is an open TLD, registration of domain names is limited to Victorian residents and businesses, and other entities with an interest in the state of Victoria, Australia as described in the Registration Policy.

The proposed protections to avoid confusion with country codes at the second level outlined below specifically apply to: ai, bh, bm, ci, cn, eg, hk, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw

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, contained within our Acceptable Use Policy for the .melbourne TLD is the following text:
“…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 Acceptable Use Policy, the domain name may be cancelled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLDs, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-03-31

 The Crown in right of the State of Victoria, represented by its Department of State Development, Business and InnovationNo
miamitwView Comments
2015-10-14
2015-12-02View Mitigation

miami 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
monstertwView Comments
2015-10-14
2015-12-02No
movietwView Comments
2015-10-14
2015-12-02View Mitigation

movie Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
nagoyatwView Comments
2015-10-14
2015-12-02View Mitigation

nagoya Mitigation

By GMO Registry

About .NAGOYA

.nagoya is a GeoTLD for the city of Nagoya, Japan, operated by GMO Registry, Inc.
The purpose of .nagoya is to promote Nagoya and provide an opportunity for citizens,
businesses and community groups to link their identities to the city’s brand. By bringing together quality and informative content, .NAGOYA provides a platform to effectively deliver city information to Internet users both locally and globally. It is also an important goal for the Registry that .NAGOYA is operated as a trusted, safe, secure, relevant and enjoyable namespace.

Protections
Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern 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 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, contained within our Domain Name Registration Policy for the .NAGOYA TLD is the following text:

All Applicants, all Domain Name Registrants, and any party submitting a Domain Name registration request represents and warrants that:
− to its knowledge, the registration of the Domain Name mentioned in the Application
or Domain Name Registration Request will not infringe upon or otherwise violate the
rights of any third party;
− will not register a domain name for the purpose of distributing malware, abusively
operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent
or deceptive practices, counterfeiting or otherwise engaging in activity contrary to
applicable laws or regulations;

Should a Registrant fail to comply with the Acceptable Use Policy, the domain name may be canceled, 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

GMO RegistryNo
navytwView Comments
2015-10-14
2015-12-02View 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
netbanktwView Comments
2015-10-14
2015-12-02View Mitigation

netbank Mitigation

By Commonwealth Bank of Australia

Refer measures in attached PDF document


View Documents
2016-04-13

Commonwealth Bank of AustraliaYes

tw Comments

By Lin, Mao-Shong, Deputy Director, Ministry of Transportation and Communications

I’m writing hereby to submit Taiwan government’s comments on the release of the “tw” label under the New gTLDs.

We object to the release of “tw” as SLD under all the above-mentioned New gTLDs for their registration by the corresponding Registry operators. We reserve the right to change position in this regard in the future.

The rationale of our objections are below:
Since “tw” label is the country code for Taiwan, the use of “tw” as SLD under these diverse New gTLDs would create confusion or concerns at multiple levels on our part, which include, but not limited to, ”dwarfing national dignity”, “violation of public order or good social custom”, “affecting the rights of domestic enterprises”, and “being prone to produce perplexity to our disadvantage”.

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