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

pizza Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

place Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

plumbing Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

plus Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
pncptView Comments
2015-11-30
2015-11-30Yes
pohlptView Comments
2015-11-30
2015-11-30View 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
pornptView Comments
2015-11-30
2015-11-30View 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
pressptView Comments
2015-11-30
2015-11-30View 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
primeptView Comments
2015-11-30
2015-11-30View 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
productionsptView Comments
2015-11-30
2015-11-30View Mitigation

productions Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
progressiveptView Comments
2015-11-30
2015-11-30No
propertiesptView Comments
2015-11-30
2015-11-30View Mitigation

properties Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
propertyptView Comments
2015-11-30
2015-11-30No
protectionptView Comments
2015-11-30
2015-11-30No
pubptView Comments
2015-11-30
2015-11-30View 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
questptView Comments
2015-11-30
2015-11-30No
recipesptView Comments
2015-11-30
2015-11-30View Mitigation

recipes Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
redstoneptView Comments
2015-11-30
2015-11-30View 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
redumbrellaptView Comments
2015-11-30
2015-11-30No
rehabptView Comments
2015-11-30
2015-11-30View 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
reisenptView Comments
2015-11-30
2015-11-30View Mitigation

reisen Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

rentals Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

repair Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

report Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

restaurant Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
reviewptView Comments
2015-11-30
2015-11-30View 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
reviewsptView Comments
2015-11-30
2015-11-30View 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
richptView Comments
2015-11-30
2015-11-30View 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
ricohptView Comments
2015-11-30
2015-11-30View 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
ripptView Comments
2015-11-30
2015-11-30View 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
rocherptView Comments
2015-11-30
2015-11-30View 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
rocksptView Comments
2015-11-30
2015-11-30View 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
rodeoptView Comments
2015-11-30
2015-11-30View 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
ruhrptView Comments
2015-11-30
2015-11-30View Mitigation

ruhr Mitigation

By regiodot GmbH & Co. KG

Proposed Measures to avoid confusion


View Documents
2016-04-20

regiodot GmbH & Co. KGNo
runptView Comments
2015-11-30
2015-11-30View Mitigation

run Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
rweptView Comments
2015-11-30
2015-11-30View 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
saarlandptView Comments
2015-11-30
2015-11-30No
saleptView Comments
2015-11-30
2015-11-30View 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
sandvikptView Comments
2015-11-30
2015-11-30View 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
sandvikcoromantptView Comments
2015-11-30
2015-11-30View 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
sanofiptView Comments
2015-11-30
2015-11-30View 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
sarlptView Comments
2015-11-30
2015-11-30View Mitigation

sarl Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
sasptView Comments
2015-11-30
2015-11-30View 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
saveptView Comments
2015-11-30
2015-11-30View 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
saxoptView Comments
2015-11-30
2015-11-30View 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
sbsptView Comments
2015-11-30
2015-11-30View 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
scaptView Comments
2015-11-30
2015-11-30View 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
schmidtptView Comments
2015-11-30
2015-11-30View 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
schoolptView Comments
2015-11-30
2015-11-30View Mitigation

school Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

schule Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
scienceptView Comments
2015-11-30
2015-11-30View 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
scorptView Comments
2015-11-30
2015-11-30View 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
secureptView Comments
2015-11-30
2015-11-30View 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
securityptView Comments
2015-11-30
2015-11-30No
senerptView Comments
2015-11-30
2015-11-30View 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
servicesptView Comments
2015-11-30
2015-11-30View Mitigation

services Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
sevenptView Comments
2015-11-30
2015-11-30View 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
sexptView Comments
2015-11-30
2015-11-30View 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
sexyptView Comments
2015-11-30
2015-11-30No
shellptView Comments
2015-11-30
2015-11-30View Mitigation

shell Mitigation

By Shell Information Technology International Inc

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

Provide a brief explanation of the TLD:

.SHELL TLD is a closed Brand new gTLD operated by Shell Information Technology International Inc

Protections:

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

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

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


2016-04-05

Shell Information Technology International IncYes
shoesptView Comments
2015-11-30
2015-11-30View Mitigation

shoes Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

show Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

silk 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
singlesptView Comments
2015-11-30
2015-11-30View Mitigation

singles Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

site 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
skiptView Comments
2015-11-30
2015-11-30View Mitigation

ski Mitigation

By Starting Dot


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

The proposed measure can be found in the file attached.


View Documents
2016-04-25

Starting DotNo
skyptView Comments
2015-11-30
2015-11-30View Mitigation

sky Mitigation

By Sky International AG

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


2016-04-14

Sky International AGYes
skypeptView Comments
2015-11-30
2015-11-30View Mitigation

skype Mitigation

By Microsoft Corporation

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

Provide a brief explanation of the TLD:

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

Protections:

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

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

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


2016-04-05

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

soccer Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

social Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

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

software Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

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

sohu Mitigation

By Sohu.com Limited

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

Sohu.com LimitedNo
solarptView Comments
2015-11-30
2015-11-30View Mitigation

solar Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

solutions Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

sony Mitigation

By Sony Corporation

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

Provide a brief explanation of the TLD:

.sony is a closed Brand new gTLD operated by Sony Corporation

Protections:

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

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

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

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

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

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

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


2016-04-25

Sony CorporationYes
spaceptView Comments
2015-11-30
2015-11-30View Mitigation

space 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
spiegelptView Comments
2015-11-30
2015-11-30View Mitigation

spiegel Mitigation

By SPIEGEL-Verlag Rudolf Augstein GmbH & Co. KG

Please find SPIEGEL-Verlag Rudolf Augstein GmbH & Co. KG's "Mitigation Measures to Avoid Confusion" (concerning 2-letter labels in general) for the “.SPIEGEL” TLD attached.


View Documents
2016-04-25

SPIEGEL-Verlag Rudolf Augstein GmbH & Co. KGYes
spreadbettingptView Comments
2015-11-30
2015-11-30View Mitigation

spreadbetting Mitigation

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

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

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


View Documents
2016-04-21

dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]No
starhubptView Comments
2015-11-30
2015-11-30Yes
stcptView Comments
2015-11-30
2015-11-30No
stcgroupptView Comments
2015-11-30
2015-11-30No
storeptView Comments
2015-11-30
2015-11-30View Mitigation

store 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
studioptView Comments
2015-11-30
2015-11-30View Mitigation

studio Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

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

style Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

supplies Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

supply Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

support 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
surfptView Comments
2015-11-30
2015-11-30View Mitigation

surf 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
surgeryptView Comments
2015-11-30
2015-11-30View Mitigation

surgery Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

suzuki Mitigation

By SUZUKI MOTOR CORPORATION

.suzuki 2 Letter Codes Mitigation Plan

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

・Developing and implementing a closed registration policy for .suzuki that requires that all domains name in the TLD be registered and used by SUZUKI MOTOR CORPORATION, its affiliates, or its trademark licensees;

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

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

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

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

This publicly available registration and usage policy would prevent Governments from registering domains in the .suzuki TLD. It would therefore clearly designate to the public that .suzuki was a proprietary space in which all second-level domains in the TLD were being operated by SUZUKI MOTOR CORPORATION and not governments.


2016-04-25

SUZUKI MOTOR CORPORATIONYes
swatchptView Comments
2015-11-30
2015-11-30View Mitigation

swatch Mitigation

By The Swatch Group Ltd

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

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

Compliance with Specification 13 prohibits the .SWATCH TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .SWATCH 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 LtdNo
swissptView Comments
2015-11-30
2015-11-30View Mitigation

swiss Mitigation

By Swiss Confederation

Proposed Measure to Avoid Confusion — Restrictive registration policy for 2-letter .SWISS domain names

Brief explanation of the TLD:
The purpose of the .SWISS TLD is to serve the Swiss community, defined as the community of individuals, legal entities and public institutions with a bona fide presence in Switzerland.
Registration of domain names under the .SWISS TLD is restricted to members of the Swiss community and subject to the further requirement that the domain name registrant’s presence in Switzerland and the registrant’s use of the domain name must comply with Swiss law.
The government of the Swiss Confederation acts as the central representative body for the Swiss community with regard to the .SWISS TLD, in consultation with the members of the Swiss community.
The measures described below address the confusion concerns cited by the governments of Anguilla, Singapore and St. Helena as well as by the Organization of African Union regarding the use of the 2-letter codes ai, sg, sh and au at the second-level of the .SWISS TLD. In the context of the .SWISS TLD, those 2-letter codes have the following meaning:
ai : official 2-letter acronym for the Swiss Canton Appenzell-Innerrhoden (see www.ai.ch)
sg : official 2-letter acronym for the Swiss Canton St-Gallen (see www.sg.ch)
sh : official 2-letter acronym for the Swiss Canton Schaffhausen (see www.sh.ch)
au : official name of the Swiss political municipality Au (see www.au.ch)

Protections:
The Swiss Confederation, as Registry Operator, has already implemented a community-based registrations policy for the .swiss TLD with particularly strict rules for all 2-letter codes. These rules were promulgated in the Federal Ordinance on Domain Names (https://www.admin.ch/opc/en/classified-compilation/20141744/index.html) and eliminate any risk of confusion. They comprise the following protections relevant to 2-letter codes:
• Each of the 26 Swiss Cantons has a single official 2-letter acronym. The Swiss Canton 2-letter acronyms are long-established, widely used and generally accepted. For instance, they appear on Swiss car license plates and are harmonized by ISO 3166-2 standard. Besides these acronyms, three Swiss political municipalities have a 2-letter name: Au, Gy and Lü.
• Only 2-letter codes matching with the official 2-letter acronym designating a Swiss Canton or matching with the official name of a Swiss political municipality will be released for registration in .SWISS.
• The 2-letter codes .SWISS domains are reserved exclusively for the respective Swiss cantonal governments, respectively for the executive council of the political municipality hence confusion due to misuse is not possible;
• A clear context specific to Switzerland is implicit with the .SWISS TLD and enforced by way of the registration policy, hence confusion with the ISO-3166 territory is not possible;
• The registration policy applying to 2-letter codes .SWISS domains is part of the Swiss legislation on domain names and published on Registry Operator’s homepage.

Process and eligibility considerations:
• The first-come-first-served principle is not applied for the allocation of .swiss domain names. As a principle, every allocation of domain name is based on an evaluation. Once a .swiss domain name application is submitted, the Registry will examine if the requested domain name is available and if the application meet the syntax rules and the general eligibility requirements set forth in the registration policy.
• The community-based eligibility and name selection criteria of the .swiss registration policy described above would also prevent the governments of Anguilla, Singapore and St. Helena as well as the Organization of African Union from registering 2-letter codes domains in the .SWISS TLD.


2016-04-21

Swiss ConfederationNo
sydneyptView Comments
2015-11-30
2015-11-30View Mitigation

sydney Mitigation

By State of NSW, Department of Premier and Cabinet

Proposed Measure to Avoid Confusion

A brief explanation of the TLD:
.sydney is a geographic TLD for the city of Sydney, Australia and the State Government of New South Wales is the designated ‘Registry Operator’. While .sydney is an open TLD, registration of domain names is limited to New South Wales residents and businesses, and other entities with an interest in the state of New South Wales, Australia as described in the Registration Policy.

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

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

1. Registry Operator will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the government of a related country code, and provide a written report in response; and

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

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

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

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


2016-04-21

State of NSW, Department of Premier and CabinetNo
systemsptView Comments
2015-11-30
2015-11-30View Mitigation

systems Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

tab Mitigation

By Tabcorp Holdings Limited

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


2016-04-22

Tabcorp Holdings LimitedYes
taipeiptView Comments
2015-11-30
2015-11-30No
tatamotorsptView Comments
2015-11-30
2015-11-30View Mitigation

tatamotors Mitigation

By Tata Motors Ltd

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

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

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


2016-04-25

Tata Motors LtdYes
tattooptView Comments
2015-11-30
2015-11-30No

pt Comments

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

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

A note about our terms of service:

We have updated our electronic terms of service to provide greater transparency and align with laws applicable to us. Learn more.

This site uses cookies to deliver an efficient user experience and to help us see how the site is used. Learn more.OK

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