.army

From ICANNWiki
Jump to: navigation, search
Status: Delegated
Manager: Demand Media
Registry Provider: Demand Media
Registry: Rightside
Registry Backend: Donuts
Date Implemented: 04 June 2014
Type: Generic
Category: Government
PIC Submitted: Download Here
nTLDStats
Registrations: 1,986
Parked Domains: 1,275
Parked Domain %: 64.2 %
Important Dates
Delegation: 04 June 2014
General Availability: 22 October 2014

More Information: NTLDStatsLogo.png

.army is a delegated TLD in ICANN's New gTLD Program. The TLD's manager and registry is Rightside/Demand Media (United TLD Holdco Ltd.).[1] Their application succeeded and was delegated to the Root Zone on 4 June 2014.[2]

GAC Early Warnings

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.[3]

The United States representative simply notes that the name is confusingly similar to an official government agency;[4] The Australian warning notes that this similarity will not only confuse end-users but negatively impact national armed forces services;[5] India adds that this will cause irreparable harm to the safety and security of the nation.[6] 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.

Independent Objector

The Independent Objector (IO) is a non-partisan, contracted appointee whose role was mandated by the applicant guidebook for ICANN's New gTLD Program, and who is responsible for officially objecting to new gTLDs that are dangerous to the public good. This process also involves reviewing "controversial applications," those that have received significant public comments, and investigating whether a public need for objection is provided for tin these comments. Thus, the Independent Objector issued a preliminary report on .army, where he also mentions .navy and .airforce, where he notes that his initial assessment led him to believe that the TLDs could mislead the end-users that the domain is associated with a national army. He notes that his final assessment changed sides, and he was reassured by the applicant's intent to create a safe TLD, when include provision for "“very broad array of protection mechanisms will insure that these gTLDs are safe for consumers and will not be abused”. These guarantees include, inter alia, “remediation of inaccurate WhoIs data, including suspending a domain name, if warranted”, “rigorous Terms of Use that prohibit illegal or abusive activity”, “limitations on domain name proxy and privacy services”, “published policies and procedures that define abusive activity”, and “a new Domain Protected Marks List (DPML) to insure greater trademark protection for trademark holders”. On this last point, the applicant made a commitment that they “will work with governments around the globe to insure that any government related trademarks blocked from use”."[7]

Registration Policies

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."[8]

Contract Signed

On 6 March 2014 Rightside received a Registry Agreement signed by ICANN for .army after passing all the required processes needed to become a Registry Operator for the string.[9]

Delegation and Availability

.army was delegated to the Root Zone of the DNS on 4 June 2014, completing the successful application for the string.[2]

References