.beer: Difference between revisions
Created page with "{{TLD| |logo = |status = Proposed |manager = |country = International |language = |translation = |stringcontention = |registryprovider = |registrations = |date = |typ..." |
m minor grammar edits and hyperlink updates |
||
| (19 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = | |logo =BEER-og.png | ||
|status = | |status = Delegated | ||
|manager = | |manager =[[Top Level Domain Holdings Ltd.]] | ||
|country = | |country = | ||
|language = | |language = | ||
|translation = | |translation = | ||
|stringcontention = | |stringcontention = | ||
|registryprovider = | |registryprovider = [[Minds + Machines]] | ||
|registrations = | |registrations = | ||
|date = | |date = | ||
|type = | |type = [[gTLD|Open]] | ||
|category = | |category = [[:Category:Food & Drink New gTLDs|Food & Drink]] | ||
|community = | |community = | ||
| | |priority = | ||
|website = [http://www.nic.beer nic.beer] | |||
}} | }} | ||
'''.beer''' is a [[gTLD]] that was proposed in [[ICANN]]'s [[New gTLD Program]]. [[Minds + Machines Group Limited|MMX]], also known as [[Minds + Machines Group Limited|Minds + Machines]], was the applicant and is now the [[Registry Operator]], being 1 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><ref name="delegation">[http://newgtlds.icann.org/en/program-status/delegated-strings Delegated Strings, ICANN.org] Retrieved 2 June 2014</ref> | |||
'''.beer''' is a | ==Intended Use== | ||
'''.beer''' is a new generic top-level domain targeted to brewers, beer consumers, and beer brands worldwide. | |||
==Delegation Status== | |||
'''.beer''' was delegated to the Root Zone of the [[DNS]] on 15 May, 2014, completing the successful application for the string.<ref name="delegation"></ref> | |||
==Notable Users== | |||
The '''.beer''' top-level domain provides an open interest focussed string that brewers, brands, and individuals can utilize to associate themselves, their products, services, thoughts, ideas or anything else in a positive way with the beer industry. | |||
==Application Details== | |||
'''Excerpts from Response to Question 18:''' | |||
"The '''.beer''' top-level domain will be marketed to registrants who want to associate themselves, their products, services, thoughts, ideas or anything else in a positive way with the beer industry, as well as to those who want to communicate with them in an easily identifiable way. Therefore we believe that the great majority of registrants who apply for a '''.beer''' domain name will do so because of its association with or because they want to reach those who do, and not for other reasons. In these ways, the '''.beer''' top-level domain will bring a special association with the beer industry to the top-level domain name space. | |||
==Goal== | |||
We are dedicated to protection of third-party rights and prevention of abusive uses of the '''.beer''' domain name. We intend to achieve this goal by crafting our Naming Policy, Acceptable Use Policy, and other policies to be readily understandable and easily accessible, and by making sure that our mechanisms for enforcing rights and preventing abuse (such as our Complaint Resolution Service) operate effectively, efficiently, and fairly. In addition, we will ensure that they work symbiotically with other ICANN-mandated rights protection mechanisms such as the UDRP. | |||
==Registration Policy== | |||
We have crafted a draft framework for registration of .'''beer''' domains that fully supports the goals and benefits set forth above. Our draft registration framework is based on advice from ICANN, [[WIPO]], applicable laws, and a variety of other expert sources.... | |||
We specifically examined more restrictive registration policies, such as limiting registration to members of organizations with a specific tie to the beer industry. We rejected such limitations because they would interfere with '''.beer'''’s primary mission, purpose and goals--which is to encourage as many registrants as possible to associate themselves with the beer industry for any legal purpose."<ref>[http://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/1726 Application Details, NewgTLDresult.ICANN.org]Retrieved 12 Dec 2012</ref> | |||
==Contract Signed== | |||
On 09 January 2014 [[Minds + Machines Group Limited|MMX]] received a [[Registry Agreement]] signed by ICANN for .beer 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 22 Jan 2014</ref> | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
[[Category:TLD]] | |||
[[Category:Food & Drink New gTLDs|beer]] | |||
[[Category:TLDs with Registry Agreements|beer]] | |||
Latest revision as of 18:15, 28 November 2017
 | |
| Status: | Delegated |
| Manager: | Top Level Domain Holdings Ltd. |
| Registry Provider: | Minds + Machines |
| Type: | Open |
| Category: | Food & Drink |
| Website: | nic.beer |
More information: 
| |
.beer is a gTLD that was proposed in ICANN's New gTLD Program. MMX, also known as Minds + Machines, was the applicant and is now the Registry Operator, being 1 of 68 applications that the company has filed on its own behalf.[1][2]
Intended Use[edit | edit source]
.beer is a new generic top-level domain targeted to brewers, beer consumers, and beer brands worldwide.
Delegation Status[edit | edit source]
.beer was delegated to the Root Zone of the DNS on 15 May, 2014, completing the successful application for the string.[2]
Notable Users[edit | edit source]
The .beer top-level domain provides an open interest focussed string that brewers, brands, and individuals can utilize to associate themselves, their products, services, thoughts, ideas or anything else in a positive way with the beer industry.
Application Details[edit | edit source]
Excerpts from Response to Question 18: "The .beer top-level domain will be marketed to registrants who want to associate themselves, their products, services, thoughts, ideas or anything else in a positive way with the beer industry, as well as to those who want to communicate with them in an easily identifiable way. Therefore we believe that the great majority of registrants who apply for a .beer domain name will do so because of its association with or because they want to reach those who do, and not for other reasons. In these ways, the .beer top-level domain will bring a special association with the beer industry to the top-level domain name space.
Goal[edit | edit source]
We are dedicated to protection of third-party rights and prevention of abusive uses of the .beer domain name. We intend to achieve this goal by crafting our Naming Policy, Acceptable Use Policy, and other policies to be readily understandable and easily accessible, and by making sure that our mechanisms for enforcing rights and preventing abuse (such as our Complaint Resolution Service) operate effectively, efficiently, and fairly. In addition, we will ensure that they work symbiotically with other ICANN-mandated rights protection mechanisms such as the UDRP.
Registration Policy[edit | edit source]
We have crafted a draft framework for registration of .beer domains that fully supports the goals and benefits set forth above. Our draft registration framework is based on advice from ICANN, WIPO, applicable laws, and a variety of other expert sources....
We specifically examined more restrictive registration policies, such as limiting registration to members of organizations with a specific tie to the beer industry. We rejected such limitations because they would interfere with .beer’s primary mission, purpose and goals--which is to encourage as many registrants as possible to associate themselves with the beer industry for any legal purpose."[3]
Contract Signed[edit | edit source]
On 09 January 2014 MMX received a Registry Agreement signed by ICANN for .beer after passing all the required processes needed to become a Registry Operator for the string.[4]
References[edit | edit source]
- ↑ gTLD Application Update 92 applications submitted, TLDH.org
- ↑ 2.0 2.1 Delegated Strings, ICANN.org Retrieved 2 June 2014
- ↑ Application Details, NewgTLDresult.ICANN.orgRetrieved 12 Dec 2012
- ↑ Registry Agreements, ICANN.org Retrieved 22 Jan 2014