- 15 Non-Certified IT Skills Growing in Demand
- How 19 Tech Titans Target Healthcare
- Twitter Suffering From Growing Pains (and Facebook Comparisons)
- Agile Comes to Data Integration
Network World - On the surface it seems like almost exactly the wrong time when on Jan. 27 Cox Communications announced it was about to start unequal mucking with the Internet traffic of its residential customers. Maybe the Cox folks know something I don't, but it sure seems to me that Cox has just figured out how to be the main target for a new administration and a new FCC chair that have made it clear they might be looking for just such a target.
At least this time Cox did let its customers know about its plans, unlike what Cox and other cable companies have done in the past. Cox published an FAQ about its plans that does provide some information, but not nearly enough to be able to tell just how it works or what will happen to customers' traffic. The FAQ says that "applications that are tolerant of delay ... may be momentarily slowed" during times of congestion. The FAQ provides a list of traffic types that will not be targeted for slowdown, including, it appears, that which it cannot otherwise categorize. In spite of the FAQ, here are few things I'd like to know from Cox:
• Just how is the slowing done? (Prioritizing packets? Dropping packets? Controlling cable time slots or…?)
• How does Cox figure out what application the traffic is from? (Port numbers? Deep packet inspection?)
• Where is the congestion experienced? (Local loop? Head end? Uplink? Backbone?)
• Why only residential and not business customers? (Business links do not get congested?)
• How often is Cox's network congested? (1% of the time, 50% of the time, every afternoon at 3 p.m. or…?)
• How overloaded is Cox's network when it gets congested? (5x oversubscribed, 50x or…?)
One thing I'd like to know from the developers of P2P protocols: How long (in hours) do you think it will take you to make your traffic look like it is not one of the applications Cox is targeting to slow?
I fully expect that the FCC will demand the answers to at least some of these questions before too long and I will be interested in seeing what Cox has to say.
But it just might be that Cox's customers will not have to wait for the company to fess up, at least for some of these questions. On the same day that Cox announced its traffic-mucking plans Google and a few partners announced Measurement Lab (M-Lab). M-Lab provides tools that Internet users can employ to see if their ISP is messing with their traffic. A fortuitous coincidence -- a set of tools and a demonstration why the tools are needed, both on the same day.
Google is working with the New America Foundation's Open Technology Institute (OTI), the PlanetLab Consortium and a number of academic researchers to make performance testing software available and to deploy testing servers (36 in 12 locations early in 2009) across the 'Net.
It is vital that ISPs be able to employ reasonable but fair network management technologies and processes to protect their networks. Maybe Cox is doing just that, and maybe not. We will all know in time. Cox has ensured that the question will be addressed earlier, rather than later, in the new regime.