Difference between revisions of ".navy"
m |
|||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = | |logo = | ||
| − | |status = | + | |status = Delegated |
|manager = | |manager = | ||
|country = | |country = | ||
|language = | |language = | ||
|translation = | |translation = | ||
| − | |registryprovider = | + | |registryprovider =[[Demand Media]] |
|registrations = | |registrations = | ||
|date = | |date = | ||
| Line 12: | Line 12: | ||
|category = [[:Category:Government New gTLDs|Government]] | |category = [[:Category:Government New gTLDs|Government]] | ||
|community = | |community = | ||
| + | |PIC = [https://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1124 Download Here] | ||
| + | |priority = 912 - [[Demand Media]] ([[United TLD Holdco Ltd.]]) | ||
|keypeople = | |keypeople = | ||
}} | }} | ||
| − | '''.navy''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[Demand Media]] ([[United TLD Holdco Ltd.]]).<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref> | + | '''.navy''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[Rightside]]/[[Demand Media]] ([[United TLD Holdco Ltd.]]).<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref> Their application succeeded and was delegated to the [[Root Zone]] on 4 June 2014.<ref name="delegation">[http://newgtlds.icann.org/en/program-status/delegated-strings Delegated Strings, ICANN.org] Retrieved 11 July 2014</ref> |
===GAC Early Warnings=== | ===GAC Early Warnings=== | ||
| Line 21: | Line 23: | ||
The United States representative simply notes that the name is confusingly similar to an official government agency;<ref>[https://gacweb.icann.org/download/attachments/22938690/Navy-US-53893.pdf?version=1&modificationDate=1353431037000 Navy US, GACweb.ICANN.org]Retrieved 25 Nov 2012</ref> The Australian warning notes that this similarity will not only confuse end-users but negatively impact national armed forces services;<ref>[https://gacweb.icann.org/download/attachments/22938690/Navy-AU-53893.pdf?version=1&modificationDate=1353451381000 Navy AU, GACweb.ICANN.org]</ref> India adds that this will cause irreparable harm to the safety and security of the nation.<ref>[https://gacweb.icann.org/download/attachments/22938690/Navy-IN-53893.pdf?version=1&modificationDate=1353469107000 Navy IN, GACweb.ICANN.org]</ref> All three governments recommend that [[Demand Media]] withdraw the application. Similar warnings were made to their other military focused applications, [[.airforce]] and [[.army]]. | The United States representative simply notes that the name is confusingly similar to an official government agency;<ref>[https://gacweb.icann.org/download/attachments/22938690/Navy-US-53893.pdf?version=1&modificationDate=1353431037000 Navy US, GACweb.ICANN.org]Retrieved 25 Nov 2012</ref> The Australian warning notes that this similarity will not only confuse end-users but negatively impact national armed forces services;<ref>[https://gacweb.icann.org/download/attachments/22938690/Navy-AU-53893.pdf?version=1&modificationDate=1353451381000 Navy AU, GACweb.ICANN.org]</ref> India adds that this will cause irreparable harm to the safety and security of the nation.<ref>[https://gacweb.icann.org/download/attachments/22938690/Navy-IN-53893.pdf?version=1&modificationDate=1353469107000 Navy IN, GACweb.ICANN.org]</ref> All three governments recommend that [[Demand Media]] withdraw the application. Similar warnings were made to their other military focused applications, [[.airforce]] and [[.army]]. | ||
| + | ==Application Details== | ||
| + | The following is excerpted from the applicant's response to question #18: | ||
| + | |||
| + | "For thousands of years, devoted men and women have served their countries in the naval forces branch of military service. Global in scope, the millions of individuals who share a bond created by service in the navy are a large and passionate group. The mission and purpose of the .navy TLD is to establish an easily recognized and accessible namespace for the universe of naval veterans, active duty personnel, family members, and supportive organizations and civilians. | ||
| + | |||
| + | The .navy TLD is proposed by United TLD Holdco Ltd. (“United TLD”), a well-funded company established by highly experienced domain industry executives for the express purpose of securing the rights to operate a portfolio of TLDs that increase choice, expression, affinity and relevance for millions of consumers, businesses and other organizations on the web. | ||
| + | |||
| + | nited 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."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1124 Application Download, gTLDresult.ICANN.org] Retrieved 21 Feb 2013</ref> | ||
| + | |||
| + | ==Contract Signed== | ||
| + | On 6 March 2014 Rightside received a [[Registry Agreement]] signed by ICANN for .navy after passing all the required processes needed to become a Registry Operator for the string.<ref>[http://www.icann.org/en/about/agreements/registries-date Registry Agreements, ICANN.org] Retrieved 11 July 2014</ref> | ||
| + | |||
| + | ==Delegation and Availability== | ||
| + | .navy was delegated to the Root Zone of the [[DNS]] on 4 June 2014, completing the successful application for the string.<ref name="delegation"></ref> | ||
==References== | ==References== | ||
| Line 27: | Line 45: | ||
[[Category:TLD]] | [[Category:TLD]] | ||
[[Category:Government New gTLDs|navy]] | [[Category:Government New gTLDs|navy]] | ||
| + | [[Category:TLDs with Registry Agreements|navy]] | ||
Latest revision as of 21:26, 11 July 2014
| Status: | Delegated |
| Registry Provider: | Demand Media |
| Type: | Generic |
| Category: | Government |
| PIC Submitted: | Download Here |
| Priority #: | 912 - Demand Media (United TLD Holdco Ltd.) |
More information: 
| |
.navy is a proposed TLD in ICANN's New gTLD Program. The applicant 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, .airforce and .army.
Application Details
The following is excerpted from the applicant's response to question #18:
"For thousands of years, devoted men and women have served their countries in the naval forces branch of military service. Global in scope, the millions of individuals who share a bond created by service in the navy are a large and passionate group. The mission and purpose of the .navy TLD is to establish an easily recognized and accessible namespace for the universe of naval veterans, active duty personnel, family members, and supportive organizations and civilians.
The .navy TLD is proposed by United TLD Holdco Ltd. (“United TLD”), a well-funded company established by highly experienced domain industry executives for the express purpose of securing the rights to operate a portfolio of TLDs that increase choice, expression, affinity and relevance for millions of consumers, businesses and other organizations on the web.
nited 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."[7]
Contract Signed
On 6 March 2014 Rightside received a Registry Agreement signed by ICANN for .navy after passing all the required processes needed to become a Registry Operator for the string.[8]
Delegation and Availability
.navy was delegated to the Root Zone of the DNS on 4 June 2014, completing the successful application for the string.[2]
References
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ 2.0 2.1 Delegated Strings, ICANN.org Retrieved 11 July 2014
- ↑ GAC Early Warning, NewgTLDS.ICANN.org Retrieved 25 Nov 2012
- ↑ Navy US, GACweb.ICANN.orgRetrieved 25 Nov 2012
- ↑ Navy AU, GACweb.ICANN.org
- ↑ Navy IN, GACweb.ICANN.org
- ↑ Application Download, gTLDresult.ICANN.org Retrieved 21 Feb 2013
- ↑ Registry Agreements, ICANN.org Retrieved 11 July 2014