We knew – and we suspect that ICANN knew – that calling for public comment on the future of the .xxx domain after ICANN was slapped on the wrist for its mishandling of the proposal was a useless procedure. Now we have confirmation. As we approach the comment deadline (May 10), we have a flood (6,000 and counting) of comments from the same rightwing religious groups that mobilized against .xxx back in June and July of 2005. We also have another 150 comments from the Free Speech Coalition – a group of online porn providers who also didn’t like the idea 5 years ago and mobilized against it. And a petition with thousands of signatures for xxx. Does this sound vaguely familiar?
At the ARIN meeting
I have been attending the American Registry for Internet Numbers (ARIN) meeting in Toronto. ARIN is one of the RIRs, i.e., the Internet address registry and policy making authority for North America. Although I have observed and participated on RIR lists for some time and interacted with RIR representatives at ICANN, WSIS and IGF, this is the first time I have been able to attend a meeting. I'm glad I did.
Internet Society Attacks Beckstrom's DNS “sky is falling” talk
It's not often you get to see the Internet Society butt heads directly with ICANN, which some consider its creature. In comments filed today with ICANN, the President and CEO of the Internet Society (ISOC), Lynn St. Amour, sent some sharply-worded criticism to ICANN President and CEO Rod Beckstrom. The comment, which was sent to the entire ICANN Board, criticized Beckstrom for his comments before the Governmental Advisory Committee at the Nairobi meeting last month, when he claimed that the domain name system is “under attack as never before” and implied that it is likely to collapse at any moment. Beckstrom made these comments by way of promoting his idea of a “DNS CERT”.
Cyber-Spin: How the Internet gets framed as dangerous
At the beginning of this year, a set of powerhouse organizations in cybersecurity (CSO Magazine, Deloitte, Carnegie Mellon's CERT program, and the U.S. Secret Service) released the results of a survey of 523 business and government executives, professionals and consultants in the ICT management field.
The media coverage generated by this survey provides an unusally clear illustration of how cyber security discourse has become willfully detached from facts. It shows clearly how there is an organized industrial and political imperative to drill into our heads the idea that the Internet is a dangerous thing and its threats are spiralling upwards at an uncontrollable rate. It doesn't matter what facts are uncovered, they are all interpreted to support this preconception.
With that intro, here is the lead sentence from the January 25 2010 Carnegie-Mellon University news release about the 2010 CyberSecurity Watch Survey: “Cybercrime threats posed to targeted organizations are increasing faster than many organizations can combat them, according to the 2010 CyberSecurity Watch Survey…”
Stop right there. A careful review of both the survey and the ensuing responses to it quickly reveals that that conclusion did NOT come from the survey itself, and was not supported by its data.
Evaluate Continued Uncertainty
On March 26, ICANN’s General Counsel, John O. Jittery, had a nervous breakdown. Internal observers speculated that the breakdown may have been caused by the stress and ignominy of losing the independent review challenge that concluded ICANN's denial of ICM Registry's application for a .xxx domain was unfair and discriminatory. Unfortunately for ICANN, the deranged lawyer managed to get links to the incoherent documents he produced posted on the organization’s front page as a request for public comment.
Advertising and the future of the Internet
Two presentations at the recent IETF meeting in California underscore the way the Internet’s architecture is being shaped increasingly by advertising-driven content distribution networks.
The clever ICANN board
I’ve been forced to rethink my initially dismissive assessment of the ICANN board’s Nairobi resolution on the separation of domain name registries and registrars. As you may recall, I called the resolution “needlessly biased and poorly worded;” and while I recognized that it was “an attempt to clarify things,” I asserted that it “probably did the opposite.” Strange as it may seem, it is possible for both of those accusations to be true and for the resolution to be a stroke of political brilliance in moving toward the formation of a new policy regarding registry-registrar separation.
The ITU IPv6 Group meeting
Geneva, March 15 and 16, 2010. The first meeting of the IPv6 group of the International Telecommunication Union (ITU) turned into a protracted and tedious confrontation between one government – Syria – and the combined weight of all the incumbent Internet institutions, the European Telecom Numbering Organization, equipment vendors and the governments of North America and Europe (plus Australia). Defenders of the IP addressing status quo showed up in force…
Ruling the Root part II: RPKI and the IP address space
The Internet Architecture Board issued a little-noticed statement February 12 that has the potential to revolutionize Internet governance – and not in a good way. The IAB is now claiming that the application of Resource Public Key Infrastructure (RPKI) to addressing and routing is “a prerequisite for improving the security of the global routing system.” What may get lost in all the technical mumbo-jumbo is that RPKI is a technology of control and identification. We need to think long and hard before embarking on a path that would lead to the global centralization of such authority in a single institution's hands.
The Nairobi Board resolutions: painful to read
The ICANN board issued a fairly large number of resolutions, at the conclusion of its Nairobi meeting. Give it an A for effort. But on substance? Give them an F. On the .xxx issue, the Board chose to ignore its independent review panel and refused to rectify what was officially determined to be unfair and discriminatory treatment. On the vertical integration issue, it issued a needlessly biased and poorly worded resolution that was an attempt to clarify things but probably did the opposite. There are other gems. We have done the painful work of reading them for you.