.airforce: Difference between revisions
No edit summary |
+delegation |
||
Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = | |logo = | ||
|status = | |status = Delegated | ||
|manager = | |manager = | ||
|country = | |country = | ||
Line 17: | Line 17: | ||
}} | }} | ||
'''.airforce''' is a | '''.airforce''' is a [[gTLD]] that was proposed in [[ICANN]]'s [[New gTLD Program]]. The applicant and now [[Registry Operator]] 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> Their application succeeded and was delegated to the [[Root Zone]] on 30 April 2014.<ref name="delegation">[http://newgtlds.icann.org/en/program-status/delegated-strings Delegated Strings, ICANN.org] Retrieved 30 May 2014</ref> | ||
==Background== | |||
===GAC Early Warnings=== | ===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.<ref>[http://newgtlds.icann.org/en/applicants/gac-early-warning GAC Early Warning, NewgTLDS.ICANN.org] Retrieved 25 Nov 2012</ref> | 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.<ref>[http://newgtlds.icann.org/en/applicants/gac-early-warning GAC Early Warning, NewgTLDS.ICANN.org] Retrieved 25 Nov 2012</ref> | ||
Line 23: | Line 25: | ||
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/Airforce-US-29190.pdf?version=1&modificationDate=1353430950000 Airforce 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/Airforce-AU-29190.pdf?version=1&modificationDate=1353451356000 Airforce 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/Airforce-IN-29190.pdf?version=1&modificationDate=1353469245000 Airforce 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, such as [[.navy]] 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/Airforce-US-29190.pdf?version=1&modificationDate=1353430950000 Airforce 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/Airforce-AU-29190.pdf?version=1&modificationDate=1353451356000 Airforce 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/Airforce-IN-29190.pdf?version=1&modificationDate=1353469245000 Airforce 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, such as [[.navy]] and [[.army]]. | ||
==Application Details== | ===Application Details=== | ||
The following is an excerpt from the applicant's response to question #18: | The following is an excerpt from the applicant's response to question #18: | ||
Line 29: | Line 31: | ||
The .airforce 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. | The .airforce 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. | ||
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. | 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. "<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1109 Application Download, gTLDresult.ICANN.org] Retrieved 16 Feb 2013</ref> | 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/1109 Application Download, gTLDresult.ICANN.org] Retrieved 16 Feb 2013</ref> | ||
==Contract Signed== | |||
On 6 March 2014 Donuts received a [[Registry Agreement]] signed by ICANN for .airforce 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 30 May 2014</ref> | |||
==Delegation and Availability== | |||
.airforce was delegated to the Root Zone of the [[DNS]] on 30 April, 2014, completing the successful application for the string.<ref name="delegation"></ref> | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
Line 40: | Line 47: | ||
[[Category:TLD]] | [[Category:TLD]] | ||
[[Category:Government New gTLDs|airforce]] | [[Category:Government New gTLDs|airforce]] | ||
[[Category:TLDs with Registry Agreements|airforce]] |
Revision as of 22:11, 30 May 2014
Status: | Delegated |
Type: | Generic |
Category: | Government |
PIC Submitted: | Download Here |
Priority #: | 339 - Demand Media (United TLD Holdco Ltd.) |
More information: |
.airforce is a gTLD that was proposed in ICANN's New gTLD Program. The applicant and now Registry Operator is Demand Media (United TLD Holdco Ltd.).[1] Their application succeeded and was delegated to the Root Zone on 30 April 2014.[2]
Background[edit | edit source]
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.[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 .army.
Application Details[edit | edit source]
The following is an excerpt from the applicant's response to question #18:
"For nearly one hundred years, devoted men and women have served their countries in the esteemed air force branch of military service. Global in scope, the millions of individuals who share a bond created by service in the air force are a large and passionate group. The mission and purpose of the .airforce TLD is to establish an easily recognized and accessible namespace for the universe of air force veterans, active duty personnel, family members and supportive organizations and civilians.
The .airforce 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.
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. "[7]
Contract Signed[edit | edit source]
On 6 March 2014 Donuts received a Registry Agreement signed by ICANN for .airforce after passing all the required processes needed to become a Registry Operator for the string.[8]
Delegation and Availability[edit | edit source]
.airforce was delegated to the Root Zone of the DNS on 30 April, 2014, completing the successful application for the string.[2]
References[edit | edit source]
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ 2.0 2.1 Delegated Strings, ICANN.org Retrieved 30 May 2014
- ↑ GAC Early Warning, NewgTLDS.ICANN.org Retrieved 25 Nov 2012
- ↑ Airforce US, GACweb.ICANN.orgRetrieved 25 Nov 2012
- ↑ Airforce AU, GACweb.ICANN.org
- ↑ Airforce IN, GACweb.ICANN.org
- ↑ Application Download, gTLDresult.ICANN.org Retrieved 16 Feb 2013
- ↑ Registry Agreements, ICANN.org Retrieved 30 May 2014