A couple of weeks ago, I attended part of the ICANN meeting in San Francisco. I've been watching ICANN and been peripherally aware of their issues since the organization began, but this was my first chance to attend a meeting. What I learned is that ICANN is a crazy behemoth of a bureaucracy, steeped in impenetrable acronyms and processes that make it nearly impossible for someone new to get up to speed. The best example of this is the recent approval of the .XXX top-level domain. more
In preparation for some upcoming long-haul international flights, I was looking for some "light" ICANN reading material. One document that came to mind was ICANN's 2010 Annual Report. Over the last four years ICANN has produced a year end report. While this document was probably originally conceived as a means to demonstrate ICANN's progress... more
After wading through the various IANA Notice of Inquiry (NOI) submissions I thought I would take a break and do a secondary review of the recently concluded ICANN regional meeting in San Francisco. In doing this review there were three things that kind of jumped out at me as still missing in action. more
Yesterday, taking a look at the "Legal Rights Objection" (3.1.2.2) I read : "An intergovernmental organization (IGO) is eligible to file a legal rights objection if it meets the criteria for registration of a .INT domain name". Taking a look at registered .INT domain names, I found Basel Convention on the Control of Transboundary Movements of Hazardous Wastes and their Disposal... more
NameSmash has interviewed Garth Bruen, Internet security expert and creator of Knujon, on some key issues under discussion during the recent ICANN meetings in San Francisco. Topics include Whois, DNS Security Extensions (DNSSEC) and generic Top-Level Domains (gTLDs) -- issues of critical importance particularly with ICANN's expected roll-out of thousands of new gTLDs in the coming years. more
In her blog EU Commissioner Neelie Kroes blogs on her stance on cloud computing. In short: this is a good development which the EU will embrace and advocate, but may need regulation in order to ensure a safe environment for industry and individuals in the cloud. Here's some thoughts on that. more
Steve DelBianco did a great job of discussing the rocky relationship between ICANN's Government Advisory Committee (GAC) and the Board of Directors, in his piece entitled ".XXX Exposes the Naked Truth for ICANN". I've been keeping an eye on the adult industry press to see what their reaction is to the .XXX debacle. But before we start, let's get something out of the way. more
At Friday's board meeting, ICANN once again narrowly approved the contentious .XXX domain intended for pornography. What this vote primarily shows is that ICANN's processes have been broken for a long time, and aren't getting fixed. Two board members made thoughtful and eloquent statements before the vote outlining the reasons they were about to vote for or against the domain. more
We have long argued that ICANN should consider categories for new gTLDs because different categories will have markedly different benefits and impacts for consumers. It is difficult to represent the complexities of the world in any system and the flat, first come first served single level approach ICANN is proposing is actually more cumbersome, more restrictive, more expensive and less equitable than the very successful existing system it is seeking to extend. more
I have struggled over the past couple of weeks to come up with a metaphor to succinctly describe the standoff between the ICANN Board and the ICANN Government Advisory Committee (GAC) over the new generic Top-Level Domain (gTLD) implementation process. So here's my best attempt to explain these dynamics in terms a layperson may be better to understand. I chose the metaphor for its timeliness, without meaning to offend anyone. more
The Brussels meeting between the ICANN Board of Directors and the Governmental Advisory Committee (GAC) became contentious over what constitutes a "bylaws consultation," what that designation means, and whether future meetings between the parties should be labeled as such. At the risk of going over familiar ground, it may be useful to review what the bylaws say about ICANN's duty to consult with the GAC. more
There has been no shortage of speculation within the ICANN community regarding the continued show down between the ICANN Board and its Governmental Advisory Committee (GAC) over new generic Top-Level Domains (gTLDs) and the pending expiration of the IANA contract this September. Now one of the more interesting topics of discussion that I have had with multiple independent parties was the potential of ICANN making changes to the L root zone file... more
If an important debate of our age is going on right now but you don't know where, no one can blame you. Part of the intrigue surrounding discussion of how the Internet will be governed is deliberate; the current process and forums were conceived by parties who want to make sure that if their agenda fails in one place that they can claw back ground in another. Part of that plan is the byzantine "commitology" of the UN system, which is now frighteningly relevant to the broadband industry and civil society. What follows is an effort to make this clear what, where, when, and how it all will happen in 2011. more
Over the last two days I have sat in a room and watched a rather interesting dynamic unfold between the ICANN Board and its Government Advisory Committee (GAC). While I remain optimistic of there being a responsible closure to the new gTLD implementation process within the next six months, an apparent double standard being used by the ICANN Board could be a potential stumbling block. more
The ICANN Board has itself in a pretty pickle. The Governmental Advisory Committee (GAC) Consultancy with the Board in Brussels was an apparent non-starter. After hundreds of man-hours' worth of comments provided by the Intellectual Property Constituency (IPC), the Board continues to claim that it lacks sufficient information on trademark issues in order to respond to concerns. more