US tightens ICANN leash
Oversight over domain oversight
Saying its progress over the four years since its inception has been "disappointing", the US Department of Commerce nevertheless has renewed the powers of the Internet Corp for Assigned Names and Numbers, which coordinates the internet's addressing systems,Kevin Murphy writes
But the one-year renewal of the Memorandum of Understanding that gives ICANN its powers and responsibilities reins in the California non-profit. The DoC is to oversee ICANN more closely, and has made it clear in one case that if a task is not completed on time, ICANN's future will be in jeopardy.
Nancy Victory, assistant secretary at the DoC, wrote Friday: "The Department views the one-year term of this extension to be a critical period for ICANN to make substantial progress on the remaining transition tasks... The Department has frankly been disappointed that ICANN's progress on the MOU tasks has moved so slowly."
Stuart Lynn, ICANN's CEO, told ComputerWire: "The department is not disappointed in ICANN, it is disappointed in the progress." He pointed out that the document admits executing many of the tasks "requires more than ICANN's unilateral effort", and some of them require unprecedented levels of international coordination.
Of the MoU tasks, securing the domain name system's root server system, a network of 13 servers distributed globally and run by companies, government and academic institutions, gains precedence. The MoU "refines and underscores" ICANN's task to have a plan for fully securing the system, and the DoC wants it by the end of this year.
"The Department considers the completion of this task absolutely crucial, particularly in today's post-September 11th world," a DoC statement reads, pointing out that ICANN has made little progress on this task in four years. "ICANN's failure to do so will be a significant consideration by the Department in determining ICANN's future".
"We're not saying the root servers are insecure, but that we must make them as secure as they possibly can be," Lynn said. This task will require coordination among the 13 root server operators, ICANN, the DoC and security advisors, he said. "You don't announce security," he added, claiming enhancements are being worked on quietly.
Perhaps recognizing ICANN has limited resources, or perhaps as a comment on its success rate to date, the DoC actually increases its own responsibilities under the MoU, essentially to become more closely involved in the running of the DNS and the path toward its privatization.
The DoC will get into talks with the root server operators with the aim of speeding up the security enhancements. It will also work more closely with ICANN's Governmental Advisory Committee (GAC) and other governments to bring on board the three Regional Internet Registries and the approximately 240 country-code top-level domain operators.
The RIRs, which manage the allocation of IP address space to network operators, and the ccTLDs, which manage domains such as .uk and .jp, have proved the toughest nuts to crack for ICANN. The organization needs the support of these international bodies to avoid being perceived as a semi-legitimate US government quango.
ICANN has only signed agreements with a handful of ccTLDs (though Lynn told us more deals will be signed this year), and recently came to public blows with the RIRs over ICANN's ongoing reform efforts, which the RIRs believe does not address their desire for more autonomy from ICANN.
It remains to be seen whether ICANN will have any more success wooing these important international organizations with the DoC working in the background to support them, or if a heavier-handed US government will merely serve to scare them away.
"The Department clearly has a role to play, as recognized by its expanded responsibilities under the amended MoU," Victory wrote. "In fact, other governments also have an important role - actively participating in ICANN's GAC so as to ensure that ICANN's structure, processes and scope develop in a manner that benefits their citizens."
Sponsored: Protecting mobile certificates