.berlin: Difference between revisions
No edit summary |
mNo edit summary |
||
| (17 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{TLD| | {{TLD| | ||
|logo = | |logo = [https://dot.berlin/sites/dot.berlin/files/dotBerlin_wortmarke_RGB.png] | ||
|status = | |status = Active | ||
|manager = | |manager = dotBERLIN GmbH & Co. KG | ||
|country = Germany | |country = Germany | ||
|language = | |language = German | ||
|translation = | |translation = English | ||
|stringcontention = Yes | |stringcontention = Yes | ||
|registryprovider = | |registryprovider =[[TLD-BOX]] | ||
|registrations = | |registrations = 54.857 | ||
|date = | |date = 31.12.2017 | ||
|type = [[GeoTLD]] | |type = [[GeoTLD]]/[[Community TLD]] | ||
|community = | |community = The city of Berlin, Germany | ||
|keypeople = | |priority = | ||
|keypeople = Dirk Krischenowski, Katrin Ohlmer | |||
}} | }} | ||
'''.berlin''' is | '''.berlin''' is an active [[geoTLD]] proposed in [[ICANN]]'s [[New gTLD Program|new gTLD program]]. [[dotBERLIN]] manages the TLD and is its [[Registry]]. The proposed application succeeded and was delegated to the [[Root Zone]] on 08 January, 2014.<ref name="delegation">[http://newgtlds.icann.org/en/program-status/delegated-strings Delegated String, ICANN.org] Retrieved 09 Jan 2014</ref> | ||
Historically, there are two main entities that have expressed public interest in running .berlin, [[ | ==Background== | ||
The proposal was one of the first and most prominent gTLDs, specifically geoTLDs, that began circulating as a possibility in the early-mid 2000s should ICANN decide to expand the root zone with new gTLDs. | |||
Historically, there are two main entities that have expressed public interest in running .berlin, [[dotBERLIN]] and [[Unite Berlin]]; the former received government support and was the only applicant.<ref>[http://dot.berlin/ dotBERLIN.de]</ref><ref>[http://www.uniteberlin.de/ UniteBerlin.de]</ref> Its application is a [[Community TLD|Community Priority Application]]. | |||
== | ===dotBERLIN=== | ||
With new gTLD discussion happening in ICANN, [[Dirk Krischenowski]] and [[Alexander Schubert]] founded [[ | With new gTLD discussion happening in ICANN, [[Dirk Krischenowski]] and [[Alexander Schubert]] founded [[dotBERLIN]] GmbH & Co. KG in 2005; at that time [[ICANN]]'s new [[gTLD]] application process was expected to begin in 2009.<ref>[http://dotberlin.com/ dotberlin.com]</ref> This process took longer to develop and was finally approved in June, 2011. Because of this delay, and the fact that dotBERLIN was prepared for a 2009 launch, they have asked for special consideration from [[ICANN]] in the delegation process. Specifically, DotBERLIN has asked that "One extra point in the [[Community Priority Evaluation]] should be given if the organization behind an applicantion was already established before the approval of the new gTLDs program by the ICANN Board on 26 June, 2008, or before the first communicated application window in March, 2009."<ref>[http://domainnamewire.com/2010/07/15/dotberlin-wants-special-status-with-new-gtlds-because-of-its-early-involvement/ DomainNameWire]</ref> That concession was not made by ICANN. | ||
The reason [[dotBERLIN]] asked for such special consideration could be due to the fact that specific threats to their proposal have appeared. That is, [[Minds + Machines]] launched a [[Unite Berlin]] initiative, which is itself lobbying for the .berlin name space, some 6 years after dotBERLIN had already declared its intentions.<ref>[http://www.domainnews.com/en/exclusive-interview-with-dirk-krischenowski-dotberlin-qwe-did-not-ask-minds-a-machines-for-helpq.html DomainNews.com]</ref> | The reason [[dotBERLIN]] asked for such special consideration could be due to the fact that specific threats to their proposal have appeared. That is, [[Minds + Machines]] launched a [[Unite Berlin]] initiative, which is itself lobbying for the .berlin name space, some 6 years after dotBERLIN had already declared its intentions.<ref>[http://www.domainnews.com/en/exclusive-interview-with-dirk-krischenowski-dotberlin-qwe-did-not-ask-minds-a-machines-for-helpq.html DomainNews.com]</ref> | ||
==Community TLD== | |||
The community has been defined in conjunction with the city to include only those individuals and entities that have a verifiable presence or connection to the city of Berlin. Registration will require verification of one of the following: "their residence or second home, office or place of business, a branch or permanent establishment in the City of BERLIN, or; a contact listed in the Whois database with a domicile in the City of BERLIN, or; other appropriate proof e.g. the certification by an employer to enroll at a school or college, or birth certificate." | |||
The City of Berlin has issues a Letter of Support for [[dotBERLIN]].<ref>Application 1-902-9993. Retrieved 23 November 2012</ref> | |||
==Contract Signed== | |||
On 31 October 2013, [[dotBERLIN]] received a [[Registry Agreement]] signed by [[ICANN]] for .berlin after passing the [[Initial Evaluation]].<ref>[http://www.icann.org/en/about/agreements/registries Registry Agreements, ICANN.org] Retrieved 04 Nov 2013</ref> | |||
==Delegation and Availability== | |||
.berlin was delegated to the [[Root Zone]] of the [[DNS]] on January 8, 2014, completing the successful application for the string.<ref name="delegation"></ref> | |||
===Sunrise=== | |||
The [[Registry]] announced that the [[Sunrise Period]] for the string would begin 14 February 2014 and end on 16 March 2014. This was a "Start Date Sunrise", a type of Sunrise period that has been rare among New gTLD strings.<ref>[http://newgtlds.icann.org/en/program-status/sunrise-claims-periods TLD Startup Information, ICANN.org] Retrieved 24 January 2014</ref> | |||
==References== | ==References== | ||
| Line 28: | Line 45: | ||
[[Category:TLD]] | [[Category:TLD]] | ||
[[Category:GeoTLD|berlin]] | [[Category:GeoTLD|berlin]] | ||
[[Category:TLDs with Registry Agreements|berlin]] | |||
Latest revision as of 13:01, 25 April 2018
| [[Image:[1]|150px|center]] | |
| Status: | Active |
| country: | Germany |
| Language: | German |
| Translates to: | English |
| Manager: | dotBERLIN GmbH & Co. KG |
| Registry Provider: | TLD-BOX |
| Registrations: | 54.857 |
| Date Implemented: | 31.12.2017 |
| Type: | GeoTLD/Community TLD |
| Community: | The city of Berlin, Germany |
More information: 
| |
![[1]](https://dot.berlin/sites/dot.berlin/files/dotBerlin_wortmarke_RGB.png){kind=link}
.berlin is an active geoTLD proposed in ICANN's new gTLD program. dotBERLIN manages the TLD and is its Registry. The proposed application succeeded and was delegated to the Root Zone on 08 January, 2014.[1]
Background[edit | edit source]
The proposal was one of the first and most prominent gTLDs, specifically geoTLDs, that began circulating as a possibility in the early-mid 2000s should ICANN decide to expand the root zone with new gTLDs.
Historically, there are two main entities that have expressed public interest in running .berlin, dotBERLIN and Unite Berlin; the former received government support and was the only applicant.[2][3] Its application is a Community Priority Application.
dotBERLIN[edit | edit source]
With new gTLD discussion happening in ICANN, Dirk Krischenowski and Alexander Schubert founded dotBERLIN GmbH & Co. KG in 2005; at that time ICANN's new gTLD application process was expected to begin in 2009.[4] This process took longer to develop and was finally approved in June, 2011. Because of this delay, and the fact that dotBERLIN was prepared for a 2009 launch, they have asked for special consideration from ICANN in the delegation process. Specifically, DotBERLIN has asked that "One extra point in the Community Priority Evaluation should be given if the organization behind an applicantion was already established before the approval of the new gTLDs program by the ICANN Board on 26 June, 2008, or before the first communicated application window in March, 2009."[5] That concession was not made by ICANN.
The reason dotBERLIN asked for such special consideration could be due to the fact that specific threats to their proposal have appeared. That is, Minds + Machines launched a Unite Berlin initiative, which is itself lobbying for the .berlin name space, some 6 years after dotBERLIN had already declared its intentions.[6]
Community TLD[edit | edit source]
The community has been defined in conjunction with the city to include only those individuals and entities that have a verifiable presence or connection to the city of Berlin. Registration will require verification of one of the following: "their residence or second home, office or place of business, a branch or permanent establishment in the City of BERLIN, or; a contact listed in the Whois database with a domicile in the City of BERLIN, or; other appropriate proof e.g. the certification by an employer to enroll at a school or college, or birth certificate."
The City of Berlin has issues a Letter of Support for dotBERLIN.[7]
Contract Signed[edit | edit source]
On 31 October 2013, dotBERLIN received a Registry Agreement signed by ICANN for .berlin after passing the Initial Evaluation.[8]
Delegation and Availability[edit | edit source]
.berlin was delegated to the Root Zone of the DNS on January 8, 2014, completing the successful application for the string.[1]
Sunrise[edit | edit source]
The Registry announced that the Sunrise Period for the string would begin 14 February 2014 and end on 16 March 2014. This was a "Start Date Sunrise", a type of Sunrise period that has been rare among New gTLD strings.[9]
References[edit | edit source]
- ↑ 1.0 1.1 Delegated String, ICANN.org Retrieved 09 Jan 2014
- ↑ dotBERLIN.de
- ↑ UniteBerlin.de
- ↑ dotberlin.com
- ↑ DomainNameWire
- ↑ DomainNews.com
- ↑ Application 1-902-9993. Retrieved 23 November 2012
- ↑ Registry Agreements, ICANN.org Retrieved 04 Nov 2013
- ↑ TLD Startup Information, ICANN.org Retrieved 24 January 2014