In several of our previous podcasts (see episodes 34, 35,and 37), we’ve discussed what we’ve called the “Comcast Kerfuffle,” which was the controversy surrounding the steps Comcast took to manage BitTorrent traffic on its networks. Critics called it a violation of Net neutrality principles while Comcast and others called it sensible network management.
This week we saw a new kerfuffle of sorts develop over the revelation in a Monday front-page Wall Street Journal story that Google had approached major cable and phone companies and supposedly proposed to create a fast lane for its own content. What exactly is it that Google is proposing, and does it mean – as the Wall Street Journal and some others have suggested – that Google is somehow going back on their support for Net neutrality principles and regulation? More importantly, what does it all mean for the future of the Internet, network management, and consumers. That’s what we discussed on the TLF’s latest “Tech Policy Weekly” podcast.
Today’s 30-minute discussion featured two of our regular contributors at the TLF, who both wrote about this issue multiple times this week.
Cord Blomquist of the Competitive Enterprise Institute wrote about the issue here and here, and Bret Swanson of the Progress & Freedom Foundation wrote about it here and here. To help us wade through some of the more technical networking issues in play, we were also joined on the podcast by Richard Bennett, a computer scientist and network engineer guru who blogs at Broadband Politics as well as Circle ID and he also pens occasional columns for The Register. Also appearing on the show was Adam Marcus, Research Fellow & Senior Technologist at PFF, who wrote a “nuts and bolts” essay full of excellent technical background on edge caching and net neutrality.
You can download the MP3 file here, or use the online player below to start listening to the show right now.
[display_podcast]
The introduction below was originally written by Adam Thierer, but now that I (Adam Marcus) am a full-fledged TLF member, I have taken authorship.
My PFF colleague Bret Swanson had a nice post here yesterday talking about the evolution of the debate over edge caching and network management (“Bandwidth, Storewidth, and Net Neutrality“), but I also wanted to draw your attention to related essay by another PFF colleague of mine. Adam Marcus, who serves as a Research Fellow and Senior Technologist at PFF, has started a wonderful series of “Nuts & Bolts” essays meant to “provide a solid technical foundation for the policy debates that new technologies often trigger.” His latest essay is on Network neutrality and edge caching, which has been the topic of heated discussion since the Wall Street Journal’s front-page story on Monday that Google had approached major cable and phone companies and supposedly proposed to create a fast lane for its own content.
Anyway, Adam Marcus gave me permission to reprint the article in its entirety down below. I hope you find this background information useful.
Nuts and Bolts: Network neutrality and edge caching
by Adam Marcus, Progress & Freedom Foundation
December 17, 2008
This is the second in a series of articles about Internet technologies. The first article was about web cookies. This article explains the network neutrality debate. The goal of this series is to provide a solid technical foundation for the policy debates that new technologies often trigger. No prior knowledge of the technologies involved is assumed.
To understand the network neutrality debate, you must first understand bandwidth and latency. There are lots of analogies equating the Internet to roadways, but it’s because the analogies are quite instructive. For example, if one or two people need to travel across town, a fast sports car is probably the fastest method. But if 50 people need to travel across town, it may require 25 trips in a single sports car. So a bus which can transport all 50 people in a single trip may be “faster” overall. The sports car is faster, but the bus has more capacity. Bandwidth is a measure of capacity, of how much data can be transmitted in a fixed period of time. It is usually measured in Megabits per second (Mbps). Latency is a measure of speed, of the time it takes a single packet data to travel between two points. It is usually measured in milliseconds. The “speeds” that ISPs advertise have nothing to do with latency; they’re actually referring to bandwidth. ISPs don’t advertise latency because its different for each different site you’re trying to reach.
Continue reading →
Claims that Google has abandoned its stance on network neutrality have been thoroughly debunked, as Cord and Adam note below. Over at Broadband Reports, Karl Bode explains that Google is seeking edge-caching agreements, not preferential treatment. Edge-caching involves Google housing its content on servers located inside consumer ISP networks, cutting bandwidth costs by allowing users to access Google content located just a few hops away.
Even though edge-caching doesn’t violate network neutrality as defined by Google, it’s still one of the many advantages that big players have over new entrants. Edge-caching isn’t a “fast track,” as the WSJ imprecisely terms it, but rather a short track—functionally, there’s a lot of similarity between the two. As Richard Bennett has explained time and time again, being close to end users is quite advantageous even without preferential treatment, as it eliminates the need to push vast amounts of data across the congestion-prone core of the public Internet.
We’ve heard about how edge-caching enables content providers and ISPs to cut their bandwidth bills and make more efficient use of finite network resources. Both of these are true, but there’s more—edge caching makes it much less likely that users will experience long load times or buffering hiccups while watching streaming video online. That high-def YouTube clip might take a few extra seconds to buffer if it has to make its way through congested central network exchanges—not so, however, if that video is housed just a few hops away, within your ISP’s network.
Continue reading →
Over just the past 24 hours, there’s been quite a hullabaloo surrounding the Wall Street Journal’s controversial front-page story on Google’s edge caching plan and whether it violates Net neutrality. (See Cord’s post and Bret’s). Lessig calls it a “made-up drama“, David Isenberg says it’s “bogus” and “bullshit,” and Google’s Rick Whitt has said it’s much ado about nothing.
Regardless, here’s the important thing not to overlook about this episode: It is a prime example of the what Tim Lee has referred to as “the fundamental problem of backlash” that ensues whenever there is even
a hint of a potential violation of network neutrality (however one defines it). As Tim argued in his excellent Cato paper on Net neutrality, “No widespread manipulation would go unnoticed for very long,” and a “firestorm of controversy would… be unleashed if a major network owner embarked on a systematic campaign of censorship on its network.” (p. 23). Indeed, this (non-)story about Google’s edge-caching plans have spawned an intense “firestorm of controversy” over the past 24 hours and it doesn’t even involve serious network meddling or censorship! I’ve been trying to keep up with all the traffic about this on TechMeme and Google News during that time, but I have given up trying to digest it all. (Take a look at those snapshots I pasted down below to get a feel for the volume we are talking about here).
In that regard, I love this quote from the always-bloodthirsty Tim Karr of the (inappropriately-named) regulatory activist group Free Press:
If Google or any other tech company were secretly violating Net Neutrality, there would be an absolute and cataclysmic backlash from the grassroots and netroots who have made Net Neutrality a signature issue in 21st Century politics. The Internet community would come crashing down on their heads like Minutemen on Benedict Arnold.
Indeed, that’s exactly what we saw today. But it wasn’t just pro-regulatory fanatics like Free Press. The entire tech and business blogoshere and even some of the mainstream media were on top of this. That’s the “fundamental problem of backlash” at work, and with a vengeance.
The Technology Liberation Front is the tech policy blog dedicated to keeping politicians' hands off the 'net and everything else related to technology.