.army

From ICANNWiki
Revision as of 05:53, 23 December 2012 by Vivian (talk | contribs)
Jump to navigation Jump to search
Status: Proposed
Manager: Demand Media
Registry Provider: Demand Media
Type: Generic
Category: Government
Priority #: 665 - Demand Media (United TLD Holdco Ltd.)

More information: NTLDStatsLogo.png

.army is a proposed TLD in ICANN's New gTLD Program. The applicant is Demand Media (United TLD Holdco Ltd.).[1]

GAC Early Warnings[edit | edit source]

The application was issued three GAC Early Warnings, from The United States, Australia, and India. The warning system is noted as a strong recommendation on behalf of national governments to the ICANN Board that a given TLD application should be denied as it stands. Applicants are encouraged to work with objecting GAC members.[2]

The United States representative simply notes that the name is confusingly similar to an official government agency;[3] The Australian warning notes that this similarity will not only confuse end-users but negatively impact national armed forces services;[4] India adds that this will cause irreparable harm to the safety and security of the nation.[5] All three governments recommend that Demand Media withdraw the application. Similar warnings were made to their other military focused applications, such as .navy and .airforce.

Registration Policies[edit | edit source]

Excerpted from response to Question 18:
United TLD will be inclusive in its registration policies for this broad and generic TLD. We will not limit registrant eligibility for second-level registrations and will provide registration services to all legitimate registrants. However, we may elect to reserve and hold back certain strings from second-level registration at the time we launch the TLD.

We will not tolerate illegal activity in this TLD and will have strict policies and enforcement that provide for takedown or other appropriate forms of remedy. United TLD will adhere to and uphold all ICANN-required registration policies and comply with the requirements of the registration policy portion of the Registry Agreement."[6]

References[edit | edit source]