Apple unveils iPhone 4 and iOS 4, coming June 24 and June 21, respectively

YouTube wins title "Best HD Video Web Service" U.S. House of Representatives rejects digital TV switch delay

Cox to start throttling its broadband based on "time sensitive" protocol use

Under the new rules, web traffic is safe, but FTP, Usenet, P2P and online backups are fair game for throttling.

Digg del.icio.us Facebook StumbleUpon Twitter

Computing | by Stephen Schenck | Wed Jan 28, 2009 4:38PM | 1 comment

If you get your broadband through Cox Communications, you're in store for a change to how the company manages your data, as it's putting new throttling programs in place. Just like Comcast was caught doing last year, Cox decided that peer-to-peer traffic, regardless of legal or illegal content, didn't deserve the same traffic priority as all other communication. After Comcast caught the FCC's wrath for the practice, Cox backed off, too. Now it's going forward with a new plan, categorizing all traffic as either time sensitive or not based on the protocol being used.

Under the new strategy, first starting in Arkansas and Kansas next month, whenever Cox's network is overloaded and the company can't deliver the bandwidth you're supposed to be getting, it will start slowing down connections for what it considers non-time sensitive protocols. Of course P2P makes that list, along FTP connections, Usenet, system updates, and "network storage", whatever protocol that's supposed to mean.

Cox seems to have made some pretty odd and arbitrary choices there - you can send big files over a web connection just as easily as with FTP, yet files sent over the web count as time sensitive. Posting messages on web-based message boards gets high priority, but posting messages on Usenet boards doesn't. Then there's the glaring hole Cox is leaving open, that it considers all traffic sent over a VPN, or virtual private network, to be time sensitive. You could P2P to your heart's content with no speed hit so long as you routed the traffic through a VPN first.

This all seems like an overly-complicated solution to the problem, and one that seems likely to draw just as much attention as Comcast did with its protocol-aware throttling. Come on, Cox, just beef up your infrastructure, provide the bandwidth your customers are paying for, and stop fiddling with their data!

This story around the web:

Get more information on topics relating to this story:


Related company news:
Comcast, Cox
Related glossary terms:
P2P, File Transfer Profile (FTP), Usenet, VPN

Comments (1)

Add a comment Inappropriate or promotional comments may be removed.

Reply
Anonymous (5:19 PM on Tue Feb 10, 2009)

Regardless of how Cox wants to present this arrangement, at the end of the day they are subjectively discriminating against certain types of traffic within their network, as well as Internet destinations their customers may wish to access.

If allowed to do so, it would contradict the FCC's ruling against Comcast, and it would establish a very dangerous precedent. Today Cox is going to filter FTP, P2P and Usenet traffic, but tomorrow it may be other types of traffic (games, music, instant messaging, etc.) that don't benefit their business for one reason or another.

At the end of the day customers pay Cox for access to the Internet... not part of the Internet, not the Internet that Cox deems worthy of their network... but access to the entire network. I thought the following article had an interesting take on the matter:

http://www.newsadmin.com/usenet_commentary/commentary_020...

Add a comment

Click one of the three commenter types below. Member comments are added immediately once you confirm your email address. Anonymous comments are moderated by our editorial staff.

I want to comment as a new member an existing member anonymously

Email me

  

Comment Preview
Anonymous (9:57 PM on Sun Sep 5, 2010)

Preview your comment here.

Inappropriate or promotional comments may be removed. To create a clickable link, simply type the URL (including http://) and we will make a link for you. Line breaks and paragraphs are automatically converted — no need to use <p> or <br> tags, but if you're into that kind of thing, you can use any of the following tags: b, i, strong, em, a (href only), p and br.