Welcome:
Login
|
Sign Up
|
About CircleID
Follow:
|
|
|
Those who have been involved in the ICANN process as long as I have naturally become accustomed to ICANN controversies at all levels. But the latest is a "wrong" of international ramifications. The four (4) versions of the Guidebook for the new generic Top-Level Domains (gTLDs) have been hundreds of pages long with a lot of The Good, The Bad, and to some, The Ugly. However, something new has appeared in the 4th and latest version called DAG4 can be called: "The Disturbing".
Attendees at the public ICANN meeting in Brussels today heard from over two dozen companies that have implemented or are planning to support DNSSEC, the next-generation standard protocol for secured domain names. It is clearer than ever before that DNSSEC is becoming a reality.
This Friday, it looks as though the ICANN Board will follow the clear conclusions drawn by its independent review and approve dot-xxx. Given the importance of the first use of the review process, the importance of the Board being seen to be accountable and the fact that the community was pretty unanimous in recent public comment, it is pretty much the only reasonable course of action. The question then is: how do things move forward?
When it comes to accountability, ICANN would rather be compared to other U.S. nonprofit companies than to the regulatory bodies it more closely resembles. If they truly wish to be treated like a nonprofit, rather than a regulator, there is a very simple solution: make all contributions strictly voluntary.
In Brussels on Friday, an esteemed panel of experts got together to discuss the challenge of improving ICANN's accountability. It's just too bad nobody from ICANN came by to hear it. ... While their prescriptions varied widely, the panelists were remarkably similar in their diagnoses - namely, that ICANN has yet to meet the fundamental challenge of making its board and staff accountable and answerable to the community that it is intended to serve.
With DNSSEC for the root zone going into production in a couple of weeks, it is now possible for Top Level Domain (TLD) managers to submit their Delegation Signer (DS) information to IANA. But what does this really mean for a TLD? In this post we're going to try to sort that out.
To mix metaphors, my e-mail has been ringing off the hook after my previous article and I've had to think deep and difficult thoughts about what we really mean by DNSCERT, and whether DNS-OARC really has the capability or really can grow the capability to operate such a thing. I've had some discussions with ICANN and with members of the DNS-OARC board and staff, and it's time I checkpointed the current state of my thinking about all this.
My book, "The Current State of Domain Name Regulation: Domain Names as Second Class Citizens in a Mark-dominated World" is now available by Routledge. The following is an overview of the book.
Global brand protection powerhouse MarkMonitor recently released survey results revealing the intentions of their corporate clients with respects to new gTLDs. After reading the report, it's fair to say that I'm not surprised by the results, but continue to be frustrated by them. Where are all of these forward thinking and revolutionary online marketers and brand managers? Are they so unaware of the opportunity that has been placed before them or are they just being very savvy?
In a previous CircleID article, it was discovered and documented that NAF Panelists and Complainants were systematically copying/pasting nonsense into UDRP decisions. It has been a couple of months with no action by ICANN, and no public statement by NAF. In a shocking new development, though, it turns out that NAF has quietly edited a past UDRP decision!
A World-Renowned Source for Internet Developments. Serving Since 2002.