At the Computers Freedom and Privacy conference, I moderated a panel on “Do Not Track.” I tried to make sure it was fun, and I think it was. Among other things, yes, I called Ed Felten, “baby.” Check it out.
The nice folks at the New York Times “Room for Debate” feature asked me and a group of bright lights to discuss the Verizon-Google agreement on network neutrality regulation, as it stood at various points in the day.
Read the comments of Tim Wu, Lawrence Lessig, David Gelernter, Ed Felten, Jonathan Zittrain, and myself. Much of my comment owes credit to Tim Lee’s excellent paper “The Durable Internet.”
We’re all over the place, folks . . .
Update: Late addition: Gigi Sohn.
Those of you interested in transparency and “Government 2.0” issues will absolutely want to pick up Open Government: Collaboration, Transparency, and Participation in Practice, a terrific collection of 34 essays edited by Daniel Lathrop and Laurel Ruma. Much like Access Controlled, the collection of essays on global Internet filtering and censorship that I praised here last month, Open Government is a resource like no other in its field. It offers an amazing diversity of viewpoints covering virtual every aspect of the debate over transparency and open government.
The collection was published by O’Reilly Media and Tim O’Reilly himself has one of the best chapters in the book on “Government as a Platform.” “The magic of open data is that the same openness that enables transparency also enables innovation, as developers build applications that reuse government data in unexpected ways.” (p. 25) This explains why in their chapter on “Enabling Innovation for Civic Engagement,” David G. Robinson, Harlan Yu, and Edward W. Felten, of the Center for Information Technology Policy at Princeton University, speak of “a new baseline assumption about the public response to government data: when government puts data online, someone, somewhere will do something valuable and innovative with it.” (p.84) “By publishing its data in a form that is free, open, and reusable,” they continue, “government will empower citizens to dream up and implement their own innovative ideas of how to best connect with their governments.” (p. 89)
Indeed, just think about some of the many exciting sites and projects (both public and private) that have been developed thanks to government data becoming more accessible in recent years. Here’s a short list of some of the best: Continue reading →
Google has—as I noted it would last June—finally released (PCWorld, Google’s policy blog) its eagerly-awaited suite of tools available for free (of course) at MeasurementLab.net that allow users to monitor how their ISP might be tweaking (degrading, deprioritizing, etc.) their traffic—among other handy features. Huzzah!
So, now that we have visibility into traffic management practices on a large scale, remind me again why the FCC would need to mandate “net neutrality” requirements? Why not just leave the matter up to the FTC to enforce each ISP’s terms of use under the agency’s existing authority to punish unfair and deceptive trade practices? Won’t the threat of users switching to another broadband provider discipline ISPs’ traffic management? (As long as ISPs have traffic nationwide traffic management policies, even those users in areas lacking meaningful broadband competition will be protected from discriminatory network management practices by pressure in other markets.)
“If you believe that network neutrality government regulation is not needed, if you believe that the market will handle this … then you should also welcome Measurement Labs,” [Princeton Center for Information Technology Policy director Ed] Felten said. “What you are appealing to is a process of public discussion … in which consumers move to the ISP [Internet service provider] that gives them the best performance. It’s a market that’s facilitated by better information.”
Yes, it’s true (as PCWorld article linked to above points out) that a consumer might not be able to discern whether apparent degradation of their traffic was actually caused by the ISP or whether it might be the result of, say, spyware or simple Internet congestion. But they don’t need to figure that out for themselves. Although the relatively small percentage of users who install this tool are likely to be highly sophisticated (at least the early adopters), all they need to is “sound the alarm” about what they think might be a serious violation of “net neutrality” principles, and a small cadre of technical experts can do the rest: examining these allegations to determine what ISPs are actually doing.
Sure, there will be false alarms and of course many advocates of “net neutrality” regulation will still insist that ISPs shouldn’t be allowed to practice certain kinds of network management, no matter how transparently the ISPs might disclose their practices. But the truth will emerge, and in the ongoing tug-of-war between public pressure and ISPs’ practical needs to manage their networks smartly, between the desire of some to have practices disclosed very specifically and the ISPs’ desire to maintain operational flexibility, I suspect we’ll find a relatively stable (if constantly-evolving) equilibrium. It won’t be perfect, but do we really think government bureaucrats will do a better job of finding that happy medium?
The video of last week’s Cato policy forum can be viewed here. (Check out TLFer Jerry Brito’s fine presentation.)
If your preference is for a briefer taste of the transparency issues, a podcast with Ed Felten recorded that day is here:
http://www.cato.org/weekly/flvplayer.swf
The Technology Liberation Front is the tech policy blog dedicated to keeping politicians' hands off the 'net and everything else related to technology.