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.

TLD  Two
Characters
 
Comments from GovernmentLast
updated
 
RO Mitigation PlanRO NameBRAND TLD
democratptView Comments
2015-11-30
2015-11-30View Mitigation

democrat Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

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

dental Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

dentist Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
desiptView Comments
2015-11-30
2015-11-30No
designptView Comments
2015-11-30
2015-11-30View Mitigation

design Mitigation

By Top Level Design LLC

The .design measures for the avoidance of confusion pertain to the following letter/letter labels: ci, cn, eg, il, in, it, me, pt, and sg.

Top Level Design LLC is the Registry Operator for .design, an open, generic TLD for designers of all disciplines.

Top Level Design LLC understands the concern that confusion may arise and is willing to offer the following:

1. Top Level Design LLC will commit to:
a. Investigate any reports of misuse, including misleading or deceptive conduct, from relevant governments (including Ivory Coast, China, Egypt, Israel, India, Italy, Montenegro, Portugal, and Singapore), and provide a written report in response.
b. Where, in the Registry Operator’s sole opinion, misuse has occurred, the Registry Operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name, in accordance with its Acceptable Use Policy.


2016-04-25

Top Level Design LLCNo
diamondsptView Comments
2015-11-30
2015-11-30View Mitigation

diamonds Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
dietptView Comments
2015-11-30
2015-11-30No
digitalptView Comments
2015-11-30
2015-11-30View Mitigation

digital Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

direct Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

directory Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

discount Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

dnp Mitigation

By Dai Nippon Printing Co., Ltd.

.dnp 2 Letter Codes Mitigation Plan

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

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

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

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

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

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

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


2016-04-25

Dai Nippon Printing Co., Ltd.Yes
docsptView Comments
2015-11-30
2015-11-30View Mitigation

docs Mitigation

By Charleston Road Registry Inc. (d/b/a Google Registry)

Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes.


View Documents
2016-04-22

Charleston Road Registry Inc. (d/b/a Google Registry)No
dogptView Comments
2015-11-30
2015-11-30View Mitigation

dog Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

domains Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

download Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

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

1. Registry Operator will commit to:

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

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

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

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


2016-04-25

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

dunlop Mitigation

By The Goodyear Tire & Rubber Company

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


2016-04-21

The Goodyear Tire & Rubber CompanyYes
dvagptView Comments
2015-11-30
2015-11-30View Mitigation

dvag Mitigation

By Deutsche Vermögensberatung Aktiengesellschaft DVAG

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


View Documents
2016-04-23

View Mitigation

dvag Mitigation

By Deutsche Vermögensberatung Aktiengesellschaft DVAG

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


View Documents
2016-04-25

Deutsche Vermögensberatung Aktiengesellschaft DVAGNo
earthptView Comments
2015-11-30
2015-11-30No
educationptView Comments
2015-11-30
2015-11-30View Mitigation

education Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

email Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

emerck Mitigation

By Merck KGaA

Please find Merck KGaA's "Mitigation Measures to Avoid Confusion" (concerning 2-letter labels in general) the “.EMERCK” TLD attached.


View Documents
2016-04-25

Merck KGaAYes
energyptView Comments
2015-11-30
2015-11-30View Mitigation

energy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

engineer Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

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

engineering Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

enterprises Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

epson Mitigation

By Seiko Epson Corporation

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

Provide a brief explanation of the TLD:

.epson is a closed Brand new gTLD operated by Seiko Epson Corporation

Protections:

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

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

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

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

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

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

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


2016-04-25

Seiko Epson CorporationYes
equipmentptView Comments
2015-11-30
2015-11-30View Mitigation

equipment Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

estate Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

events Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
everbankptView Comments
2015-11-30
2015-11-30Yes
exchangeptView Comments
2015-11-30
2015-11-30View Mitigation

exchange Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

expert Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

exposed Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

express Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

fail Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

faith Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

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

1. Registry Operator will commit to:

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

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

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

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


2016-04-25

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

family Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
fanptView Comments
2015-11-30
2015-11-30No
fansptView Comments
2015-11-30
2015-11-30No
farmptView Comments
2015-11-30
2015-11-30View Mitigation

farm Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

fashion Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
ferreroptView Comments
2015-11-30
2015-11-30View Mitigation

ferrero Mitigation

By Ferrero Trading Lux S.A.

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

Protections:

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

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

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


2016-04-18

Ferrero Trading Lux S.A.Yes
filmptView Comments
2015-11-30
2015-11-30View Mitigation

film Mitigation

By Motion Picture Domain Registry

.film Mitigation

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

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

Protections:

Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:
1. Registry Operator will commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the government of a related country code, and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

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

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


2016-04-14

Motion Picture Domain RegistryNo
finalptView Comments
2015-11-30
2015-11-30View Mitigation

final Mitigation

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

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

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

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

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


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

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

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

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

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

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




2016-04-22

Núcleo de Informação e Coordenação do Ponto BR - NIC.brNo
financeptView Comments
2015-11-30
2015-11-30View Mitigation

finance Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

financial Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

fire Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .Brand TLDs .AUDIBLE, .AWS, .FIRE, .IMDB, .KINDLE, .PRIME, .SILK, and .ZAPPOS (collectively, “the .Brand TLDs”) proposes release of the following 2-character letter-letter combinations: : ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw.

ARSI has executed Specification 13 to the Registry Agreement for each of the .Brand TLDs. Specification 13 contractually requires ARSI to apply measures which, in and of themselves, avoid confusion with the country codes corresponding to the 2-character letter-letter combinations listed above, namely:

1. Each of the .Brand TLDs is identical to a qualifying registered trademark;
2. Each of the .Brand TLDs is not a Generic String, as this is defined in Specification 11;
3. ARSI has developed and will implement a registration policy for each of the .Brand TLDs that requires all domain names in each such TLD be registered only by ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates;
4. ARSI will publish the registration policy for each of the .Brand TLDs upon delegation; and
5. ARSI has ensured, and will continue to ensure, its compliance with the registration policy through annual certification of qualification for Specification 13 for each of the .Brand TLDs.

Compliance with Specification 13 clearly designates to the public that the .Brand TLDs are proprietary spaces in which ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates use all second-level domain names. Accordingly, there will be no basis on which a letter-letter domain name registered in any of the .Brand TLDs could be confused with the country codes corresponding to the 2-character letter-letter combinations listed above.


2016-04-25

Amazon Registry Services, Inc.Yes
firestoneptView Comments
2015-11-30
2015-11-30View Mitigation

firestone Mitigation

By Bridgestone Corporation

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

Provide a brief explanation of the TLD:

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

Protections:

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

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

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

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

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

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

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


2016-04-25

Bridgestone CorporationYes
fishptView Comments
2015-11-30
2015-11-30View Mitigation

fish Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

fishing Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
fitptView Comments
2015-11-30
2015-11-30View Mitigation

fit Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
fitnessptView Comments
2015-11-30
2015-11-30View Mitigation

fitness Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

flights Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

florist Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
flowersptView Comments
2015-11-30
2015-11-30No
flsmidthptView Comments
2015-11-30
2015-11-30Yes
footballptView Comments
2015-11-30
2015-11-30View Mitigation

football Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

forex Mitigation

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

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

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


View Documents
2016-04-21

dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]No
forsaleptView Comments
2015-11-30
2015-11-30View Mitigation

forsale Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

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

foundation Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

frl Mitigation

By Ewout de Graaf

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

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

Furthermore, .frl acceptable use policy contains definitions and measures to avoid confusion between the use of an .frl domain name and country codes listed in the ISO-3166 list of 2-letter country codes. Please review attached document for more information.


View Documents
2016-04-25

Ewout de GraafNo
fundptView Comments
2015-11-30
2015-11-30View Mitigation

fund Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

furniture Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

futbol Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

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

fyi Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
galleryptView Comments
2015-11-30
2015-11-30View Mitigation
View Documents
2016-04-25

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

gallup Mitigation

By Gallup, Inc.

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


2016-04-18

Gallup, Inc.Yes
gameptView Comments
2015-11-30
2015-11-30No
gardenptView Comments
2015-11-30
2015-11-30View Mitigation

garden Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
gentingptView Comments
2015-11-30
2015-11-30Yes
giftptView Comments
2015-11-30
2015-11-30No
giftsptView Comments
2015-11-30
2015-11-30View Mitigation

gifts Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

gives Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

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

glass Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

global Mitigation

By Dot GLOBAL Domain Registry Limited

ABOUT .GLOBAL

.GLOBAL operates an open registration policy with no restrictions.

.Global is a clearly defined name path for organisations large and small who wish to demonstrate a global presence, or promote global services and products.

The Registry Operator has an Acceptable Use Policy (http://go.global/registry-policies/aup/) that prevents abusive use of .GLOBAL domain names which creates security and stability issues for the Registry, Registrars and Registrants – as well as for users of the Internet in general.

The Registry Operator actively monitors the .GLOBAL namespace for abuse and suspicious behaviour using a third party solution. In co-operation with Registrars, .GLOBAL takes action when abuse or suspicious behaviour is detected.

Protections

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

Registry Operator will commit to:

A. investigate any reports of misuse, including misleading or deceptive conduct, including those from the government Cote D'ivoire (ci), China (cn), Egypt (eg), Israel (il), India (in), Italy(it), Montenegro(me), Portugal (pt) and Singapore (sg), and provide a written report in response; and
B. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
C. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-19

Dot GLOBAL Domain Registry LimitedNo
globoptView Comments
2015-11-30
2015-11-30View Mitigation

globo Mitigation

By Globo Comunicação e Participações SA

.globo is an exclusive-use TLD for the Globo media conglomerate, based in Brazil.

Globo Comunicações e Participações SA[Globo], for the .globo gTLD[TLD], has applied for and been granted an exemption to the registry operator code of conduct under Specification 9 to the Registry Agreement. This code of conduct exemption already contractually requires that [Globo] will apply measures which, by their very nature, avoid confusion with the corresponding country code,
namely the following:
• Developing and implementing a closed registration policy for .globo that requires that all domain names in the TLD be registered and used by Registry Operator and its affiliates;
• Clearly publishing this registration policy on Registry Operator’s homepage for .globo at http://nic.globo; and
• Enforcing of this registration policy and ensuring continued compliance, including through annual recertification of .globo’s
qualification for an exemption to the Registry Operator Code of Conduct.
This publicly available registration and usage policy prevent governments from registering domains in the .globo TLD.
It clearly designates to the public that .globo is a proprietary space in which all second-level domains in the TLD are and will be operated by [Globo] and not a government, a ccTLD or a reference to a country.


2016-04-22

Globo Comunicação e Participações SANo
goldptView Comments
2015-11-30
2015-11-30View Mitigation

gold Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

goldpoint Mitigation

By YODOBASHI CAMERA CO.,LTD.

2 Letter Codes Mitigation Plan for YODOBASHI TLDs
(.yodobashi .goldpoint)

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

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

・Clearly publishing this registration policy on Registry Operator`s homepage for the YODOBASHI TLDs at “nic.yodobashi”, and “nic.goldpoint”.

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

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

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

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


2016-04-25

YODOBASHI CAMERA CO.,LTD.Yes
golfptView Comments
2015-11-30
2015-11-30View Mitigation

golf Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

goodyear Mitigation

By The Goodyear Tire & Rubber Company

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


2016-04-21

The Goodyear Tire & Rubber CompanyYes
googleptView Comments
2015-11-30
2015-11-30View Mitigation

google Mitigation

By Charleston Road Registry Inc. (d/b/a Google Registry)

Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes.


View Documents
2016-04-22

Charleston Road Registry Inc. (d/b/a Google Registry)Yes
gopptView Comments
2015-11-30
2015-11-30No
graphicsptView Comments
2015-11-30
2015-11-30View Mitigation

graphics Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

gratis Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

gripe Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

gucci Mitigation

By Guccio Gucci S.p.a.

.GUCCI TLD is a closed Brand new gTLD operated by Guccio Gucci S.p.a.

Protections:

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

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

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


2016-04-20

Guccio Gucci S.p.a.Yes
guideptView Comments
2015-11-30
2015-11-30View Mitigation

guide Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
guitarsptView Comments
2015-11-30
2015-11-30No
guruptView Comments
2015-11-30
2015-11-30View Mitigation

guru Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

hamburg Mitigation

By Hamburg Top-Level-Domain GmbH

Proposed Measures to Avoid Confusion within the Community-based GeoTLD .HAMBURG for su, ru, uk, it, gb, ac, gi, tc, sh, ms, ky, io, bm, fk, ng, kr, il, sg, hk, pn, gs, tw, vn, ln, in, pt

“.HAMBURG is the top-level domain of the Community of Hamburg in the Internet. The local domain names available with the .HAMBURG top-level domain are concise and create an identity for citizens, companies and institutions. Those providing and looking for information, goods and services can thus intuitively come together. The .HAMBURG domain names strengthen the feeling of community amongst Hamburgers, improve communication and make interaction easier, thus providing a stimulus for innovation and development. Both for Hamburgers and for non-Hamburgers, Hamburg becomes more attractive as a place to visit, as a commercial location and as a place to live.”

Protections

To address the confusion concerns cited by the governments regarding the use of the second-level domains cited above in the .HAMBURG, the Registry Operator Hamburg Top-Level-Domain GmbH has implemented a restricted registration policy for .HAMBURG that mitigates the potential confusion. To these ends, Registry Operator commits to the following (as mentioned in its application at https://gtldresult.icann.org/application-result/applicationstatus/applicationdetails:downloadapplication/1351?t:ac=1351):

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

Eligibility Requirements: .HAMBURG is intended to serve the community of the Hamburgers in general, the group of eligible registrants is limited. Exclusively eligible to register a domain name under the top-level domain .HAMBURG is any natural person, legal person, organization or association of persons, if they can demonstrate that they have an economic, cultural, historical, social or any other connection to the metropolitan area of Hamburg, verifiable by

- their residence or second home, office or place of business, a branch or permanent establishment in the metropolitan area of Hamburg, or
- a contact listed in the Whois database with a domicile in the metropolitan area of Hamburg, or
- other appropriate proof e.g. the certification by an employer to enroll at a school or college, or birth certificate.

With the registration of a .HAMBURG domain name each registrant implicitly signs the registration policies and agrees with the fact that he acknowledges compliance with the registration guidelines. A review of whether the applicant meets the required eligibility, does not take place regularly on the date of registration, however, anyone can check compliance with the registration requirements by initiating an extrajudicial dispute resolution procedure.

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

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

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

Legal Safeguards, Enforcement and continued Compliance: This designation of .HAMBURG to the .HAMBURG Community will be enforced by specific language in the Registry-Registrar-Agreement that holds gTLD registrars responsible to include the restrictions as outlined above in respective agreements with their gTLD registrants.

The Registry Operator will, from time to time in its sole discretion or upon evidence or advice, but at least once a year, conduct continuing or recurring audits of domain names registered to ensure continued compliance with these requirements. Failure to comply will result in a notice providing a timeframe to comply. Non-compliance following such a notice period may result in take-down of the relevant domain name, at the discretion of the Registry. The Registry is entitled to lock, cancel, initiate the gTLD-deletion cycle or transfer domain names that do not meet the registration criteria if certain circumstances appear.

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

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


2016-04-25

Hamburg Top-Level-Domain GmbHNo
hausptView Comments
2015-11-30
2015-11-30View Mitigation

haus Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

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

healthcare Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
helpptView Comments
2015-11-30
2015-11-30No
hermesptView Comments
2015-11-30
2015-11-30View Mitigation

hermes Mitigation

By HERMES INTERNATIONAL

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

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


2016-04-11

HERMES INTERNATIONALYes
hiphopptView Comments
2015-11-30
2015-11-30No
hockeyptView Comments
2015-11-30
2015-11-30View Mitigation

hockey Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

holdings Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

holiday Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No

pt Comments

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

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

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."