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
sucksjoView Comments
2015-12-17
2015-12-17View Mitigation

sucks Mitigation

By Vox Populi Registry Ltd.

Proposed Measure to Avoid Confusion—Phased Allocation

dotSucks is designed to help consumers find their voices and allow companies to find the value in criticism. Each dotSucks domain has the potential to become an essential part of every organization’s customer relationship management program.

Phased Allocation - Upon the release of the letter/letter combination corresponding to the following objected to country codes (ai, bh, bm, ci, cn, eg, gb, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk), Registry Operator will provide an exclusive thirty (30) day period in which registration of such letter/letter combination will be made only available to the applicable country code manager as listed at: http://www.iana.org/domains/root/db/

This type of phased allocation has been previously approved by ICANN as an acceptable and complete measure to avoid confusion with applicable country codes.

For example, .TRAVEL included the following in its RSEP on 18 May 2009:
“In seeking to minimize any confusion with county codes, Tralliance will initially place all two-letter country code names, as listed in the ISO 31-66 list, in the RFP allocation round and will seek expressions of interest from all country code managers for their respective two-character names. Tralliance will allocate two letter country codes to any corresponding country code managers (as listed at: http://www.iana.org/domains/root/db/) that desire to register their name, with no restriction other that payment of normal registration fees and a commitment to use the registered name.”

The Board approved the change via a resolution on 5 August 2010: https://www.icann.org/resources/board- material/resolutions-2010-08-05-en.

At that time, the amendment to the .TRAVEL Registry Agreement permitted release of 2 characters through a Phased Allocation Program https://www.icann.org/resources/unthemed-pages/travel-appendix-7-2010-08-23-en).

.TRAVEL has subsequently entered into a new gTLD Registry Agreement with ICANN and carried over the previous Board- approved release of two-characters through its phased allocation program. Current .TRAVEL Specification 5 language:
“All single-character and two-character labels that were previously reserved by the Registry Operator prior to the Effective Date of this Registry Agreement may be allocated through ICANN-accredited registrars according to a phased allocation program (“Phased Allocation Program”). The domain names included within the scope of the Phased Allocation Program shall be limited to a single and two-character labels. Registry Operator reserves the right to not allocate all single and two-character labels. Pursuant to the Phased Allocation Program, Registry Operator may elect to allocate labels by applying one or more of the following processes: 1) request for proposals and allocation based on evaluation criteria; 2) auction; or 3) first come, first serve registration.”

Similar Phased Allocation Programs have been approved by ICANN as an implementation of measures to avoid confusion with corresponding country codes in .BIZ, .INFO, .ORG, and .JOBS.


2016-04-22

Vox Populi Registry Ltd.No
tattoojoView Comments
2015-12-17
2015-12-17No
travelersjoView Comments
2015-12-17
2015-12-17Yes
travelersinsurancejoView Comments
2015-12-17
2015-12-17No
trvjoView Comments
2015-12-17
2015-12-17No
volkswagenjoView Comments
2015-12-17
2015-12-17View Mitigation

volkswagen Mitigation

By Volkswagen Group of America Inc.

.volkswagen is a closed Brand TLD for the sole and exclusive use of Volkswagen Group of America Inc.

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

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

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

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

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

By this submission Volkswagen Group of America Inc. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

Volkswagen Group of America Inc.Yes
warmanjoView Comments
2015-12-17
2015-12-17View Mitigation

warman Mitigation

By Weir Group IP Limited

Provide a brief explanation of the TLD:
Weir Group IP Limited has applied for .WARMAN to run a closed .brand environment.

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

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


2016-04-25

Weir Group IP LimitedYes
weirjoView Comments
2015-12-17
2015-12-17View Mitigation

weir Mitigation

By Weir Group IP Limited

Provide a brief explanation of the TLD:
Weir Group IP Limited has applied for .WEIR to run a closed .brand environment.

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

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


2016-04-25

Weir Group IP LimitedYes
woodsidejoView Comments
2015-12-17
2015-12-17View Mitigation

woodside Mitigation

By Woodside Energy ltd

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


2016-04-22

Woodside Energy ltdYes
wowjoView Comments
2015-12-17
2015-12-17View Mitigation

wow Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .WOW TLD, proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, and vn. 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, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, or vn) corresponds to its country code:
a. the use in the .WOW TLD of a domain name consisting of a 2-character letter-letter combination listed above; and
b. corresponds to that government’s country code; and
c. implies or represents that it is, or has the approval of, such government; and
2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion:
a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or
b. may cause the domain name’s records to be removed from the DNS; and
3. Provide a written response within a commercially reasonable time period.

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



2016-04-25

Amazon Registry Services, Inc.No
xn--3oq18vl8pn36ajoView Comments
2015-12-17
2015-12-17View Mitigation

xn--3oq18vl8pn36a Mitigation

By Volkswagen (China) Investment Co., Ltd.

.大众汽车 is a closed Brand TLD for the sole and exclusive use of Volkswagen (China) Investment Co., Ltd.

Protections
Volkswagen (China) Investment Co., Ltd. (Registry Operator) for the .大众汽车 TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Registry Operator will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

.大众汽车 is identical to a qualifying registered trademark;
.大众汽车 is not a Generic String, as this is defined in Specification 11;
Registry Operator has developed and will implement a closed registration policy for .大众汽车 that requires that all domain names in the .大众汽车 TLD be registered only by Volkswagen (China) Investment Co., Ltd., its Affiliates, and its Trademark Licensees.

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

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

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

By this submission Volkswagen (China) Investment Co., Ltd. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

Volkswagen (China) Investment Co., Ltd.Yes
xn--80adxhksjoView Comments
2015-12-17
2015-12-17No
xn--gk3at1e joView Comments
2015-12-17
2015-12-17View Mitigation

xn--gk3at1e  Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .xn--gk3at1e TLD, proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, and vn. 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, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, or vn) corresponds to its country code:
a. the use in the .xn--gk3at1e TLD of a domain name consisting of a 2-character letter-letter combination listed above; and
b. corresponds to that government’s country code; and
c. implies or represents that it is, or has the approval of, such government; and
2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion:
a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or
b. may cause the domain name’s records to be removed from the DNS; and
3. Provide a written response within a commercially reasonable time period.

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


2016-04-25

Amazon Registry Services, Inc.No
abbngView Comments
2015-12-18
2015-12-18View Mitigation

abb Mitigation

By ABB Ltd

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

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

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


2016-04-25

ABB LtdYes
acongView Comments
2015-12-18
2015-12-18View Mitigation

aco Mitigation

By ACO Severin Ahlmann GmbH & Co. KG

.ACO mitigation measures apply across all two character labels

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

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

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

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

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

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

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


2016-04-19

ACO Severin Ahlmann GmbH & Co. KGYes
anzngView Comments
2015-12-18
2015-12-18View Mitigation

anz Mitigation

By Australia and New Zealand Banking Group Limited

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


2016-04-22

Australia and New Zealand Banking Group LimitedYes
artengView Comments
2015-12-18
2015-12-18View Mitigation

arte Mitigation

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

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

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

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


2016-04-25

Association Relative à la Télévision Européenne G.E.I.E.Yes
audingView Comments
2015-12-18
2015-12-18View Mitigation

audi Mitigation

By Audi Aktiengesellschaft

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

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

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

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

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

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

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


2016-04-21

Audi AktiengesellschaftYes
audiongView Comments
2015-12-18
2015-12-18No
blackfridayngView Comments
2015-12-18
2015-12-18No
bugattingView Comments
2015-12-18
2015-12-18View Mitigation

bugatti Mitigation

By Bugatti International SA

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

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

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

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

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

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

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


2016-04-21

Bugatti International SAYes
christmasngView Comments
2015-12-18
2015-12-18No
clickngView Comments
2015-12-18
2015-12-18No
cscngView Comments
2015-12-18
2015-12-18View Mitigation

csc Mitigation

By Alliance-One Services, Inc.

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


2016-04-26

Alliance-One Services, Inc.Yes
dietngView Comments
2015-12-18
2015-12-18No
flowersngView Comments
2015-12-18
2015-12-18No
foxngView Comments
2015-12-18
2015-12-18View Mitigation

fox Mitigation

By FOX Registry, LLC

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

Provide a brief explanation of the TLD:

.FOX TLD is a closed Brand new gTLD operated by FOX Registry, LLC

Protections:

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

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

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


2016-04-21

FOX Registry, LLCYes
gamengView Comments
2015-12-18
2015-12-18No
geangView Comments
2015-12-18
2015-12-18View Mitigation

gea Mitigation

By GEA Group Aktiengesellschaft

.GEA Mitigation

.GEA mitigation measures apply across all two character labels
By GEA Group Aktiengesellschaft

.GEA TLD is a closed Brand new gTLD operated by GEA Group Aktiengesellschaft.

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

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

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

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

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

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

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






2016-04-19

GEA Group AktiengesellschaftYes
giftngView Comments
2015-12-18
2015-12-18No
graingerngView Comments
2015-12-18
2015-12-18View Mitigation

grainger Mitigation

By Grainger Registry Services, LLC

.GRAINGER gTLD Confusion Avoidance Plan

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

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

With this submission, Grainger Registry Services, LLC confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Grainger Registry Services, LLCYes
guitarsngView Comments
2015-12-18
2015-12-18No
helpngView Comments
2015-12-18
2015-12-18No
hiphopngView Comments
2015-12-18
2015-12-18No
hostingngView Comments
2015-12-18
2015-12-18No
juegosngView Comments
2015-12-18
2015-12-18No
lamborghiningView Comments
2015-12-18
2015-12-18View Mitigation

lamborghini Mitigation

By Automobili Lamborghini S.p.A.

.lamborghini is a closed Brand TLD for the sole and exclusive use of Automobili Lamborghini S.p.A.

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

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

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

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

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

By this submission Automobili Lamborghini S.p.A. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

Automobili Lamborghini S.p.A.Yes
lanxessngView Comments
2015-12-18
2015-12-18View Mitigation

lanxess Mitigation

By LANXESS Corporation

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

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

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


2016-04-25

LANXESS CorporationYes
lefrakngView Comments
2015-12-18
2015-12-18View Mitigation

lefrak Mitigation

By LeFrak Organization, Inc.

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


2016-04-19

LeFrak Organization, Inc.Yes
linkngView Comments
2015-12-18
2015-12-18No
lolngView Comments
2015-12-18
2015-12-18No
mattelngView Comments
2015-12-18
2015-12-18View Mitigation

mattel Mitigation

By Mattel Sites, Inc.

.MATTEL gTLD Confusion Avoidance Plan

Mattel Sites, Inc., a wholly-owned subsidiary of Mattel, Inc. and the Registry Operator for the .MATTEL gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Mattel Sites, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

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

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


View Documents
2016-04-19

Mattel Sites, Inc.Yes
momngView Comments
2015-12-18
2015-12-18No
moscowngView Comments
2015-12-18
2015-12-18No
mtrngView Comments
2015-12-18
2015-12-18View Mitigation

mtr Mitigation

By MTR CORPORATION LIMITED

To minimize the possibility of confusion for lables, ai, bh, bm, ci, cn, eg, gb, il, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw and uk, we have reserved those names at the second level of .mtr. In other words, no one can register and activate those domain names at the second level unless we received consent from ICANN and the relevant government body.

For label(s) pertaining to confusion but ICANN allows us to offer for registration and activation at the second level (e.g. in), it will not be used in a way causing confusion. In fact, .mtr is a brand TLD, the registrant of .mtr will not be people in the general public. The use of it can be easily controlled. In case of receiving comment from the relevant government, we can react at a quick and direct manner.


2016-03-24

MTR CORPORATION LIMITEDYes
photongView Comments
2015-12-18
2015-12-18No
picsngView Comments
2015-12-18
2015-12-18No
pncngView Comments
2015-12-18
2015-12-18Yes
propertyngView Comments
2015-12-18
2015-12-18No
redumbrellangView Comments
2015-12-18
2015-12-18No
rmitngView Comments
2015-12-18
2015-12-18View 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
safetyngView Comments
2015-12-18
2015-12-18View 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
sanofingView Comments
2015-12-18
2015-12-18View 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
sexyngView Comments
2015-12-18
2015-12-18No
sucksngView Comments
2015-12-18
2015-12-18View Mitigation

sucks Mitigation

By Vox Populi Registry Ltd.

Proposed Measure to Avoid Confusion—Phased Allocation

dotSucks is designed to help consumers find their voices and allow companies to find the value in criticism. Each dotSucks domain has the potential to become an essential part of every organization’s customer relationship management program.

Phased Allocation - Upon the release of the letter/letter combination corresponding to the following objected to country codes (ai, bh, bm, ci, cn, eg, gb, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk), Registry Operator will provide an exclusive thirty (30) day period in which registration of such letter/letter combination will be made only available to the applicable country code manager as listed at: http://www.iana.org/domains/root/db/

This type of phased allocation has been previously approved by ICANN as an acceptable and complete measure to avoid confusion with applicable country codes.

For example, .TRAVEL included the following in its RSEP on 18 May 2009:
“In seeking to minimize any confusion with county codes, Tralliance will initially place all two-letter country code names, as listed in the ISO 31-66 list, in the RFP allocation round and will seek expressions of interest from all country code managers for their respective two-character names. Tralliance will allocate two letter country codes to any corresponding country code managers (as listed at: http://www.iana.org/domains/root/db/) that desire to register their name, with no restriction other that payment of normal registration fees and a commitment to use the registered name.”

The Board approved the change via a resolution on 5 August 2010: https://www.icann.org/resources/board- material/resolutions-2010-08-05-en.

At that time, the amendment to the .TRAVEL Registry Agreement permitted release of 2 characters through a Phased Allocation Program https://www.icann.org/resources/unthemed-pages/travel-appendix-7-2010-08-23-en).

.TRAVEL has subsequently entered into a new gTLD Registry Agreement with ICANN and carried over the previous Board- approved release of two-characters through its phased allocation program. Current .TRAVEL Specification 5 language:
“All single-character and two-character labels that were previously reserved by the Registry Operator prior to the Effective Date of this Registry Agreement may be allocated through ICANN-accredited registrars according to a phased allocation program (“Phased Allocation Program”). The domain names included within the scope of the Phased Allocation Program shall be limited to a single and two-character labels. Registry Operator reserves the right to not allocate all single and two-character labels. Pursuant to the Phased Allocation Program, Registry Operator may elect to allocate labels by applying one or more of the following processes: 1) request for proposals and allocation based on evaluation criteria; 2) auction; or 3) first come, first serve registration.”

Similar Phased Allocation Programs have been approved by ICANN as an implementation of measures to avoid confusion with corresponding country codes in .BIZ, .INFO, .ORG, and .JOBS.


2016-04-22

Vox Populi Registry Ltd.No
tattoongView Comments
2015-12-18
2015-12-18No
travelersngView Comments
2015-12-18
2015-12-18Yes
travelersinsurancengView Comments
2015-12-18
2015-12-18No
trvngView Comments
2015-12-18
2015-12-18No
volkswagenngView Comments
2015-12-18
2015-12-18View Mitigation

volkswagen Mitigation

By Volkswagen Group of America Inc.

.volkswagen is a closed Brand TLD for the sole and exclusive use of Volkswagen Group of America Inc.

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

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

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

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

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

By this submission Volkswagen Group of America Inc. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

Volkswagen Group of America Inc.Yes
warmanngView Comments
2015-12-18
2015-12-18View Mitigation

warman Mitigation

By Weir Group IP Limited

Provide a brief explanation of the TLD:
Weir Group IP Limited has applied for .WARMAN to run a closed .brand environment.

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

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


2016-04-25

Weir Group IP LimitedYes
weirngView Comments
2015-12-18
2015-12-18View Mitigation

weir Mitigation

By Weir Group IP Limited

Provide a brief explanation of the TLD:
Weir Group IP Limited has applied for .WEIR to run a closed .brand environment.

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

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


2016-04-25

Weir Group IP LimitedYes
woodsidengView Comments
2015-12-18
2015-12-18View Mitigation

woodside Mitigation

By Woodside Energy ltd

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


2016-04-22

Woodside Energy ltdYes
wowngView Comments
2015-12-18
2015-12-18View Mitigation

wow Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .WOW TLD, proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, and vn. 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, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, or vn) corresponds to its country code:
a. the use in the .WOW TLD of a domain name consisting of a 2-character letter-letter combination listed above; and
b. corresponds to that government’s country code; and
c. implies or represents that it is, or has the approval of, such government; and
2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion:
a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or
b. may cause the domain name’s records to be removed from the DNS; and
3. Provide a written response within a commercially reasonable time period.

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



2016-04-25

Amazon Registry Services, Inc.No
xn--3oq18vl8pn36angView Comments
2015-12-18
2015-12-18View Mitigation

xn--3oq18vl8pn36a Mitigation

By Volkswagen (China) Investment Co., Ltd.

.大众汽车 is a closed Brand TLD for the sole and exclusive use of Volkswagen (China) Investment Co., Ltd.

Protections
Volkswagen (China) Investment Co., Ltd. (Registry Operator) for the .大众汽车 TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Registry Operator will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

.大众汽车 is identical to a qualifying registered trademark;
.大众汽车 is not a Generic String, as this is defined in Specification 11;
Registry Operator has developed and will implement a closed registration policy for .大众汽车 that requires that all domain names in the .大众汽车 TLD be registered only by Volkswagen (China) Investment Co., Ltd., its Affiliates, and its Trademark Licensees.

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

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

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

By this submission Volkswagen (China) Investment Co., Ltd. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

Volkswagen (China) Investment Co., Ltd.Yes
xn--80adxhksngView Comments
2015-12-18
2015-12-18No
xn--gk3at1e ngView Comments
2015-12-18
2015-12-18View Mitigation

xn--gk3at1e  Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .xn--gk3at1e TLD, proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, and vn. 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, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, or vn) corresponds to its country code:
a. the use in the .xn--gk3at1e TLD of a domain name consisting of a 2-character letter-letter combination listed above; and
b. corresponds to that government’s country code; and
c. implies or represents that it is, or has the approval of, such government; and
2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion:
a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or
b. may cause the domain name’s records to be removed from the DNS; and
3. Provide a written response within a commercially reasonable time period.

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


2016-04-25

Amazon Registry Services, Inc.No
moscowhkView Comments
2016-02-02
2016-02-02No
xn--80adxhkshkView Comments
2016-02-02
2016-02-02No
insurancehkView Comments
2016-02-02
2016-02-02View Mitigation

insurance Mitigation

By fTLD Registry Services, LLC

Please see the attached file that details fTLD Registry Services' implementation plan for .BANK and .INSURANCE to avoid confusion with corresponding country codes.


View Documents
2016-04-20

fTLD Registry Services, LLCNo
sucksgrView Comments
2016-02-02
2016-02-02View Mitigation

sucks Mitigation

By Vox Populi Registry Ltd.

Proposed Measure to Avoid Confusion—Phased Allocation

dotSucks is designed to help consumers find their voices and allow companies to find the value in criticism. Each dotSucks domain has the potential to become an essential part of every organization’s customer relationship management program.

Phased Allocation - Upon the release of the letter/letter combination corresponding to the following objected to country codes (ai, bh, bm, ci, cn, eg, gb, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk), Registry Operator will provide an exclusive thirty (30) day period in which registration of such letter/letter combination will be made only available to the applicable country code manager as listed at: http://www.iana.org/domains/root/db/

This type of phased allocation has been previously approved by ICANN as an acceptable and complete measure to avoid confusion with applicable country codes.

For example, .TRAVEL included the following in its RSEP on 18 May 2009:
“In seeking to minimize any confusion with county codes, Tralliance will initially place all two-letter country code names, as listed in the ISO 31-66 list, in the RFP allocation round and will seek expressions of interest from all country code managers for their respective two-character names. Tralliance will allocate two letter country codes to any corresponding country code managers (as listed at: http://www.iana.org/domains/root/db/) that desire to register their name, with no restriction other that payment of normal registration fees and a commitment to use the registered name.”

The Board approved the change via a resolution on 5 August 2010: https://www.icann.org/resources/board- material/resolutions-2010-08-05-en.

At that time, the amendment to the .TRAVEL Registry Agreement permitted release of 2 characters through a Phased Allocation Program https://www.icann.org/resources/unthemed-pages/travel-appendix-7-2010-08-23-en).

.TRAVEL has subsequently entered into a new gTLD Registry Agreement with ICANN and carried over the previous Board- approved release of two-characters through its phased allocation program. Current .TRAVEL Specification 5 language:
“All single-character and two-character labels that were previously reserved by the Registry Operator prior to the Effective Date of this Registry Agreement may be allocated through ICANN-accredited registrars according to a phased allocation program (“Phased Allocation Program”). The domain names included within the scope of the Phased Allocation Program shall be limited to a single and two-character labels. Registry Operator reserves the right to not allocate all single and two-character labels. Pursuant to the Phased Allocation Program, Registry Operator may elect to allocate labels by applying one or more of the following processes: 1) request for proposals and allocation based on evaluation criteria; 2) auction; or 3) first come, first serve registration.”

Similar Phased Allocation Programs have been approved by ICANN as an implementation of measures to avoid confusion with corresponding country codes in .BIZ, .INFO, .ORG, and .JOBS.


2016-04-22

Vox Populi Registry Ltd.No
bmsnaView Comments
2016-01-31
2016-02-22View Mitigation

bms Mitigation

By Bristol Myers Squibb

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


2016-04-20

Bristol Myers SquibbYes
cscnaView Comments
2016-01-31
2016-02-22View Mitigation

csc Mitigation

By Alliance-One Services, Inc.

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


2016-04-26

Alliance-One Services, Inc.Yes
freenaView Comments
2016-01-31
2016-02-22No
graingernaView Comments
2016-01-31
2016-02-22View Mitigation

grainger Mitigation

By Grainger Registry Services, LLC

.GRAINGER gTLD Confusion Avoidance Plan

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

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

With this submission, Grainger Registry Services, LLC confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Grainger Registry Services, LLCYes
insurancenaView Comments
2016-01-31
2016-02-22View Mitigation

insurance Mitigation

By fTLD Registry Services, LLC

Please see the attached file that details fTLD Registry Services' implementation plan for .BANK and .INSURANCE to avoid confusion with corresponding country codes.


View Documents
2016-04-20

fTLD Registry Services, LLCNo
junipernaView Comments
2016-01-31
2016-02-22Yes
lanxessnaView Comments
2016-01-31
2016-02-22View Mitigation

lanxess Mitigation

By LANXESS Corporation

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

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

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


2016-04-25

LANXESS CorporationYes
latrobenaView Comments
2016-01-31
2016-02-22View Mitigation

latrobe Mitigation

By Latrobe University

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


2016-04-26

Latrobe UniversityYes
lefraknaView Comments
2016-01-31
2016-02-22View Mitigation

lefrak Mitigation

By LeFrak Organization, Inc.

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


2016-04-19

LeFrak Organization, Inc.Yes
lupinnaView Comments
2016-01-31
2016-02-22Yes
mattelnaView Comments
2016-01-31
2016-02-22View Mitigation

mattel Mitigation

By Mattel Sites, Inc.

.MATTEL gTLD Confusion Avoidance Plan

Mattel Sites, Inc., a wholly-owned subsidiary of Mattel, Inc. and the Registry Operator for the .MATTEL gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Mattel Sites, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

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

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


View Documents
2016-04-19

Mattel Sites, Inc.Yes
moscownaView Comments
2016-01-31
2016-02-22No
nationwidenaView Comments
2016-01-31
2016-02-22Yes
onyoursidenaView Comments
2016-01-31
2016-02-22Yes
rexrothnaView Comments
2016-01-31
2016-02-22View Mitigation

rexroth Mitigation

By Robert Bosch GMBH

Provide a brief explanation of the TLD:
Robert Bosch GMBH has applied for .REXROTH to run a closed .brand environment.

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

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


2016-04-25

Robert Bosch GMBHYes
safetynaView Comments
2016-01-31
2016-02-22View 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
shangrilanaView Comments
2016-01-31
2016-02-22Yes
sucksnaView Comments
2016-01-31
2016-02-22View Mitigation

sucks Mitigation

By Vox Populi Registry Ltd.

Proposed Measure to Avoid Confusion—Phased Allocation

dotSucks is designed to help consumers find their voices and allow companies to find the value in criticism. Each dotSucks domain has the potential to become an essential part of every organization’s customer relationship management program.

Phased Allocation - Upon the release of the letter/letter combination corresponding to the following objected to country codes (ai, bh, bm, ci, cn, eg, gb, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk), Registry Operator will provide an exclusive thirty (30) day period in which registration of such letter/letter combination will be made only available to the applicable country code manager as listed at: http://www.iana.org/domains/root/db/

This type of phased allocation has been previously approved by ICANN as an acceptable and complete measure to avoid confusion with applicable country codes.

For example, .TRAVEL included the following in its RSEP on 18 May 2009:
“In seeking to minimize any confusion with county codes, Tralliance will initially place all two-letter country code names, as listed in the ISO 31-66 list, in the RFP allocation round and will seek expressions of interest from all country code managers for their respective two-character names. Tralliance will allocate two letter country codes to any corresponding country code managers (as listed at: http://www.iana.org/domains/root/db/) that desire to register their name, with no restriction other that payment of normal registration fees and a commitment to use the registered name.”

The Board approved the change via a resolution on 5 August 2010: https://www.icann.org/resources/board- material/resolutions-2010-08-05-en.

At that time, the amendment to the .TRAVEL Registry Agreement permitted release of 2 characters through a Phased Allocation Program https://www.icann.org/resources/unthemed-pages/travel-appendix-7-2010-08-23-en).

.TRAVEL has subsequently entered into a new gTLD Registry Agreement with ICANN and carried over the previous Board- approved release of two-characters through its phased allocation program. Current .TRAVEL Specification 5 language:
“All single-character and two-character labels that were previously reserved by the Registry Operator prior to the Effective Date of this Registry Agreement may be allocated through ICANN-accredited registrars according to a phased allocation program (“Phased Allocation Program”). The domain names included within the scope of the Phased Allocation Program shall be limited to a single and two-character labels. Registry Operator reserves the right to not allocate all single and two-character labels. Pursuant to the Phased Allocation Program, Registry Operator may elect to allocate labels by applying one or more of the following processes: 1) request for proposals and allocation based on evaluation criteria; 2) auction; or 3) first come, first serve registration.”

Similar Phased Allocation Programs have been approved by ICANN as an implementation of measures to avoid confusion with corresponding country codes in .BIZ, .INFO, .ORG, and .JOBS.


2016-04-22

Vox Populi Registry Ltd.No
wolterskluwernaView Comments
2016-01-31
2016-02-22View Mitigation

wolterskluwer Mitigation

By Wolters Kluwer N.V.

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

Provide a brief explanation of the TLD:

.WOLTERSKLUWER TLD is a closed Brand new gTLD operated by Wolters Kluwer N.V.

Protections:

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

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

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


2016-04-05

Wolters Kluwer N.V.Yes
xn--5su34j936bgsgnaView Comments
2016-01-31
2016-02-22Yes
xn--80adxhksnaView Comments
2016-01-31
2016-02-22No
bmsnaView Comments
2016-02-22
2016-02-22View Mitigation

bms Mitigation

By Bristol Myers Squibb

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


2016-04-20

Bristol Myers SquibbYes
emersonnaView Comments
2016-02-22
2016-02-22Yes
freenaView Comments
2016-02-22
2016-02-22No
gmbhnaView Comments
2016-02-22
2016-02-22View Mitigation

gmbh Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
insurancenaView Comments
2016-02-22
2016-02-22View Mitigation

insurance Mitigation

By fTLD Registry Services, LLC

Please see the attached file that details fTLD Registry Services' implementation plan for .BANK and .INSURANCE to avoid confusion with corresponding country codes.


View Documents
2016-04-20

fTLD Registry Services, LLCNo
junipernaView Comments
2016-02-22
2016-02-22Yes
lidlnaView Comments
2016-02-22
2016-02-22No
lupinnaView Comments
2016-02-22
2016-02-22Yes

jo Comments

By Jowin V Pattamukkil, Student, Technical

I need Jo.win
Under .win domains
For technical website purposes.

It will not be confused with any other govt or other agencies.. It locked only becoz of icann policy of two letter domain reserved... And it is on release option..I need it it urgently.. Becoz of my company needs.. Kindly allow me to register..

ng Comments

By Temitope FASHEDEMI, Director, e-Government, Ministry of Communications

Many of the gTLDs have corresponding names similar to existing businesses, organisations and other entities in Nigeria and allowing registration of 'ng' will lead to confusion and/or misrepresentation with any similar local entity.

Also, some of the gTLDs connote names that are considered abusive, foul, distasteful and otherwise prohibited; allowing 'ng' registration on such domains will imply that Nigeria is associated with and/or implicitly sanctioning the liberal use of such names/words.

It is our expectation that any and all request to register the above mentioned names require express permission from the relevant government organization in Nigeria.This will assist the country forestall the abuse and misuse of reserved names associated with the Government.

hk Comments

By Dominic Kwong, Alternate GAC Representative of Hong Kong Special Administrative Region, China, Office of the Government Chief Information Officer

We would like to reiterate our views to ICANN of 24 March and 27 May 2015, which have stated the confusion and rationale related to the release of "hk" as the second level domain (SLD) in new gTLDs, and "hk" shall NOT be released for ALL requests in the following two categories of new gTLDs:

(a) New gTLDs associated with Highly-regulated Sectors/Closed Entry Requirements in Multiple Jurisdictions and Inherently Governmental Functions as set out in ICANN NGPC Resolution No. 2014.02.05.NG01; and
(b) New gTLDs falling within the category of Geographic gTLDs referred to in ICANN's New gTLD Program (i.e. the gTLD string is a geographic name as provided in the ICANN's gTLD Applicant Guidebook), and .capital, .city, .country, .town, and .world.

gr Comments

By Panagiotis Papaspiliopoulos, Accredited Representative of Greece to the GAC of ICANN, Hellenic Ministry of Infrastructure, Transport & Networks

The Hellenic Republic objects to the release of the ‘gr’ and ‘ελ’ codes under the ‘.SUCKS’ TLD, because such release will have a negative impact on the ‘.gr’ and ‘.ελ’ [xn--qxam] profiles, their consumers and, more broadly, on the reputation of the Hellenic Republic, its government, citizens and businesses. The same rules have also to apply to the names ‘Greece’, ‘Hellas’, ‘Hellenic Republic’, ‘Ellas’, ‘Ελλάς’, ‘Elliniki Dimokratia’, ‘Ελληνική Δημοκρατία’ (the short name and the formal name according to “the United Nations Group of Experts on Geographical Names, Technical Reference Manual for the Standardization of Geographical Names, Part III Names of Countries of the World”) and, generally, to the name of the country in any non-English language. Finally, the Hellenic Republic holds its legitimate right to object to the use of the name of any of its cities, territories and, more broadly, any term related to the history, the cultural identity, the protected Greek products and the touristic representation of the country.

na Comments

By Ziegie Willemse, Deputy Director - MICT, ICTD

RESPONSE TO APPLICATIONS TO AUTHORIZE TWO-CHARACTER (LETTER-LETTER) DOMAINS AT THE SECOND LEVEL BY GAC REPRESENTATIVE OF THE REPUBLIC OF NAMIBIA: 25 MAY 2015



We hereby respectfully submit an objection to release of “.na" with the names in the subject line for its registration by the registry operators of the TLD. We further request clarification from ICANN regarding the implementation of Specification 5 of the current Registry Agreement preventing all two-character ASCII labels from registration or allocation to a registry operator at the second level within the TLD. However, such two-character label strings may be released to the extent that the registry operator reaches agreement with the relevant government and country code manager of the string as specified in the ISO 3166-1 alpha-2 standard (my emphasis added).

".na" is the country code for Namibia and the Applicants are new gTLDs. Save for an agreement between the involved Registry Operators and the Namibian Government, through facilitation by the designated government representative accredited to the GAC, the “.na" with the names in the subject line must remain reserved until assigned to a person or entity proposed, supported or accepted by the Namibian Government and the ccTLD manager for “.na”.

The objection and request for clarification are necessitated based on the following considerations:

· A national policy on the matter is due to be revised to address changes and advances in the Namibian DNS arrangements, which may require such reservations.
· The Namibian Government enacted national legislation on the operation and management of the “.na’ name and these are subject to revision, including ongoing consultations to develop a Namibian solution for the mandate to administer the “.na” name.
· The Namibian Government and wider internet community have limited understanding and appreciation for the two-character ASCII labels authorization process and need urgent and effective capacity building in this critical area from ICANN.
This would allow us to avoid third parties using the name “.na” for the wrong reasons and in a way that could negatively affect the Namibian internet community and the Government of Namibia.

We shall appreciate being informed of the decision taken in regards to our request and objection.



Kind regards,



Henri Jacob Kassen

Director for ICT Development

Ministry of ICT, Government of Namibia

na Comments

By Ziegie Willemse, Deputy Director - MICT, ICTD

RESPONSE TO APPLICATIONS TO AUTHORIZE TWO-CHARACTER (LETTER-LETTER) DOMAINS AT THE SECOND LEVEL BY GAC REPRESENTATIVE OF THE REPUBLIC OF NAMIBIA: 25 MAY 2015

We hereby respectfully submit an objection to release of “.na" with the names in the subject line for its registration by the registry operators of the TLD. We further request clarification from ICANN regarding the implementation of Specification 5 of the current Registry Agreement preventing all two-character ASCII labels from registration or allocation to a registry operator at the second level within the TLD. However, such two-character label strings may be released to the extent that the registry operator reaches agreement with the relevant government and country code manager of the string as specified in the ISO 3166-1 alpha-2 standard (my emphasis added).
".na" is the country code for Namibia and the Applicants are new gTLDs. Save for an agreement between the involved Registry Operators and the Namibian Government, through facilitation by the designated government representative accredited to the GAC, the “.na" with the names in the subject line must remain reserved until assigned to a person or entity proposed, supported or accepted by the Namibian Government and the ccTLD manager for “.na”.
The objection and request for clarification are necessitated based on the following considerations:
· A national policy on the matter is due to be revised to address changes and advances in the Namibian DNS arrangements, which may require such reservations.
· The Namibian Government enacted national legislation on the operation and management of the “.na’ name and these are subject to revision, including ongoing consultations to develop a Namibian solution for the mandate to administer the “.na” name.
· The Namibian Government and wider internet community have limited understanding and appreciation for the two-character ASCII labels authorization process and need urgent and effective capacity building in this critical area from ICANN.
This would allow us to avoid third parties using the name “.na” for the wrong reasons and in a way that could negatively affect the Namibian internet community and the Government of Namibia.
We shall appreciate being informed of the decision taken in regards to our request and objection.

Kind regards,

Henri Jacob Kassen
Director for ICT Development
Ministry of ICT, Government of Namibia

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