Jump to content

.menu: Difference between revisions

From ICANNWiki
No edit summary
No edit summary
Line 1: Line 1:
{{TLD|
{{TLD|
|logo  =
|logo  =
|status = Proposed
|status = Delegated
|manager  =
|manager  =
|country  =  
|country  =  
Line 17: Line 17:


'''.menu''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[WhatBox?]] (Wedding TLD2, LLC).<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> 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.<ref>[http://www.thedomains.com/2013/03/04/menu-one-of-the-first-new-gtld-that-should-launch-goes-with-namejetafternic/ Menu One of the First New gTLD That Should Launch Goes with NameJetAfternic] TheDomains.com, Retrieved 5 March Published 4 March 2013</ref>
'''.menu''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[WhatBox?]] (Wedding TLD2, LLC).<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> 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.<ref>[http://www.thedomains.com/2013/03/04/menu-one-of-the-first-new-gtld-that-should-launch-goes-with-namejetafternic/ Menu One of the First New gTLD That Should Launch Goes with NameJetAfternic] TheDomains.com, Retrieved 5 March Published 4 March 2013</ref>
The proposed application succeeded and was delegated to the [[Root Zone]] on 2 December, 2013.<ref name="delegation">[http://domainincite.com/15216-two-more-new-gtlds-delegated Two More gTLDs Delegated, DomainIncite] Retrieved 02 December 2013</ref>


==Application Excerpt==
==Application Excerpt==
Line 29: Line 31:
==Contract Signed==
==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>
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>
==Delegation and Availability==
.menu was delegated to the [[Root Zone]] of the [[DNS]] on November 19, 2013, completing the successful application for the string.<ref name="delegation"></ref>


==References==
==References==

Revision as of 22:21, 2 December 2013

Status: Delegated
Registry Provider: ARI Registry Services
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]

The proposed application succeeded and was delegated to the Root Zone on 2 December, 2013.[3]

Application Excerpt[edit | edit source]

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."[4]

Contract Signed[edit | edit source]

On Sept 11, 2013 WhatBox? received a Registry Agreeement signed by ICANN for .menu after passing the Initial Evaluation.[5]

Delegation and Availability[edit | edit source]

.menu was delegated to the Root Zone of the DNS on November 19, 2013, completing the successful application for the string.[3]

References[edit | edit source]