.eat: Difference between revisions
Created page with "{{TLD| |logo = |status = Proposed |manager = |country = |language = |translation = |registryprovider = |registrations = |date = |type = Generic |category..." |
No edit summary |
||
| Line 16: | Line 16: | ||
'''.eat''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[Google]] ([[Charleston Road Registry Inc.]]).<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> | '''.eat''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[Google]] ([[Charleston Road Registry Inc.]]).<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> | ||
==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."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1336 Application Details, gTLDresult.ICANN.org] Retrieved 20 Feb 2013</ref> | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
Revision as of 17:17, 20 February 2013
| Status: | Proposed |
| 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]
References
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ Application Details, gTLDresult.ICANN.org Retrieved 20 Feb 2013