Blog
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
107
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
109
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
111
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
112
Jul 20
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
London, Juli 2011, Der Vorstand von Top Level Domain Holdings Limited (AIM: TLDH.L) hat am 17. Juli 2011 Peter Dengate Thrush mit sofortiger Wirkung zum Aufsichtsrat ernannt. Bis vor kurzem war Dengate Thrush Vorsitzender der „Internet Corporation for Assigned Names and Numbers“ (ICANN) und in dieser Funktion maßgeblich an der im Juni erteilten Genehmigung des Programms zur Einführung neuer gTLDs beteiligt.
Antony Van Couvering, Geschäftsführer von TLDH:
“Peter und ich arbeiten als ständige ICANN Teilnehmer bereits seit deren Gründung zusammen, deshalb weiß ich, was für eine außerordentliche Bereicherung er für TLDH ist. Ich freue mich, ihn als unseren Aufsichtsratsvorsitzenden begrüßen zu können. Peter hat sich auf höchster Ebene erfolgreich für die Einführung neuer gTLDs eingesetzt. Ich bin davon überzeugt, dass wir mit ihm bei TLDH ebenso erfolgreich sein werden. Ich kann mir niemanden vorstellen, der unser Team besser ergänzen würde.“
Peter Dengate Thrush, neuer Aufsichtsratsvorsitzender:
“Ich freue mich sehr, Teil dieses erstklassigen Teams sein zu dürfen, das wesentlich an dem neuen gTLD Programm beteiligt war und das sich durch Innovationskraft, Enthusiasmus und Effektivität hervorgetan hat. Neue gTLDs bieten sowohl dem Unternehmen und seinen Investoren als auch den TLD Bewerbern und der Internet Community eine große Chance. Ich freue mich über die Gelegenheit, meinen Beitrag hierzu leisten zu können.”
“Das neue gTLD Programm stellt einen ganz erheblichen Fortschritt in Bezug darauf, wie wir das Internet verstehen und uns darin bewegen, dar. Folglich wird die Erstellung jeder Website eine wirkliche Entscheidung für eine bestimmte Top-Level Domain beinhalten und diese Entscheidung mit dem Versenden jeder Email bekräftigt. Ich freue mich, einem Unternehmen beizutreten, das diese Möglichkeiten erkennt.”
Fred Krueger, ehemaliger Aufsichtsratsvorsitzender von TLDH:
“Peter ist in diesem Geschäft überaus erfahren, allgemein geachtet und blickt auf eine lange Erfolgsgeschichte zurück. Sowohl bei unseren Kunden als auch bei den Investoren ist er gleichermaßen angesehen. Wir freuen uns sehr über das Potential und die Wachstumsmöglichkeiten des Unternehmens unter seiner Führung.”
Dengate Thrush war seit 1995 aktiv an der Ausarbeitung internationaler Regelwerke sowie der Verwaltung des Internets beteiligt und bezieht in den Medien regelmäßig Stellung zu Internetthemen. Peter war im Vorstand von InternetNZ sowie von der Asia Pacific Top Level Domain Association. Als Rechtsanwalt und eingetragener Patentanwalt mit Spezialisierung im Bereich des geistigen Eigentums ist Peter stellvertretender Vorsitzender des New Zealand Electricity Rulings Panels und Mitglied des New Zealand Copyright Tribunal.
Die Top Level Domain Holdings Limited ist das einzige börsennotierte Unternehmen mit alleinigem Schwerpunkt auf dem Erwerb und Betrieb neuer generischer Top-Level-Domains (”gTLDs”).
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
107
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
109
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
111
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
112
Jun 30
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Hier finden sie das Video vom M+M Auftritt bei TV Berlin.
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
107
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
109
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
111
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
112
Jun 22
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Berlin – Die Internet-Verwaltungsorganisation ICANN (Internet Corporation for Assigned Names and Numbers) hat bei ihrem Treffen in Singapur die Erweiterung der Top-Level Domains (TLD) verkündet. Dies ermöglicht nun die Schaffung von zahlreichen neuen Endungen und stellt eine wegweisende Entscheidung für die Entwicklung des Adresssystems im Internet dar. Unternehmen oder Organisationen können schon bald ihre eigene Domain-Endung wie etwa .berlin, .blog oder .bayern beantragen und nutzen.
Damit geht die vor zwei Jahren gegründete Minds + Machines GmbH mit ihrer, speziell dafür geschaffenen Initiative UNITE BERLIN in die konkrete Planung für die Bewerbung um den Betrieb der Top-Level-Domain .berlin. Nur mit der Zustimmung des Berliner Senats ist eine erfolgreiche Bewerbung um eine geographische Top- Level Domain, wie .berlin, bei der ICANN ab dem 12. Januar 2012 möglich.
Somit liegt die Entscheidung, ob Berlin eine eigene Top-Level Domain bekommt, allein in der Hand der Stadt. Diese ist auch für die Auswahl des Anbieters innerhalb des Wettbewerbs verantwortlich. Die Stadt Berlin profitiert von dem Wettbewerb insofern, als das dieser die beste Möglichkeit bietet, den geeignetsten Bewerber zu finden.
“Wir sind über die Entwicklung hoch erfreut. Berlin kann nun seine eigene Identität im Internet bekommen. Es liegt aber an der Stadt Berlin darüber zu entscheiden. Wir werden uns weiter um die Unterstützung der Stadt bemühen, um uns erfolgreich bei der ICANN für .BERLIN bewerben zu können.” sagte Caspar Veltheim, Geschäftsführer Minds + Machines GmbH.
Minds + Machines hat bereits vergangene Woche gemeinsam mit der Kommunikationsagentur red onion zu einem Kick-off Event mit Gästen aus der Berliner Politik, Wirtschaft und Kultur ins Soho House geladen und den Dialog zu den Berliner Köpfen gesucht. Thema dort waren die Aufklärung über den Bewerbungsprozess und den Wettbewerb für die Top-Level-Domain .BERLIN sowie das Vorgehen von Minds + Machines bei der Bewerbung.
“Wir freuen uns, die Bewerbung von Caspar Veltheims Team mit zu unterstützen. Das Treffen heute mit einigen bedeutenden Entscheidern der Stadt war ein wichtiger Schritt.” so die Einschätzung von Stephan Balzer, Geschäftsführer red onion GmbH.
Die Teilnehmer, darunter Thomas Heilmann, stv. CDU Vorsitzender des Landesverbandes Berlin, Design-Legende Erik Spiekermann, der Berliner Architekt Christoph Langhof und viele andere diskutierten über Chancen für den Standort Berlin und die Berliner Unternehmen im Zusammenhang mit dieser Erweiterung des Internets.
Die Minds + Machines GmbH ist davon überzeugt das bestmögliche Konzept umsetzen zu können, indem sie die Interessen der Stadt und der Einwohner in den Vordergrund stellt. Auch wird Minds + Machines Berlinern Domains mit weltweit führenden Registry- und DNS Services anbieten können, so dass Funktionalität und Stabilität von .BERLIN gesichert ist. Damit geht die Firma neben bisher einem weiteren Bewerber in den Wettbewerb bei der Vergabe.
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
107
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
109
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
111
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
112
Mrz 21
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Minds + Machines war wieder beim ICANN Meeting vertreten, um sich für die Einführung der .BERLIN Top-Level Domain einzusetzen.
Der ICANN Vorstand hat am Ende des Meetings eine neue Zeitleiste zur Einführung neuer Top-Level Domains veröffentlicht. Die ICANN plant den Start des Top-Level Domain Programms während des nächsten ICANN Treffens Ende Juni in Singapur. Mit diesem Treffen in Singapur endet auch die Beschäftigung von Peter Dengate Thrush – “Chair of the ICANN Board”. Er ist ein großer Befürworter neuer Top-Level Domains und viele in der Community sind der Meinung, dass er das Programm als letzte große Amtshandlung verkünden wird.
Hier die neue Timeline.
Ein Highlight des Meetings war der Auftritt vom ehemaligen US Präsidenten Bill Clinton, der das “Multi-Stakeholder-Modell” der ICANN lobte und darauf hinwies, dass bei seinem Amtsantritt 1992 nur um die 50 Internet-Webseiten existierten. Als er 2000 abtrat, waren es bereits um die 36 Millionen.
Alle Beschlüsse der ICANN in San Francisco finden Sie hier:
http://www.icann.org/en/minutes/resolutions-18mar11-en.htm

Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
107
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
109
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
111
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
112
Jan 26
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Minds + Machines hat wieder auf der Digital-Life-Design Konferenz (DLD) in München teilgenommen. Die Münchner Zukunftskonferenz bringt Internetpioniere und Vordenk
er mit Größen aus Wirtschaft, Medien und Politik zum Gedankenaustausch zusammen.
Diesjährige Teilnehmer waren u.a. Eric Schmidt (CEO and Chairman of the Board and designated Executive Chairman of Google), Randi Zuckerberg (Head of Marketing Facebook), Andrew Mason (Founder and CEO of Groupon) oder Marissa Mayer (Head of Google Local Services).
Minds + Machines konnte das Interesse vieler Teilnehmer in Top-Level Domains wecken. Erstaunlicherweise ist vielen nicht bewusst, dass ein Umbruch in der Namensgebung im Internet bevorsteht. Allerdings wussten viele von dem bevorstehend ICANN Meeting in San Fancisco.
Hier ein Link zum DLD Programm:
http://www.dld-conference.com/events/event/dld11_program_aid_5.html
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
107
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
109
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
111
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
112
Dez 17
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
ICANN Chairman Peter Dengate Thrush sagte am Ende des 39. ICANN Treffens in Cartagena, Kolumbien: “We have reached an turning point.”
Damit hat er ausgesprochen was sich viele Bewerber von neuen Top-Level Domains erhofft haben. Auch wenn die Öffnung des Bewerbungsfensters sich wohl um ca. 2 Monate verschieben wird, ist in Cartagena die Einführung neuer Top-Level Domains einen Riesenschritt weiter gekommen.
Das ICANN Board hat beschlossen, dass mehrere Bereiche im Bewerberhandbuch (Applicant Guidebook) als abgeschlossen gelten. Gerade die Fragen zum Markenschutz, die in den letzten Jahren den Bewerbungsprozeß signifikant verzögert haben, werden nun von ICANN als gelöst betrachtet. Andere noch offene Fragen zu Wirtschaftlichkeitsstudien, Malicious Conduct und Root-Scaling gelten auch als geklärt.
Trotzdem, einige andere Problembereiche bleiben weiterhin bestehen. Deshalb wird sich das Governmental Advisory Committee (GAC) und ICANN kommenden Februar zusammensetzen, um die restlichen noch offenen Fragen zu klären. Hier wird es hauptsächlich um den Schutz geographischer Namen und um “Public Morality” gehen.
Die Entscheidungen der ICANN finden Sie hier:
http://icann.org/en/minutes/resolutions-10dec10-en.htm
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
107
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
109
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
111
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
112
Okt 31
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
ICANN veröffentlicht eine neue Zeitleiste nach einem Treffen am 28. Oktober.
Das finale Richtlinienbuch soll nun schon am 09. November veröffentlicht werden.
Hier finden sie die neue Timeline und die ICANN “Resolutions”
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
107
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
109
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
111
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
112
Sep 27
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Am 24. und 25. September versammelte sich das ICANN-Board in Trondheim, Norwegen, um über noch offene Fragen der ansteheneden Erweiterung des Top-Level Domain Raumes zu entscheiden.
ICANN möchte noch vor dem Dezember-Meeting in Cartagena, Kolumbien, die nächste und wahrscheinlich finale Version des Applicant-Guidebooks (Richtlinienbuch) veröffentlichen.
“Resolved (2010.09.25.03), the Board gives the CEO the following directions relating to the forthcoming version of the Applicant Guidebook for new gTLDs, which is intended to be posted for public comment before the ICANN meeting in Cartagena in December 2010.”
Dies sind gute Nachrichten für alle Bewerber einer Top-Level Domain.
Ausserdem hat ICANN bekannt gegeben, dass das übernächste ICANN-Meeting im März 2011 in San Franciso stattfinden wird.
“Resolved (2010.09.25.07), the Board approves San Francisco, California as the location of the ICANN 2011 North America Meeting to be held from 13-18 March 2011, with a budget not to exceed US$1.941M.”
Wir erwarten, dass die ersten Bewerbungen für neue Top-Level Domains kurz nach dem Meeting in San Francisco bei der ICANN eingehen können.
Quellen:
http://www.icann.org/en/announcements/announcement-26sep10-en.htm
http://www.icann.org/en/minutes/resolutions-25sep10-en.htm#6
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
107
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
109
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
111
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
112
Sep 9
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
The .CO top-level domain made over $10 million in just a couple of months. What do the results of the .CO re-launch mean for new gTLDs?
Remember, .CO is the country-code TLD for Colombia. Until this summer, you could only register names under .com.co, .net.co, etc. You couldn’t register myname.co. Now anyone in the world can register a .co name, and register it directly under the top level. Remember also that as a country-code TLD, .CO was not constrained by ICANN rules, which means that they were able to (re-) launch their TLD relatively quickly. Even so, their rules and regulations closely hewed to the latest ICANN rules, especially in regard to cybersquatting.
The response to the .CO launch was tremendous. Let’s review:
- 11,000 names applied for during the Sunrise Period
- 28,000 names sold during the Landrush Period (closed July 15, 2010)
- Total paid by applicants for Sunrise and Landrush names: over $10 million
- Total .co names registered as of this writing: 440,000
What do these numbers mean for prospective new gTLDs? Obviously, they prove that there are lots of buyers out there if the value proposition is good, and that’s a very good sign. There is no indication (quite the opposite, in fact) that people have anything against new TLDs. Quite the opposite, in fact: if it’s a good one, they’ll flock to it in droves.
But .CO is somewhat of a special case. There are a few things to keep in mind:
First, although cybersquatting of brand names was dealt with aggressively by the talented .CO team, we have to assume that many of the registrations were done in hopes of getting traffic from people who forgot to add the “m” to a .com URL. No new gTLDs will be able to benefit from similar fat-fingered mistakes, because ICANN is running a “similarity test” to make sure that there aren’t such confusions. We won’t know how much typo traffic there actually is until it comes time to renew the names. Then, speculative traffic names will either be renewed (if they received typo traffic) or will be dropped (if they didn’t). So keep an eye on next July for interesting stats.
Second, the .CO team is really good, and did everything right. They hired smart veterans and spent a fair amount of time and money making sure that brand owners and registrars knew what was happening, what the rules were, how and when to apply, etc. This had the virtuous double effect of almost completely eliminating complaints about the process and also maximizing registrations. New TLD applicants, take note.
Third, .CO had the field to itself. When new gTLDs start launching, it will probably be on a rolling schedule, but nonetheless there is likely to be more than one launch at any given time.
These are the factors giving .CO an edge, but this doesn’t mean that new gTLDs won’t be able to duplicate or surpass their success. Many of these considerations are double-edged swords. The fact that .CO is a misspelling of .COM also means that fewer real sites will get built, fewer names will be renewed, and cybersquatting problems will be relatively larger than in most new gTLDs. The fact that .CO spent a lot of money means that their profit margin is lower.
Every new TLD launch will have specific considerations and circumstances that will both help and hinder its growth. Several new gTLDs, especially geographical names and communities, will have natural constituencies that will fuel registrations. Others will have worldwide appeal. Many will not measure their success in registrations, but instead on service to their communities.
Overall, the .CO launch should make prospective new gTLD applicants very happy indeed. It is a great proof of the market, and it shows (once again) that intelligent branding and marketing will go a long way to making a project a success.
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
43
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
35
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
107
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
109
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
111
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/functions.php on line
112
Jul 9
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Warning: strtotime() [
function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
113
Warning: date() [
function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/home/uniteber/public_html/wp-includes/link-template.php on line
138
Minds + Machines zieht ein positives Fazit aus dem 38. ICANN-Meeting in Brüssel. Die Tage wurden damit verbracht Kompromisse für Streitfragen zu finden, bei denen noch beim letzten Meeting in Nairobi keine Einigung abzusehen war. Zudem wurde nicht viel Kritik an der 4. Version des Bewerberhandbuches laut und der ICANN-Vorstand hat sich dazu bereiterklärt sich zu einer außerordentlichen Sitzung zu treffen, um die ausstehenden Probleme zu lösen. Des Weiteren kam es zu keinen unerwarteten Verzögerungen im Bewerbungsverfahren, wie zuletzt in Nairobi und Seoul. Wir erläutern hier die wichtigsten Themen des Meetings in Brüssel und geben eine Einschätzung, ob sie den Bewerbungsprozess beschleunigen oder verzögern werden.
Sondersitzung im September
Der Vorstandsvorsitzende der ICANN, Peter Dengate Thrush, hat angekündigt, dass die ICANN sich voraussichtlich im September zu einer Sondersitzung trifft, um die noch offenen Fragen im Bewerbungsverfahren zu klären. Mit großer Wahrscheinlichkeit werden bei dieser Sondersitzungen die Probleme, bei denen für die verschiedenen Interessensgruppen wenig Kompromissbereitschaft gibt, in Angriff genommen.
Der Vorstand übt somit Druck auf die verschiedenen Arbeitsgruppen („Working Groups“) aus, Anträge mit Lösungsvorschlägen vor der Sitzung zu erarbeiten. Die Bewerber für neue Top-Level Domains können sich über die Bereitschaft der ICANN, die noch offenen Probleme anzugehen, freuen.
Die Zulassung der .XXX Top-Level Domain
Der ICANN-Vorstand hat einer Bewerbung für .XXX, der Top-Level Domain für pornografische Inhalte, jetzt doch zugestimmt und somit dem gTLD Bewerbungsverfahren einen langwierigen Gerichtsprozess erspart. Hätte sich die ICANN prinzipiell gegen die Bewerbung von .XXX ausgesprochen, hätte ICM Registry, die sich für die umstrittene Top-Level Domain bewirbt, die ICANN verklagt. Dies hätte zu großen zeitlichen Verzögerungen im Bewerbungsprozess geführt. Die Entscheidung die Bewerbung für .XXX anzunehmen, wirkt sich dadurch positiv für andere Teilnehmer des Bewerbungsprozesses aus.
Klärung vieler Markenrechtsangelegenheiten
Inhaber von Markenrechten standen der Einführung neuer Top-Level Domains seit jeher kritisch gegenüber. Daher werten wir es als ein sehr positives Signal, dass sich viele Markenrechtsinhaber, darunter BBC, Nestle und das American Red Cross zusammengesetzt haben und konstruktiv darüber diskutiert haben, wie sie von der Einführung neuer Top-Level Domains profitieren können. Viele Markeninhaber stehen der Erweiterung des Namensraumes im Internet nicht mehr prinzipiell entgegen. Charlotte Walthers, vom Mobilfunkanbieter Orange, sieht neue Top-Level Domains als eine Möglichkeit den Markenwert eines Produktes zu maximieren. Voraussetzung für die Kooperation der Markeninhaber ist, dass sinnvolle Richtlinien für den Schutz von Markenrechten entwickelt werden.
Die Markenrechtinhaber haben bereits gewisse „Rights Protection Mechanisms“ im Bewerberhandbuch durchgesetzt. Ein Beispiel dafür sind Maßnahmen den Registries, die wissentlich und systematisch Markenrechtverletzungen durchführen, das Recht Top-Level Domains zu betreiben, zu entziehen. Das GAC und der ICANN-Vorstand sind ebenfalls zuversichtlich, dass bei den Markenrechtsangelegenheiten bald eine Einigung erreicht wird.
Vertigal Integration
Vertigal Integration befasst sich mit der Frage inwieweit ICANN-akkreditierte Registrare Anteil an Registries besitzen dürfen. Das aktuelle Bewerberhandbuch untersagt es Registraren mehr als 2% an einer Registry zu besitzen. Vertigal Integration ist sehr umstritten, weil sich viele Registrare für den technischen Betrieb einer Top-Level Domain bewerben möchten. Eine endgültige Regelung wurde von ICANN noch nicht abgesegnet, dennoch bemüht sich eine Working Group, der auch Minds + Machines angehört, eine Einigung zu erreichen. Trotz allem erwarten wir, dass die Entwicklung der Vertigal Integration Richtlinien den Bewerbungsprozess nicht verzögern wird.
Die letzte große Hürde: Morality and Public Order
Im Mittelpunkt der Kritik in Brüssel stand das im Bewerbungshandbuch vorgeschriebene Einspruchverfahren gegen moralisch anstößige Top-Level Domains oder Top-Level Domains, die in manchen Teilen der Welt Probleme verursachen mögen, während sie anderswo als Stärkung der regionalen Kultur im globalen Internet und Ausfluss einer aufgeklärten Gesellschaft angesehen werden.
Das Governmental Advisory Committee (GAC), das Gremium, welches die Regierungen bei der ICANN vertritt, hatte in Brüssel das Einspruchverfahren für moralisch anstößige Top-Level Domains für nicht durchführbar erklärt und die ICANN beauftragt ein alternatives Verfahren zu erarbeiten. Wir erwarten, dass ICANN einen Ausschuss zusammenstellt, der breitgefächerte kulturelle Interessensgruppen vertritt und über anstößige Top-Level Domains entscheidet.
Die Diskussion um „Morality and Public Order“ ist die größte Hürde, die es noch zu überwinden gilt, bevor die Bewerbungen endgültig eingereicht werden können. Obwohl es schwierig wird einen Konsens zu erreichen, bemühen sich die verschiedenen Parteien intensiv um einen, für alle vertretbaren, Kompromiss.
Positives Fazit
Zusammenfassend nimmt das Bewerbungshandbuch seine endgültige Form an. Obwohl es mit dem Streit um „Morality and Public Order“ eine letzte Hürde zu überwinden gilt, ist in allen anderen Streitfragen ein Konsens abzusehen. Der ICANN-Vorstand ist bemüht die Einführung neuer Top-Level Domains voranzubringen und übt Druck auf die verschiedenen Working Groups aus, um die letzten offenen Fragen bei der Sondersitzung im September klären zu können.
Wir sind optimistisch, dass unsere Timeline eingehalten wird und erwarten die Bekanntgabe des Abgabetermins für Bewerbungen bei dem nächsten ICANN Meeting im Dezember in Kolumbien.