The Wall Street Journal reports today that Google wants a fast lane on the Internet and has claimed that the Mountain View based giant may be moving away from its stance on network neutrality:
Google’s proposed arrangement with network providers, internally called OpenEdge, would place Google servers directly within the network of the service providers, according to documents reviewed by the Journal.
The problem with the Journal piece is that OpenEdge isn’t exactly a neutrality violation, or maybe it is. As Declan McCullagh at CNET has pointed out in his post “Google accused of turning its back on Net neutrality,” figuring out when a neutrality violation has occurred is a little tricky:
The problem with defining Net neutrality so the government can regulate it is a little like the problem of defining obscenity so the government can ban it: You know it when you see it.
Well, Google says that it knows a neutrality violation when it sees one and not surprisingly it doesn’t see one in its own actions. It’s defense essentially boils down to them pointing out that OpenEdge is caching. It’s more of a warehouse than a fast lane. Besides, anyone else can do the same thing, so Google isn’t using any ISP’s “unilateral control over consumers’ broadband connections” to their advantage.
Interestingly, however, the same Google’s Policy Blog entry defends other companies that engage in the same sort of caching, including LimeLight. But LimeLight Networks isn’t just a data warehousing company, they combine caching with real fast lanes.