Difference between revisions of ".menu"
| Line 23: | Line 23: | ||
"The Registry intends to develop two components of this gTLD. The first is the traditional registry model - a domain registration wholesale-retail model. Beyond this, the Registry plans to establish Registry-owned domains and websites, in accordance with Specification 9 of the Registry Agreement, centered around different menu categories, such as: Italian, French, Sushi, German, Ethiopian, Mexican, Indian, to name just some examples. A dedicated domain and website for each of these categories will be a content-rich environment driving Search Engine Optimization (ʺSEOʺ) and viewership, and serving as an information, pricing, reviews and communication resource for its participants. Each domain will also contain a directory of enterprises wishing to gain greater exposure to the users of the site. | "The Registry intends to develop two components of this gTLD. The first is the traditional registry model - a domain registration wholesale-retail model. Beyond this, the Registry plans to establish Registry-owned domains and websites, in accordance with Specification 9 of the Registry Agreement, centered around different menu categories, such as: Italian, French, Sushi, German, Ethiopian, Mexican, Indian, to name just some examples. A dedicated domain and website for each of these categories will be a content-rich environment driving Search Engine Optimization (ʺSEOʺ) and viewership, and serving as an information, pricing, reviews and communication resource for its participants. Each domain will also contain a directory of enterprises wishing to gain greater exposure to the users of the site. | ||
| − | |||
.. | .. | ||
The Registry will reach out to entities within the restaurant community-building platforms to generate publicity for the proposed gTLD and will welcome all registrants seeking a .menu domain. Following a Sunrise and Landrush period, the Registry intends to make domains available to anyone willing to complete the Registry’s application process and comply with Registry policies and ICANN requirements. The Registry will collect limited demographic information from registrants, which will be used to streamline searches and target communications. Registration requests for available names will be allocated by the registry through accredited registrars on a first come, first served basis, subject to the registry policies and ICANN requirements. The Registry will establish dispute resolution procedures concerning compliance with TLD registration policies and shall enforce such registration policies."<ref>[http://gtldresult.icann.org/application-result/applicationstatus Download from gTLDresult.ICANN.org]Retrieved 6 Feb 2013</ref> | The Registry will reach out to entities within the restaurant community-building platforms to generate publicity for the proposed gTLD and will welcome all registrants seeking a .menu domain. Following a Sunrise and Landrush period, the Registry intends to make domains available to anyone willing to complete the Registry’s application process and comply with Registry policies and ICANN requirements. The Registry will collect limited demographic information from registrants, which will be used to streamline searches and target communications. Registration requests for available names will be allocated by the registry through accredited registrars on a first come, first served basis, subject to the registry policies and ICANN requirements. The Registry will establish dispute resolution procedures concerning compliance with TLD registration policies and shall enforce such registration policies."<ref>[http://gtldresult.icann.org/application-result/applicationstatus Download from gTLDresult.ICANN.org]Retrieved 6 Feb 2013</ref> | ||
| + | |||
| + | ==Contract Signed== | ||
| + | On Sept 11, 2013 [[WhatBox?]] received a [[Registry Agreeement]] signed by [[ICANN]] for .menu after passing the [[Initial Evaluation]].<ref>[http://domainincite.com/14450-four-more-new-gtlds-including-sexy-get-contracts Four More New gTLDs Get Contracts, Domain Incite] Retrieved 12 Sept 2013</ref> | ||
==References== | ==References== | ||
Revision as of 17:35, 12 September 2013
| Status: | Proposed |
| Registry Provider: | ARI Registry Services |
| Registry: | Wedding TLD2, LLC |
| Registry Backend: | GoDaddy |
| Type: | Generic |
| Category: | Food & Drink |
| Priority #: | 132 - WhatBox? (Wedding TLD2, LLC) |
More information: 
| |
.menu is a proposed TLD in ICANN's New gTLD Program. The applicant is WhatBox? (Wedding TLD2, LLC).[1] In early March 2013, WhatBox? became one of the first applicants to announce its decision for auction and premium service providers. It chose Afternic and NameJet to provide sunrise and landrush auctions, and offer premium name distribution for .menu, which given its place in the priority line should be one of the first generic (non-IDN, non-brand) TLDs to be launched.[2]
Application Excerpt
The following is excerpted from applicant response to question # 18:
"The Registry intends to develop two components of this gTLD. The first is the traditional registry model - a domain registration wholesale-retail model. Beyond this, the Registry plans to establish Registry-owned domains and websites, in accordance with Specification 9 of the Registry Agreement, centered around different menu categories, such as: Italian, French, Sushi, German, Ethiopian, Mexican, Indian, to name just some examples. A dedicated domain and website for each of these categories will be a content-rich environment driving Search Engine Optimization (ʺSEOʺ) and viewership, and serving as an information, pricing, reviews and communication resource for its participants. Each domain will also contain a directory of enterprises wishing to gain greater exposure to the users of the site. ..
The Registry will reach out to entities within the restaurant community-building platforms to generate publicity for the proposed gTLD and will welcome all registrants seeking a .menu domain. Following a Sunrise and Landrush period, the Registry intends to make domains available to anyone willing to complete the Registry’s application process and comply with Registry policies and ICANN requirements. The Registry will collect limited demographic information from registrants, which will be used to streamline searches and target communications. Registration requests for available names will be allocated by the registry through accredited registrars on a first come, first served basis, subject to the registry policies and ICANN requirements. The Registry will establish dispute resolution procedures concerning compliance with TLD registration policies and shall enforce such registration policies."[3]
Contract Signed
On Sept 11, 2013 WhatBox? received a Registry Agreeement signed by ICANN for .menu after passing the Initial Evaluation.[4]
References
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ Menu One of the First New gTLD That Should Launch Goes with NameJetAfternic TheDomains.com, Retrieved 5 March Published 4 March 2013
- ↑ Download from gTLDresult.ICANN.orgRetrieved 6 Feb 2013
- ↑ Four More New gTLDs Get Contracts, Domain Incite Retrieved 12 Sept 2013