Difference between revisions of ".cooking"
Simoncousins (talk | contribs) |
m |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
| − | |logo = | + | |logo =Cooking.jpg |
|status = Delegated | |status = Delegated | ||
|manager = | |manager = | ||
| Line 7: | Line 7: | ||
|translation = | |translation = | ||
|stringcontention = | |stringcontention = | ||
| − | |registryprovider = | + | |registryprovider =[[MMX]] |
|registrations = | |registrations = | ||
|date = | |date = | ||
| − | |type = [[gTLD| | + | |type = [[gTLD|Open]] |
|category = [[:Category:Food & Drink New gTLDs|Food & Drink]] | |category = [[:Category:Food & Drink New gTLDs|Food & Drink]] | ||
| + | | website = [http://mmx.co mmx.co] | ||
|community = | |community = | ||
|priority = | |priority = | ||
| Line 17: | Line 18: | ||
}} | }} | ||
| − | '''.cooking''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]]. [[ | + | '''.cooking''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]]. [[Minds + Machines Group Limited|MMX]], also known as [[Minds and Machines, LLC|Minds + Machines]], was the only applicant for .cooking, which is one of 68 applications that the company has filed on its own behalf.<ref>[http://www.tldh.org/2012/06/gtld-application-update-92-applications-submitted/ gTLD Application Update 92 applications submitted, TLDH.org]</ref> The proposed application succeeded and was delegated to the [[Root Zone]] on 31 March 2014.<ref name="delegation">[http://newgtlds.icann.org/en/program-status/delegated-strings Delegated Strings, ICANN.org] Retrieved 15 April 2014</ref> |
| − | + | ==Intended Use== | |
| − | . | + | '''.cooking''' is a new generic top-level domain targeted to chefs, cooks, restaurants, culinary organizations, food-focused e-commerce platforms, kitchen appliance brands, and other food-related industries. |
| − | == | + | ==Notable Users== |
| − | .cooking | + | The potential applications of a '''.cooking''' address are many. Restaurants, culinary organizations, food-focused e-commerce platforms, kitchen appliance brands: virtually any company that works in the trillion-dollar global food industry can make use of a .'''cooking''' domain to enhance its brand. |
| − | ===Application Details | + | ==Delegation and Availability== |
| + | '''.cooking''' was delegated to the [[Root Zone]] of the [[DNS]] on 31 March 2014, completing the successful application for the string.<ref name="delegation"></ref> | ||
| + | |||
| + | ==Application Details== | ||
The following is excerpted from the applicant's response to question #18: | The following is excerpted from the applicant's response to question #18: | ||
| − | "The goal of the . | + | "The goal of the '''.cooking''' gTLD is to give cooks of all experience levels the ability to share ideas, methods, tips, and best-practices and to provide a meaningful domain for those involved in the commercial aspects of cooking. |
| + | |||
| + | As one of the most popular recreational activities in the United States, cooking has a diverse following. There are cooking shows to teach technique and recipes and even cook-offs that pit master chefs against each other and against guests. Cooking benefits both from being a utilitarian activity and an art form; a growing community exists based on the common interest it generates and is sustained by the sharing of methods, tips, knowledge, and expertise built on years of experience. The '''.cooking''' top-level domain will offer those looking for information about cooking an easily-identifiable means of recognizing sites that want to affiliate themselves with the cooking world. | ||
| − | + | 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. | |
| − | + | ==Registration Policies== | |
| − | + | 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 . | ||
| − | * Our recognition that registrants of a . | + | * Our recognition that registrants of a '''.cooking''' domain name will self-select because they have an interest in cooking, naturally reducing the number of potential registrants; and, because restrictive policies such as, for example, requiring membership in a specific organization or organizations, would exclude many legitimate registrants from obtaining a '''.cooking''' domain name. For example, and by way of illustration, if membership an organization were required for registration, businesses and charitable organizations that would find a '''.cooking''' top-level domain name an effective marketing tool would be excluded from registering a .cooking domain name as they might not be eligible to be members in an organization that accepted only natural persons for membership. |
| − | 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 . | + | 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 [[ | + | On November 21, 2013 [[Minds + Machines Group Limited|MMX]] 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== | |
{{reflist}} | {{reflist}} | ||
Latest revision as of 18:42, 28 November 2017
 | |
| Status: | Delegated |
| Registry Provider: | MMX |
| Type: | Open |
| Category: | Food & Drink |
| Website: | mmx.co |
.cooking is a proposed TLD in ICANN's New gTLD Program. MMX, also known as Minds + Machines, was the only applicant for .cooking, which is one of 68 applications that the company has filed on its own behalf.[1] The proposed application succeeded and was delegated to the Root Zone on 31 March 2014.[2]
Intended Use
.cooking is a new generic top-level domain targeted to chefs, cooks, restaurants, culinary organizations, food-focused e-commerce platforms, kitchen appliance brands, and other food-related industries.
Notable Users
The potential applications of a .cooking address are many. Restaurants, culinary organizations, food-focused e-commerce platforms, kitchen appliance brands: virtually any company that works in the trillion-dollar global food industry can make use of a .cooking domain to enhance its brand.
Delegation and Availability
.cooking was delegated to the Root Zone of the DNS on 31 March 2014, completing the successful application for the string.[2]
Application Details
The following is excerpted from the applicant's response to question #18:
"The goal of the .cooking gTLD is to give cooks of all experience levels the ability to share ideas, methods, tips, and best-practices and to provide a meaningful domain for those involved in the commercial aspects of cooking.
As one of the most popular recreational activities in the United States, cooking has a diverse following. There are cooking shows to teach technique and recipes and even cook-offs that pit master chefs against each other and against guests. Cooking benefits both from being a utilitarian activity and an art form; a growing community exists based on the common interest it generates and is sustained by the sharing of methods, tips, knowledge, and expertise built on years of experience. The .cooking top-level domain will offer those looking for information about cooking an easily-identifiable means of recognizing sites that want to affiliate themselves with the cooking world.
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.
Registration Policies
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:
- Our recognition that registrants of a .cooking domain name will self-select because they have an interest in cooking, naturally reducing the number of potential registrants; and, because restrictive policies such as, for example, requiring membership in a specific organization or organizations, would exclude many legitimate registrants from obtaining a .cooking domain name. For example, and by way of illustration, if membership an organization were required for registration, businesses and charitable organizations that would find a .cooking top-level domain name an effective marketing tool would be excluded from registering a .cooking domain name as they might not be eligible to be members in an organization that accepted only natural persons for membership.
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."[3]
Contract Signed
On November 21, 2013 MMX received a Registry Agreement signed by ICANN for .cooking after passing the Initial Evaluation.[4]
References
- ↑ gTLD Application Update 92 applications submitted, TLDH.org
- ↑ 2.0 2.1 Delegated Strings, ICANN.org Retrieved 15 April 2014
- ↑ Application Download, gTLDresult.ICANN.org Retrieved 27 Feb 2013
- ↑ Registry Agreements, ICANN.org Retrieved 02 Dec 2013