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
berlinptView Comments
2015-11-30
2015-11-30View 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
bestptView Comments
2015-11-30
2015-11-30No
betptView Comments
2015-11-30
2015-11-30View 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
bhartiptView Comments
2015-11-30
2015-11-30Yes
bibleptView Comments
2015-11-30
2015-11-30View Mitigation

bible Mitigation

By American Bible Society

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

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

Protections

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

1. Registry Operator will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the governments of Côte d'Ivoire, China, Egypt, Israel, India, Italy, Montenegro, Portugal and Singapore and provide a written report in response; and

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

Furthermore, contained within our Acceptable Use Policy for the .BIBLE TLD is the following text:

5.1.1.14 Use of the domain name, where that domain name is a two letter Label that corresponds to a country code described in the ISO 3166-1 alpha-2 standard, avoids confusion with the corresponding country code.

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


View Documents
2016-04-15

American Bible SocietyNo
bidptView Comments
2015-11-30
2015-11-30View Mitigation

bid Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

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

1. Registry Operator will commit to:

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

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

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

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


2016-04-25

Famous Four Media LimitedNo
bikeptView Comments
2015-11-30
2015-11-30View Mitigation

bike Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
bingptView Comments
2015-11-30
2015-11-30View Mitigation

bing Mitigation

By Microsoft Corporation

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

Provide a brief explanation of the TLD:

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

Protections:

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

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

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


2016-04-05

Microsoft CorporationYes
bingoptView Comments
2015-11-30
2015-11-30View Mitigation

bingo Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
bioptView Comments
2015-11-30
2015-11-30View 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
blackfridayptView Comments
2015-11-30
2015-11-30No
bloombergptView Comments
2015-11-30
2015-11-30View Mitigation

bloomberg Mitigation

By Bloomberg IP Holdings LLC

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


2016-04-19

Bloomberg IP Holdings LLCYes
bmwptView Comments
2015-11-30
2015-11-30View Mitigation

bmw Mitigation

By Bayerische Motoren Werke Aktiengesellschaft

Please find Bayerische Motoren Werke Aktiengesellschaft's "Mitigation Measures to Avoid Confusion" (concerning 2-letter labels in general) for the “.MINI” and the ."BMW" TLDs attached.


View Documents
2016-04-23

Bayerische Motoren Werke AktiengesellschaftYes
bnpparibasptView Comments
2015-11-30
2015-11-30View Mitigation

bnpparibas Mitigation

By BNP PARIBAS

Brief explanation of the TLD: The TLD .BNPPARIBAS belongs to BNPPARIBAS a financial institution of high repute, known worldwide and is a closed TLD restricted to BNPPARIBAS its Affiliates and Trademark Licensees. The BNPPARIBAS gTLD is intended for the exclusive use of BNPPARIBAS products, services and branding purposes.

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

By this proposed plan BNPPARIBAS confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.

It can be added that all domain name registration requests under the TLD BNPPARIBAS are centralized within BNPPARIBAS to ensure that all deposits comply with Specification 13 when they are processed.

As regards risks of potential malicious use of the gtld BNPPARIBAS, it is a problem widely taken into account by BNPPARIBAS. Indeed BNPPARIBAS has a CSIRT (Corporate Security Incident Response Team) member of the FIRST (Forum of Incidental Response and Security Teams) and of the Task Force-CSIRT. This task force promotes collaboration and coordination between CSIRTs in Europe and neighboring regions, whilst liaising with relevant organisations at the global level and in other regions. The gTLD BNPPARIBAS is part of the CSIRT processes.

Thus BNPPARIBAS processes in place and the use of the gTLD BNPPARIBAS avoid confusion with the ISO code representing the designated country.


View Documents
2016-04-21

BNP PARIBASYes
boatsptView Comments
2015-11-30
2015-11-30View Mitigation

boats Mitigation

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

See attached document


View Documents
2016-04-26

DERAutos LLC, DERBoats LLC, DERHomes LLC, DERMotorcycles LLC, DERYachts LLC (collective Dominion Registries)No
boehringerptView Comments
2015-11-30
2015-11-30View 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
bomptView Comments
2015-11-30
2015-11-30View Mitigation

bom Mitigation

By Núcleo de Informação e Coordenação do Ponto BR - NIC.br

Here follows the measures to avoid confusion submitted by NIC.br for its gTLDs .bom and .final are attached. We note the incorrect usage of the word "mitigation" in ICANN 2-char website since it's not what is prescribed in the registry agreement.

.bom and .final are Portuguese words and the target market for such domains is mostly Brazil, the largest Portuguese speaking country in the world, although not restricted to Brazilians.

We divided our comment into 3 sets of 2-letter combinations.

Set 1: ci, cn, eg, il, sg
=========================
Although we do not perceive any of these combinations as confusing, we won't file measures for these combinations at this time. We reserve the right to refile for these combinations in the future, as they might be referenced in the yet to be published registration policies.


Set 2: in, it, me
=================
Although not a native language, most Internet users in Brazil have at least a rudimentary understanding of the English language. The 3 2-letter combinations in this set are incredibly common words of the English language that are known even by less skilled Internet users. Also of notice is that the word "it" is also known as the acronym "IT" for Information Technology; IT specialists have a higher understanding of English than the average Internet user and commonly see "IT" as referencing their area of expertise. Considering this, we understand that no further measures to avoid confusion with these combination are required.

Set 3: pt
=========
pt is not only the country designation for Portugal, it's also the language designation in ISO 639-1 code for the Portuguese language. A myriad of websites use the form pt.example.com or example.com/pt for their Portuguese versions, which makes pt most known for Internet users as a language designator rather than a country designator. We note that this reasoning has already been accepted in RSEP2014007 for all ISO 639-1 and 639-2 codes, and is even more applicable to this context considering it being the native language of the target registrants and the likely target users of such domains.

"PT" is also widely recognized in Brazil for the acronym of the Workers's Party ("Partido dos Trabalhadores"), the ruling party in Brazil since 2002.

"PT" is also known in the Brazil, and possibly other Portuguese speaking countries, as an abbreviation for "Ponto" (dot). In telegrams or telex messages of the previous century, it was used to replace "Ponto" due to having less letters at a time each character was costly to transmit.

"PT" is also commonly used as acronym of "Perda Total", which is a total loss of an insured property (usually a car). This become a slang used not only in the insurance business but to mean that anything was beyond repair, or even to mean that a person was totally drunk.

Considering the many uses of the 2-char combination 'pt', it would be surprising for someone to understand it as a reference to Portugal or .pt domains, and we understand that no further measures to avoid confusion with this 2-char combination are required.




2016-04-22

Núcleo de Informação e Coordenação do Ponto BR - NIC.brNo
bookptView Comments
2015-11-30
2015-11-30View 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
bootsptView Comments
2015-11-30
2015-11-30View 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
boutiqueptView Comments
2015-11-30
2015-11-30View Mitigation

boutique Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
bridgestoneptView Comments
2015-11-30
2015-11-30View 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
brokerptView Comments
2015-11-30
2015-11-30View 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
budapestptView Comments
2015-11-30
2015-11-30View 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
bugattiptView Comments
2015-11-30
2015-11-30View Mitigation

bugatti Mitigation

By Bugatti International SA

.bugatti is a closed Brand TLD for the sole and exclusive use of Bugatti International SA.

Protections
Bugatti International SA (Registry Operator) for the .bugatti 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:

.bugatti is identical to a qualifying registered trademark;
.bugatti is not a Generic String, as this is defined in Specification 11;
Registry Operator has developed and implemented a closed registration policy for .bugatti that requires that all domain names in the .bugatti TLD be registered only by Bugatti International SA, 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 .bugatti TLD is a proprietary space in which all second-level domains in the TLD are being operated by the Registry Operator, its Affiliates and Trademark Licensees and not the governments or the corresponding country code operators.

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


2016-04-21

Bugatti International SAYes
buildptView Comments
2015-11-30
2015-11-30No
buildersptView Comments
2015-11-30
2015-11-30View Mitigation

builders Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
businessptView Comments
2015-11-30
2015-11-30View Mitigation

business Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
buzzptView Comments
2015-11-30
2015-11-30No
bzhptView Comments
2015-11-30
2015-11-30No
cabptView Comments
2015-11-30
2015-11-30View Mitigation

cab Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cafeptView Comments
2015-11-30
2015-11-30View Mitigation

cafe Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cameraptView Comments
2015-11-30
2015-11-30View Mitigation

camera Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
campptView Comments
2015-11-30
2015-11-30View Mitigation

camp Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
capitalptView Comments
2015-11-30
2015-11-30View Mitigation

capital Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
carptView Comments
2015-11-30
2015-11-30No
cardsptView Comments
2015-11-30
2015-11-30View Mitigation

cards Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
careptView Comments
2015-11-30
2015-11-30View Mitigation

care Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
careersptView Comments
2015-11-30
2015-11-30View Mitigation

careers Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
carsptView Comments
2015-11-30
2015-11-30No
cartierptView Comments
2015-11-30
2015-11-30View Mitigation

cartier Mitigation

By Richemont DNS Inc.

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

Provide a brief explanation of the TLD:

.CARTIER TLD is a closed Brand new gTLD operated by Richemont DNS Inc

Protections:

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

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

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


2016-04-05

Richemont DNS Inc.Yes
casaptView Comments
2015-11-30
2015-11-30View Mitigation

casa 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
cashptView Comments
2015-11-30
2015-11-30View Mitigation

cash Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
casinoptView Comments
2015-11-30
2015-11-30View Mitigation

casino Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cateringptView Comments
2015-11-30
2015-11-30View Mitigation

catering Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cbaptView Comments
2015-11-30
2015-11-30View Mitigation

cba Mitigation

By Commonwealth Bank of Australia

Refer measures in attached PDF document


View Documents
2016-04-13

Commonwealth Bank of AustraliaYes
centerptView Comments
2015-11-30
2015-11-30View Mitigation

center Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
ceoptView Comments
2015-11-30
2015-11-30No
cernptView Comments
2015-11-30
2015-11-30View 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
cfdptView Comments
2015-11-30
2015-11-30View 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
chanelptView Comments
2015-11-30
2015-11-30View 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
chatptView Comments
2015-11-30
2015-11-30View Mitigation

chat Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cheapptView Comments
2015-11-30
2015-11-30View Mitigation

cheap Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
chloeptView Comments
2015-11-30
2015-11-30View Mitigation

chloe Mitigation

By Richemont DNS Inc.

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

Provide a brief explanation of the TLD:

.CHLOE TLD is a closed Brand new gTLD operated by Richemont DNS Inc

Protections:

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

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

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


2016-04-05

Richemont DNS Inc.Yes
christmasptView Comments
2015-11-30
2015-11-30No
churchptView Comments
2015-11-30
2015-11-30View Mitigation

church Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
circleptView Comments
2015-11-30
2015-11-30View 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
cityptView Comments
2015-11-30
2015-11-30View Mitigation

city Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
claimsptView Comments
2015-11-30
2015-11-30View Mitigation

claims Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cleaningptView Comments
2015-11-30
2015-11-30View Mitigation

cleaning Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
clickptView Comments
2015-11-30
2015-11-30No
clinicptView Comments
2015-11-30
2015-11-30No
cliniqueptView Comments
2015-11-30
2015-11-30View Mitigation

clinique Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.Yes
clothingptView Comments
2015-11-30
2015-11-30View Mitigation

clothing Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cloudptView Comments
2015-11-30
2015-11-30View 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
clubptView Comments
2015-11-30
2015-11-30No
clubmedptView Comments
2015-11-30
2015-11-30View 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
coachptView Comments
2015-11-30
2015-11-30View Mitigation

coach Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
codesptView Comments
2015-11-30
2015-11-30View Mitigation

codes Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
coffeeptView Comments
2015-11-30
2015-11-30View Mitigation

coffee Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
collegeptView Comments
2015-11-30
2015-11-30No
commbankptView Comments
2015-11-30
2015-11-30View Mitigation

commbank Mitigation

By Commonwealth Bank of Australia

Refer measures in attached PDF document


View Documents
2016-04-13

Commonwealth Bank of AustraliaYes
communityptView Comments
2015-11-30
2015-11-30View Mitigation

community Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
companyptView Comments
2015-11-30
2015-11-30View Mitigation

company Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
computerptView Comments
2015-11-30
2015-11-30View Mitigation

computer Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
condosptView Comments
2015-11-30
2015-11-30View Mitigation

condos Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
constructionptView Comments
2015-11-30
2015-11-30View Mitigation

construction Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
consultingptView Comments
2015-11-30
2015-11-30View Mitigation

consulting Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
contractorsptView Comments
2015-11-30
2015-11-30View Mitigation

contractors Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cookingptView Comments
2015-11-30
2015-11-30View Mitigation

cooking 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
coolptView Comments
2015-11-30
2015-11-30View Mitigation

cool Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
countryptView Comments
2015-11-30
2015-11-30View 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
couponsptView Comments
2015-11-30
2015-11-30View Mitigation

coupons Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
creditptView Comments
2015-11-30
2015-11-30View Mitigation

credit Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
creditcardptView Comments
2015-11-30
2015-11-30View Mitigation

creditcard Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cricketptView Comments
2015-11-30
2015-11-30View Mitigation

cricket Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

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

1. Registry Operator will commit to:

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

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

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

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


2016-04-25

Famous Four Media LimitedNo
crsptView Comments
2015-11-30
2015-11-30View Mitigation

crs Mitigation

By Federated Co-operatives Limited

Registry Operator has updated its domain registration policy to take steps to mitigate the risk of confusion. Registry Operator will not register two string SLDs where it believes there is a risk of confusion with a ccTLD, confusion that the domain is operated by or for the owner of a ccTLD, or otherwise associated with a government or government agency. Registry Operator will also terminate any domains which have been registered but which no longer conform to the foregoing.


2016-03-30

Federated Co-operatives LimitedNo
cruisesptView Comments
2015-11-30
2015-11-30View Mitigation

cruises Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
cuisinellaptView Comments
2015-11-30
2015-11-30View 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
cyouptView Comments
2015-11-30
2015-11-30View Mitigation

cyou Mitigation

By Beijing Gamease Age Digital Technology Co., Ltd.

A Proposal to Minimize the Potential Likelihood of Confusion in Connection with the Allocation of Specific Two Character Domain Names

The intention of the Beijing Gamease Age Digital Technology Go., Ltd. (“Cyou”) is to proactively protect the ownership of the “Changyou.com” and “Cyou.com” trademark at the Internet TLD name space and to provide a trusted, hierarchical and intuitive namespace for registrants and users that use CYOU’s broad range of high-quality entertainment and virtual communities services.

Protections

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the following:
.cyou is identical to a qualifying registered trademark;
1. .cyou is not a Generic String, as this is defined in Specification 11;
2. .cyou TLD has developed and will implement a closed registration policy for .cyou that requires that all domain names in the .cyou TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
3. As required under the Registry Agreement, the .cyou TLD will clearly publish this registration policy;

As a brand TLD, registering domain names to unaffiliated third parties will not be allowed and thus clearly designate to the public that .cyou TLD is a proprietary space in which all second-level domains in the TLD are being operated by Beijing Gamease Age Digital Technology Go., Ltd., its Affiliates and Trademark Licensees and not a government or their corresponding country code operator.



View Documents
2016-04-25

Beijing Gamease Age Digital Technology Co., Ltd.No
danceptView Comments
2015-11-30
2015-11-30View Mitigation

dance Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
dateptView Comments
2015-11-30
2015-11-30View Mitigation

date Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

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

1. Registry Operator will commit to:

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

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

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

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


2016-04-25

Famous Four Media LimitedNo
datingptView Comments
2015-11-30
2015-11-30View Mitigation

dating Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
datsunptView Comments
2015-11-30
2015-11-30View Mitigation

datsun Mitigation

By NISSAN MOTOR CO., LTD.

2 Letter Codes Mitigation Plan for NISSAN TLDs
(.nissan .infiniti .datsun)

To address the confusion concerns cited by governments regarding the use of the second-level domains in the NISSAN TLDs,
NISSAN MOTOR CO., LTD. will implement a closed registration policy for NISSAN TLDs that mitigates the potential confusion. To these ends, NISSAN MOTOR CO., LTD. commits to the following:

・Developing and implementing a closed registration policy for NISSAN TLDs that requires that all domains name in the TLDs be registered and used by NISSAN MOTOR CO., LTD., its affiliates, or its trademark licensees;

・Clearly publishing this registration policy on Registry Operator`s homepage for the NISSAN TLDs at “nic.nissan”,”nic.infiniti”, and “nic.datsun”.

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

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

・Using all domain names in the NISSAN TLDs in association with NISSAN`s brand products, and services.

This publicly available registration and usage policy would prevent Governments from registering domains in the NISSAN TLDs. It would therefore clearly designate to the public that NISSAN TLDs were proprietary spaces in which all second-level domains in the TLDs were being operated by NISSAN MOTOR CO., LTD. and not governments.


2016-04-25

NISSAN MOTOR CO., LTD.No
dealptView Comments
2015-11-30
2015-11-30View 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
dealsptView Comments
2015-11-30
2015-11-30View Mitigation

deals Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
degreeptView Comments
2015-11-30
2015-11-30View Mitigation

degree Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
deliveryptView Comments
2015-11-30
2015-11-30View Mitigation

delivery Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
dellptView Comments
2015-11-30
2015-11-30View Mitigation

dell Mitigation

By Dell Inc.

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

1. .DELL is identical to a qualifying registered trademark;
2. .DELL is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement;
3. Dell Inc. has developed and will implement a closed registration policy for .DELL that requires that all domain names in the .DELL gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, Dell Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and
5. .DELL 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 .DELL gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .DELL gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Dell Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator.

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


2016-04-15

Dell Inc.Yes
deloitteptView Comments
2015-11-30
2015-11-30View 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
deltaptView Comments
2015-11-30
2015-11-30View 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

pt Comments

By Ana Cristina Ferreira Amoroso das Neves, Director, Department Information Society, Fundação para a Ciência e a Tecnologia, Ministry of Science, Technology and Higher Education

I request previous comments to objections to the release of the ".pt" as the SLD signalling 1) consumer protection concerns and confusion; 2) some gTLD correspond to a regulated market in EU countries, so their release might generate possible abuses and confusion at the end-users level and therefore must be subject to authorization by the Portuguese Government; 3) others should remain reserved so that can only be assigned to a person, entity or corporation proposed or accepted by the Portuguese Government, which demands consultations with the Portuguese Government. These comments are due to the ICANN's new process launched on the 6th October 2015 on the use of the 2-letter CC and CN at the SLD, taken into account nonetheless GAC's advice from Dublin Communiqué (October 2015). Confusability exists in all instances since the PT code is widely recognized both on and off the Internet as an identifier for Portugal. In this regard, we are concerned that consumers assume that persons or undertakings operating under "pt.string" not only offer their services in Portugal or products or services related to Portugal but that they comply with applicable regulations. As this may not be warranted by registration policies and contracts, we would request Portuguese Government is consulted before any registration, regardless of the grounds for objection. Portugal reserves the right to change position in this regard in the future.
The Portuguese Government will continue to closely follow the evolution of the market and of the technical and political framework to collect data and evidence to better understand the consequences of such release.

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