If you’re reading this within an hour after it was posted, you’ve got about 17 hours to comment on an important change being proposed at ARIN, the manager of Internet Protocol addresses for the North American region.
ARIN is proposing a new “Policy Development Process.” (Sound familiar?) A step by step description of the proposal can be found here. The essence of the change is that the ARIN Advisory Council would manage and dispose of all policy proposals. The new PDP proposal is an example of the increasing formalization of IP address policy making. This trend, which is probably inevitable, will continue. Everyone interested in Internet governance needs to understand that and be attuned to the consequences. ARIN’s Advisory Council will become more of a gatekeeper for policy proposals.
Net neutrality debate spreads to Europe
Thursday I spoke in Brussels at a well-attended seminar on “Net Neutrality and the [EU] Reform Proposals for the Electronic Communications Sector.” The event had a number of sponsors, including two Belgian Universities (Namur and Leuven) the ISP Association of Belgium and some consultancies. It appears that the neutrality norm for internet governance is becoming widely discussed in Europe and is influencing the European Commission's implementation of its sectoral reform efforts. Indeed there is a Principle proposed in Article 8 that end users should be able to access and distribute content and use the applications of their choice.
Chris Boam of Verizon was there and made some interesting comments. One was that Verizon has no interest in Deep Packet Inspection technologies and has rejected the idea of implementing them. The other was that Verizon's Open Development Initiative, which supposedly loosened up its vertical leverage over wireless handsets on its network, was “not a change in policy” but simply a re-packaging and more aggressive public promotion of its prior policy, which was that any handset manufacturer or developer could approach Verizon and be approved if they met some basic criteria. Hmmm…
NTIA Shrugs
The NTIA has released a short announcement about the mid-term review of ICANN. The announcement tells us very little except that the administration hasn't changed its position on anything important regarding its supervisory relationship to ICANN. The US is reasonably comfortable with the status quo and won't move until someone makes them very uncomfortable. Nothing they heard in February did so. Clearly, NTIA was not looking for information about what needs to be done, but seeking confirmation of its prior tendency to do nothing. It will leave to a future Presidential administration the issue of whether to continue to be the unilateral “ruler of the root”
Judge Says We Can't Look Inside US .XXX deliberations
It's “Sunshine Week” in Washington, a week devoted to “open government,” but the light came a few days late for ICM Registry and Stuart Lawley, proponents of the .xxx top level domain for adult content. A US court dismissed ICM Registry's litigation to pry more information out of the US government about the pressure it put on ICANN to reject ICM's application to operate the .xxx top level domain. The court decision favoring darkness is posted here.
New Anti-phishing law: A Snowe job?
Council of Europe Works to Criminalize Political Expression
The Council of Europe is pushing to extend the Cybercrime Convention to impose criminal sanctions on what it considers to be unacceptable forms of political or religious expression. The Cybercrime Convention was originally negotiated to respond to transnational problems such as theft of data, breaking into computers, computer-based financial fraud and the like. But now the Council is engaged in bulk unsolicited emails to promote the idea that web site content that is insulting or xenophobic is a cybercrime of the same order.
Finnish scandal unmasks censorship tactics
For some time it has been known that law enforcement authorities in Norway and Finland have prepared lists of alleged child pornography web sites, and demanded that local Internet service providers block access to them. This model of blocking access was avidly picked up by Internet law enforcement authorities in other countries, including the Netherlands, where pressure has been placed on ISPs to block these sites or risk being publicly smeared as aiding and abetting child abuse.
Using ISPs as intermediaries for censorship is a bad idea because mandated site blocking violates the principle of net neutrality. Truly illegal content should be handled by prosecuting the producers, publishers and hosts of the content rather than through attempts to block and control Internet access on a territorial basis. Governments, however, claim that they must block access because of the heinousness of child abuse and because the heinous sites were out of the reach of local law enforcement. Many people have bought that argument.
Until now. Recently, Finnish activists got their hands on the Finnish government's official list of blocked sites. The results of their discovery are astounding. Most of the censored sites are located either in the United States or EU countries — and thus are not outside the reach of child protection laws. Equally disturbing, most of the sites on the blocking list are not child pornography sites at all, but legal adult pornography sites. And many are not even porn sites at all.
What is the JPA?
Bret Fausett's blog has cast new light on the ICANN JPA question. Many of us had assumed that the JPA was a replacement for the earlier, more prescriptive Memorandum of Understanding between ICANN and the US Commerce Department. The MoU was first drafted in November 1998 and was amended six times from 1999 to 2003. Ending the JPA, it is widely assumed, would eliminate all forms of Commerce Department oversight over ICANN's policy making and leave in place only the more important IANA contract, which is completely separate from the JPA/MoU. Doubts are now raised about this assumption.
As IGP warned an uncomprehending press corps back in 2006, the shift from MoU to JPA was much less of a “dramatic step” away from US control than ICANN's PR effort made it out to be. Now, if Fausett is right, it appears that getting rid of the JPA is less important than ICANN is making it out to be.
It all depends on what we mean by “the JPA.”
Reforming ICANN Oversight: A Historic Opportunity
IGP today responded to a U.S. Department of Commerce proceeding seeking comment on the future of its political oversight over ICANN. The proceeding is part of a mid-term review of ICANN's 3-year Joint Project Agreement (JPA) with U.S. Commerce Department NTIA.
In a move that is likely to attract attention and debate we called for ICANN and the IGF to forge an agreement to institute a bi-annual review and public consultation concerning ICANN’s record and accountability. These ideas will be raised both at the U.S. Commerce Department public meeting February 28 and at the public consultation of the U.N. Internet Governance Forum in Geneva February 26.
Governments, ICANN and the JPA (part 2)
We were discussing how governments could take over ICANN. This was in response to a new meme gaining popularity within the Beltway: the idea that we need to retain the Commerce Department’s leash on ICANN (the JPA) because if we don’t, other governments (autocratic Russians, Chinese commie hordes, turbaned Islamo-fascists or languid, dirigiste Europeans) will somehow “interfere” with DNS.
But the future of the JPA has virtually nothing to do with ICANN’s subordination to other governments. It's about ICANN's subordination to the US government. The people advancing this meme have not specified how a government takeover is supposed to happen, much less how retaining the JPA would prevent it. As I started to argue yesterday, it is hard to conceive of a single plausible scenario for governments to exert more power over ICANN that isn't either a) already happening, and being aided and abetted by the USG; b) more likely to happen the longer the US stays in control or c) require the US government’s consent.
To prove this point, here are some plausible scenarios and mechanisms through which national governments could put pressure on ICANN. By examining these, we can better appreciate just how far off base the CDT and others are.