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
omegaitView Comments
2015-12-08
2015-12-08View Mitigation

omega Mitigation

By The Swatch Group Ltd

Provide a brief explanation of the TLD:
The Swatch Group Ltd has applied for .OMEGA to run a closed .brand environment.

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

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


2016-04-25

The Swatch Group LtdYes
onlitView Comments
2015-12-08
2015-12-08View Mitigation

onl Mitigation

By I-Registry Ltd.

The .onl TLD provides a unique digital identity and facilitate the promotion of the brand ONL to Internet users in general.

Protections
I-Registry Ltd. (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 respective governments, 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, or may result in the suspension or termination of the domain name registration.

Furthermore, contained within our Acceptable Use Policy for the .onl TLD is the following text:
The Registrant of a domain name, as recorded in the Registry Service, will be responsible for:
- the use of their domain name;
- 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;
- no domain name in the .onl space shall be used in a manner which infringes any other third parties’ rights;
- no domain name in the .onl space is in breach with any applicable laws, government rules or requirements or for the purposes of undertaking any illegal or fraudulent actions, including spam or phishing activities.

Failure to comply with the above provisions may result in the suspension or termination of the domain name registration by the Registry. Thus all Registrants in the TLD, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-20

I-Registry Ltd.No
onlineitView Comments
2015-12-08
2015-12-08View Mitigation

online Mitigation

By Radix

Dear ICANN,

We are submitting these proposed measures to avoid confusion with specific country codes at the second level for each of our 8 TLDs, in relation to the individual Government objections that have been raised pertaining to the release of those specific two-character labels:

Protections

Radix understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the following:

1. Radix will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the relevant governments that have raised concerns about the release of specific two-character labels at the second level, and provide a written report in response; and

b. where, in Radix’s sole opinion, misuse has occurred, Radix will seek to work
with the sponsoring registrar and/or directly with the registrant to address the misuse.

c. In the event that misuse continues to occur, Radix may, in its sole discretion,
undertake direct action up to and including suspension or deletion of the domain name.

Thank you.


2016-04-25

RadixNo
oooitView Comments
2015-12-08
2015-12-08View Mitigation

ooo Mitigation

By Infibeam Incorporation Ltd.

The .OOO gTLD could be used for any entity launching or expanding an e-commerce venture as it offers a domain name of their choice.

The Registry Operator wishes to adopt the following mechanism of mitigation measures for all the 2 character labels identified by ICANN :

1.Registry Operator will commit to:
 a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the concerned government, and provide a written report in response; and
 b. where, in RO’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 .OOO TLD is the following text:

“The Registrant of a domain name, as recorded in the Registry Service, will be responsible for:
 the use of their domain name;
 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, 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-21

Infibeam Incorporation Ltd.No
oracleitView Comments
2015-12-08
2015-12-08Yes
orangeitView Comments
2015-12-08
2015-12-08View Mitigation

orange Mitigation

By Orange Brand Services Limited

Provide a brief explanation of the TLD:
Orange Brand Services Limited has applied for .ORANGE to run a closed .brand environment.

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

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


2016-04-25

Orange Brand Services LimitedYes
organicitView Comments
2015-12-08
2015-12-08View Mitigation

organic 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
originsitView Comments
2015-12-08
2015-12-08Yes
osakaitView Comments
2015-12-08
2015-12-08No
otsukaitView Comments
2015-12-08
2015-12-08View Mitigation

otsuka Mitigation

By Otsuka Holdings Co., Ltd.

.otsuka 2 Letter Codes Mitigation Plan

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

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

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

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

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

・Using all domain names in the .otsuka TLD in association with Otsuka Holdings Co., Ltd.`s brand products, and services.

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


2016-04-25

Otsuka Holdings Co., Ltd.Yes
pageitView Comments
2015-12-08
2015-12-08View Mitigation

page 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
paneraiitView Comments
2015-12-08
2015-12-08View Mitigation

panerai Mitigation

By Richemont DNS Inc.

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

Provide a brief explanation of the TLD:

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

Protections:

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

Compliance with Specification 13 prohibits the .PANERAI TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .PANERAI 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
partnersitView Comments
2015-12-08
2015-12-08View Mitigation

partners Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
partsitView Comments
2015-12-08
2015-12-08View Mitigation

parts Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
partyitView Comments
2015-12-08
2015-12-08View Mitigation

party 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
payitView Comments
2015-12-08
2015-12-08View Mitigation

pay 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
petitView Comments
2015-12-08
2015-12-08View Mitigation

pet 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
pharmacyitView Comments
2015-12-08
2015-12-08View Mitigation

pharmacy Mitigation

By National Association of Boards of Pharmacy

Background

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

Implementation Plan to Avoid Confusion

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

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

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

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

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


View Documents
2016-04-25

National Association of Boards of PharmacyNo
philipsitView Comments
2015-12-08
2015-12-08View Mitigation

philips Mitigation

By Koninklijke Philips N.V.

Registry Operator will not register two letter SLDs that are equal to ccTLDs under its gTLD, unless:
- the corresponding country has given general consent to register these SLDs, or
- that Registry Operator has obtained authorization of the competent authority of that corresponding country to register the two letter SLD under its TLD..

Registry Operator will not register two letter SLDs under its TLD that are equal to ccTLDs when the corresponding country has objected to these registrations.


2016-03-08

Koninklijke Philips N.V.Yes
photoitView Comments
2015-12-08
2015-12-08No
photographyitView Comments
2015-12-08
2015-12-08View Mitigation

photography Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
photositView Comments
2015-12-08
2015-12-08View Mitigation

photos Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
piagetitView Comments
2015-12-08
2015-12-08View Mitigation

piaget Mitigation

By Richemont DNS Inc.

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

Provide a brief explanation of the TLD:

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

Protections:

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

Compliance with Specification 13 prohibits the .PIAGET TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .PIAGET 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
picsitView Comments
2015-12-08
2015-12-08No
pictetitView Comments
2015-12-08
2015-12-08View Mitigation

pictet Mitigation

By Pictet Europe S.A.

.PICTET gTLD Confusion Avoidance Plan

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

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

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


2016-04-21

Pictet Europe S.A.Yes
picturesitView Comments
2015-12-08
2015-12-08View Mitigation

pictures Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
pinitView Comments
2015-12-08
2015-12-08View Mitigation

pin 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
pinkitView Comments
2015-12-08
2015-12-08View Mitigation

pink 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
pizzaitView Comments
2015-12-08
2015-12-08View Mitigation

pizza Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
placeitView Comments
2015-12-08
2015-12-08View Mitigation

place Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
playitView Comments
2015-12-08
2015-12-08View Mitigation

play 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
plumbingitView Comments
2015-12-08
2015-12-08View Mitigation

plumbing Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
plusitView Comments
2015-12-08
2015-12-08View Mitigation

plus Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
pncitView Comments
2015-12-08
2015-12-08Yes
pohlitView Comments
2015-12-08
2015-12-08View Mitigation

pohl Mitigation

By Deutsche Vermögensberatung Aktiengesellschaft DVAG

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


View Documents
2016-04-25

Deutsche Vermögensberatung Aktiengesellschaft DVAGNo
pokeritView Comments
2015-12-08
2015-12-08View Mitigation

poker 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
pornitView Comments
2015-12-08
2015-12-08View Mitigation

porn Mitigation

By ICM Registry

Protections

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

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

Furthermore, we have the following Anti-Abuse Policy:

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

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

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

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

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

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

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

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

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


2016-04-19

ICM Registry No
pressitView Comments
2015-12-08
2015-12-08View Mitigation

press Mitigation

By Radix

Dear ICANN,

We are submitting these proposed measures to avoid confusion with specific country codes at the second level for each of our 8 TLDs, in relation to the individual Government objections that have been raised pertaining to the release of those specific two-character labels:

Protections

Radix understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the following:

1. Radix will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the relevant governments that have raised concerns about the release of specific two-character labels at the second level, and provide a written report in response; and

b. where, in Radix’s sole opinion, misuse has occurred, Radix will seek to work
with the sponsoring registrar and/or directly with the registrant to address the misuse.

c. In the event that misuse continues to occur, Radix may, in its sole discretion,
undertake direct action up to and including suspension or deletion of the domain name.

Thank you.


2016-04-25

RadixNo
primeitView Comments
2015-12-08
2015-12-08View Mitigation

prime 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
productionsitView Comments
2015-12-08
2015-12-08View Mitigation

productions Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
progressiveitView Comments
2015-12-08
2015-12-08No
propertiesitView Comments
2015-12-08
2015-12-08View Mitigation

properties Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
propertyitView Comments
2015-12-08
2015-12-08No
protectionitView Comments
2015-12-08
2015-12-08No
pubitView Comments
2015-12-08
2015-12-08View Mitigation

pub Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
questitView Comments
2015-12-08
2015-12-08No
readitView Comments
2015-12-08
2015-12-08View Mitigation

read 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
recipesitView Comments
2015-12-08
2015-12-08View Mitigation

recipes Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
reditView Comments
2015-12-08
2015-12-08View Mitigation

red 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
redstoneitView Comments
2015-12-08
2015-12-08View Mitigation

redstone Mitigation

By Redstone Haute Couture Co., Ltd.

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

The fundamental mission and purpose of .Redstone TLD application is to protect the trademark rights of “Redstone” mark that was established by Redstone Haute Couture Company Ltd.. The .Redstone TLD will be used for Redstone itself and tis portfolio companies and brands to ensure best-in-class online experience and customer satisfaction. By operating and utilizing the .Redstone TLD, Redstone also hopes to be the pioneer of digital branding for the fast-growing luxury retailing and marketing in China as well as in the world. .Redstone TLD will carry the corporate vision set by of the Redstone company-we strive to become an influential fashion company in the world’s fashion realm through professionalism and culture cohesion, so as to contribute to the peaceful rise of China.

Protections

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

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

Redstone Haute Couture Company Ltd. confirms that all registrations of two letter
domain names shall comply with the requirements of Specification 13.


View Documents
2016-04-25

Redstone Haute Couture Co., Ltd.Yes
redumbrellaitView Comments
2015-12-08
2015-12-08No
rehabitView Comments
2015-12-08
2015-12-08View Mitigation

rehab Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
reiseitView Comments
2015-12-08
2015-12-08View Mitigation

reise Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
reisenitView Comments
2015-12-08
2015-12-08View Mitigation

reisen Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
renitView Comments
2015-12-08
2015-12-08View Mitigation

ren Mitigation

By Beijing Qianxiang Wangjing Technology Development Co., Ltd.

.REN Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the domains with the following:
1. not be used to imply that it is, or represents, the government；
2. investigate any reports of misuse or abusive use, including misleading or deceptive conduct, and provide a written report in response; and
3. in Registry Operator’s sole opinion, if misuse has occurred or been reported, 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.


View Documents
2016-04-25

Beijing Qianxiang Wangjing Technology Development Co., Ltd.No
rentitView Comments
2015-12-08
2015-12-08No
rentalsitView Comments
2015-12-08
2015-12-08View Mitigation

rentals Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
repairitView Comments
2015-12-08
2015-12-08View Mitigation

repair Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
reportitView Comments
2015-12-08
2015-12-08View Mitigation

report Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
republicanitView Comments
2015-12-08
2015-12-08View Mitigation

republican Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
restaurantitView Comments
2015-12-08
2015-12-08View Mitigation

restaurant Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
reviewitView Comments
2015-12-08
2015-12-08View Mitigation

review 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
reviewsitView Comments
2015-12-08
2015-12-08View Mitigation

reviews Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
richitView Comments
2015-12-08
2015-12-08View Mitigation

rich Mitigation

By I-Registry Ltd.

The .RICH TLD has the mission to serve the needs of rich people and service providers for the rich (the Rich) worldwide in terms of privacy, communication, and exceptional services.

Protections
I-Registry Ltd. (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 respective governments, 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, or may result in the suspension or termination of the domain name registration.

Furthermore, contained within our Acceptable Use Policy for the .rich TLD is the following text:
The Registrant of a domain name, as recorded in the Registry Service, will be responsible for:
- the use of their domain name;
- 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;
- no domain name in the .RICH space shall be used in a manner which infringes any other third parties’ rights;
- no domain name in the .RICH space is in breach with any applicable laws, government rules or requirements or for the purposes of undertaking any illegal or fraudulent actions, including spam or phishing activities.

Failure to comply with the above provisions may result in the suspension or termination of the domain name registration by the Registry. Thus all Registrants in the TLD, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-20

I-Registry Ltd.No
ricohitView Comments
2015-12-08
2015-12-08View Mitigation

ricoh Mitigation

By Ricoh Company, Ltd.

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

Provide a brief explanation of the TLD: .ricoh is a closed Brand new gTLD operated by Ricoh Company, Ltd.

Protections:

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

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

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

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

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

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

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


2016-04-25

Ricoh Company, Ltd.Yes
ripitView Comments
2015-12-08
2015-12-08View Mitigation

rip Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
rmititView Comments
2015-12-08
2015-12-08View Mitigation

rmit Mitigation

By Royal Melbourne Institute of Technology

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


2016-04-22

Royal Melbourne Institute of TechnologyYes
rocheritView Comments
2015-12-08
2015-12-08View Mitigation

rocher Mitigation

By Ferrero Trading Lux S.A.

.ROCHER TLD is a closed Brand new gTLD operated by Ferrero Trading Lux S.A.

Protections:

Ferrero Trading Lux S.A. for the .ROCHER TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Ferrero Trading Lux S.A. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

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

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


2016-04-18

Ferrero Trading Lux S.A.Yes
rocksitView Comments
2015-12-08
2015-12-08View Mitigation

rocks Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
rodeoitView Comments
2015-12-08
2015-12-08View Mitigation

rodeo 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
roomitView Comments
2015-12-08
2015-12-08View Mitigation

room 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
ruhritView Comments
2015-12-08
2015-12-08View Mitigation

ruhr Mitigation

By regiodot GmbH & Co. KG

Proposed Measures to avoid confusion


View Documents
2016-04-20

regiodot GmbH & Co. KGNo
runitView Comments
2015-12-08
2015-12-08View Mitigation

run Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
rweitView Comments
2015-12-08
2015-12-08View Mitigation

rwe Mitigation

By RWE AG

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

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

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


2016-04-25

RWE AGYes
saarlanditView Comments
2015-12-08
2015-12-08No
safeitView Comments
2015-12-08
2015-12-08View Mitigation

safe 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
safetyitView Comments
2015-12-08
2015-12-08View Mitigation

safety Mitigation

By Safety Registry Services, LLC

Safety Registry Services, LLC, the Registry Operator for the .SAFETY TLD, is operating .SAFETY as a restricted TLD where only credible and verified individuals or organizations are eligible to register and use domain names in .SAFETY. As such, .SAFETY will clearly only include registrants and domains related to the safety community.

To address the confusion concerns cited by government representatives regarding the use of second-level domains in the .SAFETY gTLD, Safety Registry Services, LLC will implement a restricted registration policy for .SAFETY that mitigates the potential confusion. To this end, Safety Registry Services, LLC commits to the following:

1. Developing and implementing a restricted registration policy for .SAFETY that adheres to the values of the safety community;
2. Clearly publishing this registration policy on Registry Operator’s homepage for .SAFETY;
3. Including this registration policy in Registry Operator’s Registry-Registrar Agreement with all contracted registrars for the .SAFETY TLD; and
4. Enforcing of this registration policy and ensuring continued compliance with the TLD’s credibility standards.

This registration and usage policy would prevent national governments and their representatives from registering domains in the .SAFETY TLD, because the only possible registrants allowed under the registration policy will be members of the .SAFETY community. Safety Registry Services, LLC will clearly designate to users that .SAFETY is a restricted space in which all second-level domains were registered by and for members of the safety community.


2016-04-25

Safety Registry Services, LLCNo
saleitView Comments
2015-12-08
2015-12-08View Mitigation

sale Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
sandvikitView Comments
2015-12-08
2015-12-08View Mitigation

sandvik Mitigation

By Sandvik AB

.sandvik is a closed top-level domain name for the sole and exclusive use of Sandvik AB.

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


2016-04-11

Sandvik ABYes
sandvikcoromantitView Comments
2015-12-08
2015-12-08View Mitigation

sandvikcoromant Mitigation

By Sandvik AB

.sandvikcoromant is a closed top-level domain name for the sole and exclusive use of Sandvik AB.

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


2016-04-11

Sandvik ABYes
sanofiitView Comments
2015-12-08
2015-12-08View Mitigation

sanofi Mitigation

By Sanofi

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

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

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


2016-04-25

SanofiYes
sarlitView Comments
2015-12-08
2015-12-08View Mitigation

sarl Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
sasitView Comments
2015-12-08
2015-12-08View Mitigation

sas 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
saveitView Comments
2015-12-08
2015-12-08View Mitigation

save 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
saxoitView Comments
2015-12-08
2015-12-08View Mitigation

saxo Mitigation

By Saxo Bank A/S

.saxo is a closed top-level domain name for the sole and exclusive use of Saxo Bank A/S.

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


2016-04-08

Saxo Bank A/S Yes
sbsitView Comments
2015-12-08
2015-12-08View Mitigation

sbs Mitigation

By SPECIAL BROADCASTING SERVICE CORPORATION

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


2016-04-22

SPECIAL BROADCASTING SERVICE CORPORATIONYes
scaitView Comments
2015-12-08
2015-12-08View Mitigation

sca Mitigation

By SVENSKA CELLULOSA AKTIEBOLAGET SCA (publ)

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

Provide a brief explanation of the TLD:

.SCA TLD is a closed Brand new gTLD operated by SVENSKA CELLULOSA AKTIEBOLAGET SCA (publ)

Protections:

SVENSKA CELLULOSA AKTIEBOLAGET SCA (publ) for the .SCA TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the SVENSKA CELLULOSA AKTIEBOLAGET SCA (publ) will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

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

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


2016-04-25

SVENSKA CELLULOSA AKTIEBOLAGET SCA (publ)Yes
schmidtitView Comments
2015-12-08
2015-12-08View Mitigation

schmidt Mitigation

By SALM S.A.S.

.schmidt 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 .schmidt 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. .schmidt is identical to a qualifying registered trademark;
2. .schmidt is not a Generic String, as this is defined in Specification 11;
3. .schmidt TLD has developed and will implement a closed registration policy for .schmidt that requires that all domain names in the .schmidt TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .schmidt TLD will clearly publish this registration policy;
5. .schmidt TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.
Compliance with Specification 13 prohibits the .schmidt TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .schmidt 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
schoolitView Comments
2015-12-08
2015-12-08View Mitigation

school Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
schuleitView Comments
2015-12-08
2015-12-08View Mitigation

schule Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
scienceitView Comments
2015-12-08
2015-12-08View Mitigation

science 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
scoritView Comments
2015-12-08
2015-12-08View Mitigation

scor Mitigation

By SCOR SE

.scor is a closed top-level domain name for the sole and exclusive use of Scor SE.

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


2016-04-13

SCOR SEYes
secureitView Comments
2015-12-08
2015-12-08View Mitigation

secure 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
securityitView Comments
2015-12-08
2015-12-08No
seneritView Comments
2015-12-08
2015-12-08View Mitigation

sener Mitigation

By Sener Ingeniería y Sistemas, S.A.

Provide a brief explanation of the TLD:
Sener Ingeniería y Sistemas, S.A. has applied for .SENER to run a closed .brand environment.

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

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


2016-04-25

Sener Ingeniería y Sistemas, S.A.Yes
servicesitView Comments
2015-12-08
2015-12-08View Mitigation

services Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
sevenitView Comments
2015-12-08
2015-12-08View Mitigation

seven Mitigation

By Seven West Media Ltd

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


2016-04-27

Seven West Media LtdYes
sewitView Comments
2015-12-08
2015-12-08View Mitigation

sew Mitigation

By SEW-EURODRIVE GmbH & Ko KG

.sew is a closed top-level domain name for the sole and exclusive use of SEW-EURODRIVE GmbH & Co KG.

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


2016-04-20

SEW-EURODRIVE GmbH & Ko KGYes
sexitView Comments
2015-12-08
2015-12-08View Mitigation

sex Mitigation

By ICM Registry

Protections

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

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

Furthermore, we have the following Anti-Abuse Policy:

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

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

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

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

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

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

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

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

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


2016-04-19

ICM Registry No
sexyitView Comments
2015-12-08
2015-12-08No

it Comments

By Rita Forsi, Italia GAC Representative, Ministry of Economic Development

With reference to the process for Considering Comments for Two-Character Letter/Letter Labels launched by ICANN on October 6, 2015, Italy restates its position expressed on March 25, 2015 (http://mm.icann.org/pipermail/twochar_comments/2015/000063.html) and on May 14, 2015 (email attached).

Italy does not object tout-court to the delegation of our ccSLD, but wants to exercise the right to evaluate the delegation of “it” as a SLD on a case-by-case basis.

The evaluation process takes into account not only the confusion risks, but also the national and international legal framework (e.g. IPR) and opportunity considerations (e.g. it.sucks).

We would like to recall that both the Singapore and Dublin GAC Communiqué advise the Board that comments submitted by the relevant Governments be fully considered regardless of the grounds for objection.

For the abovementioned reasons, we reiterate our position expressed in March 25 2015 for the release of the two‐character “it” label at the second level under new gTLDs.

In general, “it” label string may be released to the extent that the registry operator reaches a formal agreement with the Italian government (included our ccTLD registry “.it”) as per Specification 5 of the Registry Agreement.
This policy is to be applied to all new gTLDs, including, but not limited to, those falling within Category 1 and Category 2 of the Beijing Communiquè. who have requested for the release of “it” labels at the second level.
The authorization requests should be sent to the Italian GAC representatives.

Furthermore, we would like to underline that these “lines-to-take” are agreed with the “.it” Registry.

Rita Forsi

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