Feeds

ICANN explains ‘thinking’ behind top domain decisions

It was never anything to do with how good the application was (?!)

  • alert
  • submit to reddit

Top three mobile application threats

ICANN has explained its peculiar rational behind the choice of global top-level domain names, and defended accusations that the entire process was flawed, at a Congressional sub-committee.

Chairman of ICANN, Vinton G. Cerf, was faced with a barrage of criticism over the process, its limited time span, and the final choices made. He defended the decision to charge all applicants a non-refundable $50,000, saying that the fee was needed to cover the cost of the process since ICANN has no money of its own.

He admitted it was a shame that its staff report into the bids - on which decisions were heavily based and was full of errors - wasn't available to anyone except ICANN until only days before the decisions were made. He claimed this was because of the large number of comments made by members of the public, which were then tied into the report.

As for complaints that ICANN refused to talk to applicants: this just isn't true. ICANN staff refused to have private conversations with them. "For this process to work, the vast bulk of ICANN's work must be transparent to the public, and so with very rare exceptions (such as matters dealing with personnel issues), everything ICANN does it does in public." [cough! splutter! cough!] We must warn you that Mr Cerf's definitions of "private" and "personnel" are liable to be very different from your own.

The three-minute pitch that comprised the entire personal contact that applicants had with ICANN staff was also justifiable. Oral presentations "were never intended to be the sole or primary source of information for the Board". And "the opportunity to make a presentation at the public forum was simply the final step in an extensive process, available so that any last-minute questions could be asked or points made."

We haven't heard if he commented on the accusation that the incredible speed with which the entire process was run (and original aspects of the process dropped) was due to the fact that the At-Large members (again, that's the directors voted for entirely democratically by the Internet community) were due to start. As it was, the decisions were made before they took their places and none of them had a hand in the process.

However, the most interesting bit about Vinton's testimony was the explanation of how ICANN viewed the entire process. The decision over what gTLDs were approved and who was given the right to run them apparently had nothing to do with how good the actual applications were.

"This effort was not a contest to find the most qualified, or the most worthy, or the most attractive for any reason of the various applicants," he told the committee. "ICANN is not and should not be in the business of making value judgments. What ICANN is about is protecting the stability of the Internet and, to the extent consistent with that goal, increasing competition and competitive options for consumers of domain name services. Thus, what ICANN was doing here was an experiment, a proof of concept, an attempt to find a limited number of appropriate applicants to test what happens when new TLDs of various kinds are added to the namespace today."

It would seem that ICANN has a serious identity problem here. No matter what it may think it is, it has effectively managed to win executive power of the Internet. With this power comes not only technical responsibility but also commercial responsibility. If ICANN is unable to make a fair decision, it should have found another organisation to do it.

He goes on to say the same thing a few times, but sums it up in this phrase: "This was never a process in which the absolute or relative merit of the particular application was determinative."

So have we all misunderstood ICANN? It is just a techie outfit that has been lumbered with all these other responsibilities and everyone is being a bit unfair to it? Well, we'd agree that it's not up to the job. But then the organisation has gone out of its way to make itself as powerful and non-attributable as possible, so it only has itself to blame. We'd welcome the formation of another body to take over the non-techie aspects of the Internet. In fact, we'd be delighted. ®

Related Links

Vinton's testimony
The Committee run-down

Related Story

Congress sets date for ICANN review

Top three mobile application threats

More from The Register

next story
Sorry London, Europe's top tech city is Munich
New 'Atlas of ICT Activity' finds innovation isn't happening at Silicon Roundabout
MtGox chief Karpelès refuses to come to US for g-men's grilling
Bitcoin baron says he needs another lawyer for FinCEN chat
Dropbox defends fantastically badly timed Condoleezza Rice appointment
'Nothing is going to change with Dr. Rice's appointment,' file sharer promises
Audio fans, prepare yourself for the Second Coming ... of Blu-ray
High Fidelity Pure Audio – is this what your ears have been waiting for?
Did a date calculation bug just cost hard-up Co-op Bank £110m?
And just when Brit banking org needs £400m to stay afloat
Zucker punched: Google gobbles Facebook-wooed Titan Aerospace
Up, up and away in my beautiful balloon flying broadband-bot
Apple DOMINATES the Valley, rakes in more profit than Google, HP, Intel, Cisco COMBINED
Cook & Co. also pay more taxes than those four worthies PLUS eBay and Oracle
prev story

Whitepapers

Designing a defence for mobile apps
In this whitepaper learn the various considerations for defending mobile applications; from the mobile application architecture itself to the myriad testing technologies needed to properly assess mobile applications risk.
3 Big data security analytics techniques
Applying these Big Data security analytics techniques can help you make your business safer by detecting attacks early, before significant damage is done.
Five 3D headsets to be won!
We were so impressed by the Durovis Dive headset we’ve asked the company to give some away to Reg readers.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Securing web applications made simple and scalable
In this whitepaper learn how automated security testing can provide a simple and scalable way to protect your web applications.