.eat: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = | |logo = | ||
|status = | |status = Contract Signed | ||
|manager = | |manager = [[Google]] | ||
|country = | |country = | ||
|language = | |language = | ||
| Line 20: | Line 20: | ||
"The proposed gTLD will provide the marketplace with direct association to the term, ʺeat.ʺ The mission of this gTLD, .eat, is to provide a dedicated domain space in which registrants can enact second-level domains that provide content about food, restaurants and⁄or eating. This mission will enhance consumer choice by providing new availability in the second-level domain space, creating new layers of organization on the Internet, and signaling the kind of content available in the domain. Charleston Road Registry believes that registrants will find value in associating with this gTLD, which could have a vast array of purposes for businesses, organizations or individuals seeking to provide content related to eating. Charleston Road Registry expects these uses may include but are not limited to applications such as restaurant branded spaces (restaurantname.eat), spaces about or promoting certain food products (cheese.eat), kinds of food (organic.eat), and cooking (howtobakebrownies.eat). | "The proposed gTLD will provide the marketplace with direct association to the term, ʺeat.ʺ The mission of this gTLD, .eat, is to provide a dedicated domain space in which registrants can enact second-level domains that provide content about food, restaurants and⁄or eating. This mission will enhance consumer choice by providing new availability in the second-level domain space, creating new layers of organization on the Internet, and signaling the kind of content available in the domain. Charleston Road Registry believes that registrants will find value in associating with this gTLD, which could have a vast array of purposes for businesses, organizations or individuals seeking to provide content related to eating. Charleston Road Registry expects these uses may include but are not limited to applications such as restaurant branded spaces (restaurantname.eat), spaces about or promoting certain food products (cheese.eat), kinds of food (organic.eat), and cooking (howtobakebrownies.eat). | ||
Charleston Road Registry believes that given its wide variety of uses, the .eat gTLD will best add value to the gTLD space by remaining purely open and unencumbered by registrant restrictions. There will, therefore, be no restrictions on second-level domain name registrations in the proposed gTLD, .eat. | Charleston Road Registry believes that given its wide variety of uses, the .eat gTLD will best add value to the gTLD space by remaining purely open and unencumbered by registrant restrictions. There will, therefore, be no restrictions on second-level domain name registrations in the proposed gTLD, .eat. | ||
| Line 28: | Line 26: | ||
Charleston Road Registry is committed to implementing strong and integrated intellectual property rights protection mechanisms. Doing so is critical to Google’s goals of model Internet citizenship and fostering Internet development, especially in emerging regions. Accordingly, Charleston Road Registry intends to offer a suite of rights protection measures, which builds upon ICANNʹs required policies while fulfilling our commitment to encouraging innovation, competition and choice on the Internet."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1336 Application Details, gTLDresult.ICANN.org] Retrieved 20 Feb 2013</ref> | Charleston Road Registry is committed to implementing strong and integrated intellectual property rights protection mechanisms. Doing so is critical to Google’s goals of model Internet citizenship and fostering Internet development, especially in emerging regions. Accordingly, Charleston Road Registry intends to offer a suite of rights protection measures, which builds upon ICANNʹs required policies while fulfilling our commitment to encouraging innovation, competition and choice on the Internet."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1336 Application Details, gTLDresult.ICANN.org] Retrieved 20 Feb 2013</ref> | ||
==Contract Signed== | |||
On 23 January 2014 [[Google]] received a [[Registry Agreement]] signed by [[ICANN]] for .eat after passing all the required processes needed to become a [[Registry Operator]] for the string.<ref>[http://www.icann.org/en/about/agreements/registries-date Registry Agreements, ICANN.org] Retrieved 27 Jan 2014</ref> | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
| Line 33: | Line 35: | ||
[[Category:TLD]] | [[Category:TLD]] | ||
[[Category:Food & Drink New gTLDs|eat]] | [[Category:Food & Drink New gTLDs|eat]] | ||
[[Category:TLDs with Registry Agreements|eat]] | |||
Revision as of 22:04, 27 January 2014
| Status: | Contract Signed |
| Manager: | |
| Type: | Generic |
| Category: | Food & Drink |
More information: 
| |
.eat is a proposed TLD in ICANN's New gTLD Program. The applicant is Google (Charleston Road Registry Inc.).[1]
Application Details
The following is excerpted from that applicant's response to question #18:
"The proposed gTLD will provide the marketplace with direct association to the term, ʺeat.ʺ The mission of this gTLD, .eat, is to provide a dedicated domain space in which registrants can enact second-level domains that provide content about food, restaurants and⁄or eating. This mission will enhance consumer choice by providing new availability in the second-level domain space, creating new layers of organization on the Internet, and signaling the kind of content available in the domain. Charleston Road Registry believes that registrants will find value in associating with this gTLD, which could have a vast array of purposes for businesses, organizations or individuals seeking to provide content related to eating. Charleston Road Registry expects these uses may include but are not limited to applications such as restaurant branded spaces (restaurantname.eat), spaces about or promoting certain food products (cheese.eat), kinds of food (organic.eat), and cooking (howtobakebrownies.eat).
Charleston Road Registry believes that given its wide variety of uses, the .eat gTLD will best add value to the gTLD space by remaining purely open and unencumbered by registrant restrictions. There will, therefore, be no restrictions on second-level domain name registrations in the proposed gTLD, .eat.
Charleston Road Registry will make access to Registry Services, including the shared registration system, available to all ICANN-accredited registrars. Domain names within the proposed gTLD will be available to the general public for registration and use.
Charleston Road Registry is committed to implementing strong and integrated intellectual property rights protection mechanisms. Doing so is critical to Google’s goals of model Internet citizenship and fostering Internet development, especially in emerging regions. Accordingly, Charleston Road Registry intends to offer a suite of rights protection measures, which builds upon ICANNʹs required policies while fulfilling our commitment to encouraging innovation, competition and choice on the Internet."[2]
Contract Signed
On 23 January 2014 Google received a Registry Agreement signed by ICANN for .eat after passing all the required processes needed to become a Registry Operator for the string.[3]
References
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ Application Details, gTLDresult.ICANN.org Retrieved 20 Feb 2013
- ↑ Registry Agreements, ICANN.org Retrieved 27 Jan 2014