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

abogado 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
abogadogsView Comments
2015-12-02
2015-12-02View Mitigation

abogado 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
abogadovnView Comments
2015-12-02
2015-12-02View Mitigation

abogado 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
abogadopnView Comments
2015-12-02
2015-12-02View Mitigation

abogado 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
abogadobmView Comments
2015-12-02
2015-12-08View Mitigation

abogado 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
abogadoioView Comments
2015-12-02
2015-12-08View Mitigation

abogado 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
abogadokyView Comments
2015-12-02
2015-12-08View Mitigation

abogado 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
abogadomsView Comments
2015-12-02
2015-12-08View Mitigation

abogado 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
abogadoshView Comments
2015-12-02
2015-12-08View Mitigation

abogado 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
abogadotcView Comments
2015-12-02
2015-12-08View Mitigation

abogado 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
abogadogiView Comments
2015-12-02
2015-12-08View Mitigation

abogado 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
abogadoacView Comments
2015-12-02
2015-12-08View Mitigation

abogado 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
abogadohkView Comments
2015-12-03
2015-12-03View Mitigation

abogado 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
abogadoilView Comments
2015-12-03
2015-12-03View Mitigation

abogado 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
abogadokrView Comments
2015-12-04
2015-12-04View Mitigation

abogado 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
abogadongView Comments
2015-12-04
2015-12-05View Mitigation

abogado 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
abogadoruView Comments
2015-12-07
2016-08-15View Mitigation

abogado 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
abogadosuView Comments
2015-12-07
2016-08-15View Mitigation

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

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

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

abogado 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
academyinView Comments
2015-12-01
2015-12-01View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academysgView Comments
2015-11-11
2015-12-03View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academylnView Comments
2015-12-01
2015-12-01View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyfkView Comments
2015-12-02
2015-12-08View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academygsView Comments
2015-12-02
2015-12-02View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyvnView Comments
2015-12-02
2015-12-02View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academypnView Comments
2015-12-02
2015-12-02View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academybmView Comments
2015-12-02
2015-12-08View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyioView Comments
2015-12-02
2015-12-08View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academykyView Comments
2015-12-02
2015-12-08View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academymsView Comments
2015-12-02
2015-12-08View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyshView Comments
2015-12-02
2015-12-08View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academytcView Comments
2015-12-02
2015-12-08View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academygiView Comments
2015-12-02
2015-12-08View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyacView Comments
2015-12-02
2015-12-08View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyilView Comments
2015-12-03
2015-12-03View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academykrView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyngView Comments
2015-12-04
2015-12-05View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyruView Comments
2015-12-07
2016-08-15View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyfrView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academygpView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academywfView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyreView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academypmView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academymfView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academysuView Comments
2015-12-07
2016-08-15View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academypfView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyncView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academymqView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyytView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academytfView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academygfView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
academyblView Comments
2015-12-04
2015-12-04View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
accenturetwView Comments
2015-10-14
2015-12-02View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accentureinView Comments
2015-12-01
2015-12-01View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturesgView Comments
2015-11-11
2015-12-03View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturelnView Comments
2015-12-01
2015-12-01View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturefkView Comments
2015-12-02
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accentureptView Comments
2015-11-30
2015-11-30View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturegsView Comments
2015-12-02
2015-12-02View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturevnView Comments
2015-12-02
2015-12-02View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturepnView Comments
2015-12-02
2015-12-02View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturebmView Comments
2015-12-02
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accentureioView Comments
2015-12-02
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturekyView Comments
2015-12-02
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturemsView Comments
2015-12-02
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accentureshView Comments
2015-12-02
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturetcView Comments
2015-12-02
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturegiView Comments
2015-12-02
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accentureacView Comments
2015-12-02
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accentureilView Comments
2015-12-03
2015-12-03View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturekrView Comments
2015-12-04
2015-12-04View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturengView Comments
2015-12-04
2015-12-05View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accentureruView Comments
2015-12-07
2016-08-15View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturesuView Comments
2015-12-07
2016-08-15View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accenturegbView Comments
2015-12-08
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accentureukView Comments
2015-12-08
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accentureitView Comments
2015-12-08
2015-12-08View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accountantinView Comments
2015-12-01
2015-12-01View Mitigation

accountant 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
accountantsgView Comments
2015-11-11
2015-12-03View Mitigation

accountant 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
accountantlnView Comments
2015-12-01
2015-12-01View Mitigation

accountant 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
accountantfkView Comments
2015-12-02
2015-12-08View Mitigation

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

accountant 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
accountantgsView Comments
2015-12-02
2015-12-02View Mitigation

accountant 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
accountantvnView Comments
2015-12-02
2015-12-02View Mitigation

accountant 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
accountantpnView Comments
2015-12-02
2015-12-02View Mitigation

accountant 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
accountantbmView Comments
2015-12-02
2015-12-08View Mitigation

accountant 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
accountantioView Comments
2015-12-02
2015-12-08View Mitigation

accountant 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
accountantkyView Comments
2015-12-02
2015-12-08View Mitigation

accountant 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
accountantmsView Comments
2015-12-02
2015-12-08View Mitigation

accountant 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
accountantshView Comments
2015-12-02
2015-12-08View Mitigation

accountant 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
accountanttcView Comments
2015-12-02
2015-12-08View Mitigation

accountant 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
accountantgiView Comments
2015-12-02
2015-12-08View Mitigation

accountant 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
accountantacView Comments
2015-12-02
2015-12-08View Mitigation

accountant 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
accountantilView Comments
2015-12-03
2015-12-03View Mitigation

accountant 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

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.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

The administration in South Georgia and the South Sandwich Islands (UK overseas territory) have no objection to the use of two character domains which coincide with their ccTLD at the second level, and do not wish to be notified of such requests by registries.

vn Comments

By Le Thi Ngoc Mo, Deputy Director General of Vietnam Telecommunications Authority (VNTA), Ministry of Information and Communication (MIC)

Dear ICANN,
“vn” is the country code for Viet Nam. The release of the two-character ".vn" label at the second-level under new gTLDs would create confusion with the ccTLD ".vn". On behalf of Viet Nam government, I would like to submit an objection to the release of the “.vn” at the second level under all new gTLDs.
Viet Nam is seting up the accurate criteria for releasing this two character at the second level domain names under new gTLDs . This is sensitive issue for government so it is taking some time for government to consider.
To reiterate, our objections are applied to all new gTLDs who have requested or will be requesting for the release of “.vn” at the second level until we set up the accurate criteria for releasing and send notice to ICANN.
Thank you and best regards,

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

The administration in the Pitcairn Islands (UK overseas territory) have no objection to the use of two character domains which coincide with their ccTLD at the second level, and do not wish to be notified of such requests by registries.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Bermuda (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of British Indian Ocean Territory wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Cayman Islands (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Montserrat (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Saint Helena (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of the Turks and Caicos Islands (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Gibraltar (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion and any unintended consequences, the administration of Ascension Island (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

hk Comments

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

In response to ICANN’s request for clarification of 6 October 2015 on how the release of two-character country codes as the second level domain (SLD) in new gTLDs would create confusion, we would like to reiterate our views on 24 March and 27 May 2015, which have stated the confusion and rationale related to the release of "hk" as SLD on the following two categories of new gTLDs, that they shall NOT be released for ALL requests:

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

For easy reference, texts of our previous submitted views are reproduced below:

HKSARG’s VIEWS ON 24 MARCH 2015

‘I am writing to express the view of Hong Kong Special Administrative Region Government on the release of "hk" as the second level domain (SLD) in new gTLDs.

Our ccTLD, .hk, is commonly understood as the abbreviated name of Hong Kong. HK means Hong Kong to the Internet community globally and locally. The use of "hk" as SLD in new gTLDs would give the perception that the domain names in question belong to or are related to Hong Kong and the Hong Kong community.

(I) gTLDs for Regulated Sectors

As pointed out by GAC, gTLD strings that are linked to regulated or professional sectors should operate in a way that is consistent with applicable laws. These gTLD strings or Category 1 gTLDs are likely to invoke a level of implied trust from consumers, and carry higher levels of risk associated with consumer harm. GAC advised ICANN to apply safeguards (GAC Safeguard Advice 1 - 5) to these strings. In addition, for a limited subset of the Category 1 gTLDs that are associated with market sectors which have clear and/or regulated entry requirements (i.e. highly-regulated sectors), additional safeguards (GAC Safeguard Advice 6 - 8) should apply.

In this context, for the use of "hk" as SLD in new gTLDs associated with (1) Highly-regulated Sectors/Closed Entry Requirements in Multiple Jurisdictions and (2) Inherently Governmental Functions as set out in the ICANN NGPC Resolution No. 2014.02.05.NG01, The Government of Hong Kong Special Administrative Region (HKSAR Government) requests that :

(a) Registry operator should consult HKSAR Government on any request for domain name registration;
(b) The registry operator should implement measures in line with GAC safeguards 6-8 on verification and validation of credentials of registrants;
(c) Registry operator should consult HKSAR Government on any complaint expressing doubt with regard to authenticity of licences or credentials.

(II) Geographic gTLDs

For geographic gTLDs which are names of cities, countries or regions, or have strong geographic connotation, putting "hk" at the second level may cause confusion or perception of subordination. Among the current requests posted from 23 February 2015 to 19 March 2015, these gTLDs include: .amsterdam, .bayern, .berlin, .budapest, .capital, .city, .country, .frl, .hamburg, .kyoto, .london, .miami, .nagoya, .nrw, .nyc, .osaka, .taipei, .tirol, .tokyo, .town, .wien, .world, .yokohama, and .zuerich.

In this context, HKSAR Government requests that Registry operator should consult HKSAR Government on any request for domain name registration on such gTLDs.’


HKSARG’s VIEWS ON 27 MAY 2015

‘For the current requests of R000375 to R000466 and ALL FUTURE requests, “hk” shall NOT be included in ICANN's Authorization for Release of Two-character Letter/Letter ASCII Labels at the Second Level and shall NOT be released as SLD for -

(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 NAMELY .melbourne, .saarland, and .sydney in the current requests.'


Best Regards,
Dominic Kwong
Alternate GAC Representative of Hong Kong Special Administrative Region, China

il Comments

By Dr. Amir Adler, Chief Scientist, Ministry of Communications, Ministry of Communications

Request that “il” will be assigned under these TLDs only to a person, entity or
corporation proposed or accepted by the Israeli Government, due to the following concerns:

(1) Unproper or offensive utilization in conjuction with ".il".

(2) Missleading association with the State of Israel.

(3) Interference, or violation of the rights of domestic businesses and organizations.

kr Comments

By Seonyoung Jeong, Assistant Director, Internet Policy Division, Internet Convergence Policy Bureau Ministry of Science, ICT and Future Planning

KR is the country code for the republic of Korea. On behalf of the .kr registry and Korean government, we would like to submit a temporary objection to the release of the '.kr' at the second level under all new gTLDs UNTIL we, Korea government, set up the accurate criteria for releasing. This is sensitive issue for government so it is taking some time for government to consider.
To reiterate, our objections are applied to all new gTLDs who have requested or will be requesting for the release of .kr at the second level until we set up the accurate criteria for releasing. Thank you.

ng Comments

By Nkiru Ebenmelu, GAC Rep, Nigerian Communications Commission

Nigeria does not support the release of Two-Character ASCII Labels ".ng" or the use of "NIGERIA", in the context of any/all of the gTLD(s) at the second level. This should apply to all current and future requests. It is against Nigerian law and strictly prohibited to use the word "Nigeria" or code representing Nigeria without proper authorization by the Government. This assists the Country forestall the abuse and misuse of reserved names associated with the Government; the release would be a breach of our laws. We also wish to inform you that Nigeria reserves the right of authorization for use of “NGR” and “NGA”. As these are also reserved for use by Nigeria. (ISO 3166). We will appreciate it if we are informed of the decision(s) taken.

ru Comments

By Yulia Elanskaya, Deputy Director of International Cooperation Department, Ministry of Telecom and Mass Communications of the Russian Federation

Russia objects the release of Two-Character combination “.ru” at the second level under any kind/all gTLD.
We are concerned that the deceptive similarity of these two-letter combinations with country codes ccTLDs creates the risk of confusion and misleading of Internet users.
This requirement should apply to all current and future requests.

su Comments

By Yulia Elanskaya, Deputy Director of International Cooperation Department, Ministry of Telecom and Mass Communications of the Russian Federation

Russia objects the release of Two-Character combination “.su” at the second level under any kind/all gTLD.
We are concerned that the deceptive similarity of these two-letter combinations with country codes ccTLDs creates the risk of confusion and misleading of Internet users.
This requirement should apply to all current and future requests.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

The UK government notes that gb is a reserved ccTLD string. In order to avoid the potential for confusion, any unintended consequences and consistency within the DNS, the UK requests that this two character code must not be delegated for use as a second-level domain.

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion, and any unintended consequences, the UK government wish to be notified of all registry requests to use the two characters of its country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

it Comments

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

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

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

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

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

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

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

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

Rita Forsi

in Comments

By Rahul Gosain, Director, Department of Electronics and Information Technology, Ministry of communication and Information Technology

India is not favouring the release of Two-Character ASCII labels "in", "1n" and deceptively similar as the ccTLD ".in" at the second level. ICANN is requested that India's objection on release of Two-character ASCII labels "in" and "1n" at the second level should apply to all current and future requests from new gTLD's

sg Comments

By Queh Ser Pheng, Deputy Director, Internet Resource Management, Policy & Competition Development Group, Infocomm Development Authority of Singapore

We hereby respectfully submit our comment regarding the release of letter/letter two-character labels as second level domains.

At this stage, we are unable to agree to the release of the two-character "sg" label at the second-level under gTLDs because of the concern that such use would create confusion with the ccTLD "sg" representing Singapore. Until further notice, this policy is to be applied to all gTLDs who have requested or will be requesting for the release of letter-letter two-character labels at the second level.

To elaborate further, we are open to considering the release of "sg" to registry operators who have robust framework in place to address concerns of government. We recognise there are legitimate and valid reasons for such use. However, we are of the view that it is prudent for ICANN to first put in place a holistic and robust framework before approvals can be given. More thoughts need to be given to the evaluation process and in particular the remedies available should a registry operator use the approved names in an undesirable manner. Besides possible confusion with the corresponding country code and/or country/territory name, we are also concerned with:

(a) The possible reputational harm if ".sg." is associated with illegal or objectionable content and/or manner-of-use; and

(b) The direct harm if ".sg." content or manner-of-use targets Singapore as a nation or Singapore entities (e.g., websites could masquerade as Singapore Government agencies).

ICANN's current policy focuses only on the "initial release" process. There needs to be considerations given to "post-release" issues. As such, the ICANN framework should include:

(a) A recourse for the government/country code manager to issue a notice to object to the content and/or manner-of-use that is misleading, questionable, objectionable or contrary to the country’s reputation and laws. There should be an effective and robust process acceptable by the government/country code manager for the registry operator to address the concern; and

(b) Provisions to require the registry operator to re-seek approval from government/country code manager should there be material changes in ownership or organisational control (for example merger with or acquisitions by another entity).

In addition, ICANN must be committed to take actions against the registry operator should they fail to comply with the framework (e.g. implement a process for country/territory to raise objections to ICANN and for ICANN to take appropriate remedial actions such as remove/delete/revoke affected names).

in Comments

By Rahul Gosain, Director, Department of Electronics and Information Technology, Ministry of communication and Information Technology

India is not favouring the release of Two-Character ASCII labels "ln" and "1n" and deceptively similar as the ccTLD ".in" at the second level. ICANN is requested that India's objection on release of Two-character ASCII labels "ln" and "1n" at the second level should apply to all current and future requests from new gTLD's

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

The administration of the Falkland Islands (UK overseas territory) have no objection to the use of two character domains which coincide with their ccTLD at the second level, and do not wish to be notified of such requests by registries.

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, domains, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

fr Comments

By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique

Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.

Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique

tw Comments

By Lin, Mao-Shong, Deputy Director, Ministry of Transportation and Communications

I’m writing hereby to submit Taiwan government’s comments on the release of the “tw” label under the New gTLDs.

We object to the release of “tw” as SLD under all the above-mentioned New gTLDs for their registration by the corresponding Registry operators. We reserve the right to change position in this regard in the future.

The rationale of our objections are below:
Since “tw” label is the country code for Taiwan, the use of “tw” as SLD under these diverse New gTLDs would create confusion or concerns at multiple levels on our part, which include, but not limited to, ”dwarfing national dignity”, “violation of public order or good social custom”, “affecting the rights of domestic enterprises”, and “being prone to produce perplexity to our disadvantage”.

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