.cooking: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = | |logo = | ||
|status = | |status = Contract Signed | ||
|manager = | |manager = | ||
|country = | |country = | ||
| Line 26: | Line 26: | ||
The .COOKING top-level domain will offer professional chefs and amateur cooks the opportunity to better connect with one another and share knowledge about cooking. For providers of cooking goods and services, .COOKING will provide a readily identifiable banner to help attract customers. | The .COOKING top-level domain will offer professional chefs and amateur cooks the opportunity to better connect with one another and share knowledge about cooking. For providers of cooking goods and services, .COOKING will provide a readily identifiable banner to help attract customers. | ||
.. | .. | ||
We specifically examined more restrictive registration policies, such as limiting registration to members of organizations with a specific tie to cooking. We rejected such limitations because they would interfere with .COOKING’s primary mission, purpose and goals--which is to encourage as many registrants as possible to associate themselves with cooking for any legal purpose. Factors that we took into account when considering a more restrictive registration policy included: | We specifically examined more restrictive registration policies, such as limiting registration to members of organizations with a specific tie to cooking. We rejected such limitations because they would interfere with .COOKING’s primary mission, purpose and goals--which is to encourage as many registrants as possible to associate themselves with cooking for any legal purpose. Factors that we took into account when considering a more restrictive registration policy included: | ||
| Line 34: | Line 32: | ||
With respect to protecting registrant privacy and confidential information, we will comply with all applicable ICANN rules, including Whois policies, and all applicable laws, rules and regulations of appropriate jurisdictions. Registrant privacy and use of confidential information are set forth in our Privacy & Whois Policy. Information concerning updates and changes to the Privacy & Whois Policy will be promptly and prominently displayed on the .COOKING web site."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1404 Application Download, gTLDresult.ICANN.org] Retrieved 27 Feb 2013</ref> | With respect to protecting registrant privacy and confidential information, we will comply with all applicable ICANN rules, including Whois policies, and all applicable laws, rules and regulations of appropriate jurisdictions. Registrant privacy and use of confidential information are set forth in our Privacy & Whois Policy. Information concerning updates and changes to the Privacy & Whois Policy will be promptly and prominently displayed on the .COOKING web site."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1404 Application Download, gTLDresult.ICANN.org] Retrieved 27 Feb 2013</ref> | ||
==Contract Signed== | |||
On November 21, 2013 [[TLDH]] received a [[Registry Agreement]] signed by [[ICANN]] for .cooking after passing the [[Initial Evaluation]].<ref>[http://www.icann.org/en/about/agreements/registries-date Registry Agreements, ICANN.org] Retrieved 02 Dec 2013</ref> | |||
==References== | ==References== | ||
| Line 40: | Line 41: | ||
[[Category:TLD]] | [[Category:TLD]] | ||
[[Category:Food & Drink New gTLDs|cooking]] | [[Category:Food & Drink New gTLDs|cooking]] | ||
[[Category:TLDs with Registry Agreements|cooking]] | |||