.watch: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = | |logo = | ||
|status = | |status = Contract Signed | ||
|manager = | |manager = | ||
|country = | |country = | ||
| Line 20: | Line 20: | ||
===Application Details=== | ===Application Details=== | ||
Many of [[Donuts]]' applications, including this one, seem to have been applied for using the same boiler-plate application in which the TLD is defined as a means of providing greater expression on the Internet and will be an open TLD without pre-registration policies. It notes its plans to adhere with all registration policies required by ICANN and its intent to have remediation and takedown policies clearly defined to fit within these requirements. Pre-registration verification will not be used and this as defined as causing "more harm than benefit by denying domain access to legitimate registrants." They intend to control abuse through "extensive user and rights protections."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/887 ApplicationDetails, gTLDresult.ICANN.org]Retrieved 12 Dec 2012</ref> | Many of [[Donuts]]' applications, including this one, seem to have been applied for using the same boiler-plate application in which the TLD is defined as a means of providing greater expression on the Internet and will be an open TLD without pre-registration policies. It notes its plans to adhere with all registration policies required by ICANN and its intent to have remediation and takedown policies clearly defined to fit within these requirements. Pre-registration verification will not be used and this as defined as causing "more harm than benefit by denying domain access to legitimate registrants." They intend to control abuse through "extensive user and rights protections."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/887 ApplicationDetails, gTLDresult.ICANN.org]Retrieved 12 Dec 2012</ref> | ||
On 14 November 2013, [[Donuts]] received a [[Registry Agreement]] signed by [[ICANN]] for .watch after passing all the required processes needed to become a [[Registry Operator]] for the string.<ref>[http://www.icann.org/en/about/agreements/registries Registry Agreements, ICANN.org] Retrieved 20 Nov 2013</ref> | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
| Line 25: | Line 28: | ||
[[Category:TLD]] | [[Category:TLD]] | ||
[[Category:Technology New gTLDs|watch]] | [[Category:Technology New gTLDs|watch]] | ||
[[Category:TLDs with Registry Agreements|watch]] | |||
Revision as of 17:16, 20 November 2013
| Status: | Contract Signed |
| Registry Provider: | Demand Media |
| Type: | Generic |
| Category: | Technology |
| PIC Submitted: | Download Here |
| Priority #: | 1377 - Donuts (Sand Shadow, LLC) |
More information: 
| |
.watch is a proposed TLD in ICANN's New gTLD Program. The applicant is Donuts (Sand Shadow, LLC).[1] Their is an applicant for the plural, .watches.
Application Details[edit | edit source]
Many of Donuts' applications, including this one, seem to have been applied for using the same boiler-plate application in which the TLD is defined as a means of providing greater expression on the Internet and will be an open TLD without pre-registration policies. It notes its plans to adhere with all registration policies required by ICANN and its intent to have remediation and takedown policies clearly defined to fit within these requirements. Pre-registration verification will not be used and this as defined as causing "more harm than benefit by denying domain access to legitimate registrants." They intend to control abuse through "extensive user and rights protections."[2]
On 14 November 2013, Donuts received a Registry Agreement signed by ICANN for .watch after passing all the required processes needed to become a Registry Operator for the string.[3]
References[edit | edit source]
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ ApplicationDetails, gTLDresult.ICANN.orgRetrieved 12 Dec 2012
- ↑ Registry Agreements, ICANN.org Retrieved 20 Nov 2013