Cox to try coaxing the Internet into submission
Our friend at Cox is about to get selectively friendly toward Internet content.
(Credit: Dong Ngo/CBS Interactive)Net neutrality fans, grab your chairs; I have some rocking news.
Cox Communications, the third-largest cable Internet provider in the U.S., announced Tuesday that starting February, it will begin testing a new method of managing traffic on its high-speed Internet network in Kansas and Arkansas.
This means during the times the network is congested the company will--to put it bluntly--discriminate between Internet content and regulate the bandwidth accordingly.
The company divides Internet traffic into two categories: time-sensitive and nontime-sensitive, with the former taking the priority during the congested hours.
Here's the company's break-down of these two categories:
The time sensitive category includes:
- Web (Web surfing, including web-based e-mail and chat embedded in Web pages)
- VoIP (Voice over IP, telephone calls made over the Internet)
- IM (Instant messages, including related voice and Webcam traffic)
- Streaming (Web-based audio and video programs)
- Games (Online interactive games)
- Tunneling & Remote Connectivity (VPN-type services for telecommuting)
- Other (Any service not categorized into another area)
The nontime-sensitive category includes:
- File Access (Bulk transfers of data such as FTP)
- Network Storage (Bulk transfers of data for storage)
- P2P (Peer to peer protocols)
- Software Updates (Managed updates, such as operating system updates)
- Usenet (Newsgroup related)
Cox says the new congestion management plan only kicks in when congestion levels reach a certain high. It also insists the company will ensure that its customers continue to have a good online experience.
Personally, I don't really mind this, because I live in California and games are categorized as time-sensitive. For those who are more concerned, you can learn more about Cox's congestion management plan here.
Dong Ngo is a CNET editor who covers networking and network storage, and writes about anything else he finds interesting. You can also listen to his podcast at insidecnetlabs.cnet.com. E-mail Dong. 
Maybe they should move your bandwidth hogging to the overnight hours when the neighborhood isn't trying to surf the web? An acquaintance had the idea that the ISP should be like the electric company and charge a lower rate for bandwidth at night when demand is lower to encourage bandwidth hogs to not run during the day. Or maybe like the cell phone company and have a limit during high demand periods and no limit during low demand periods.
IMHO, it seems to me that the people crying the loudest about "net neutrality" and "I want unlimited bandwidth" are the ones hogging all the bandwidth.
Burying cables not only lets you do less work for maintenance, but by having them in the ground, there's more support for a larger amount of cables. Fiber Optics do have weight to them, if they're buried, there can be more fiber optic cables.
If they're kept inside a noncorrosive pipe and run through sewer lines across the US, like telephone lines should be, along with power lines, then not only would these services go down much less, but there could be a much larger flow of information without a huge increase in cost for the ISPs, the timber from the poles used to hold them up in the air could come down, fallen trees would no longer cause outages for large numbers of customers at a time and ice storms wouldn't be any worry at all.
It would require one massive investment in the beginning. After that, the prices for customers could drop to near zero because of the decline in need for maintenance.
Of course, there are other benefits, such as getting rid of the eye sores that currently fill the skylines and getting rid of lots of the reasons power, telephone or internet goes out.
Of course, very few people think in the long-term these days.
It's only a matter of time.
I agree about someone getting faster serivce for the same price. Cox should have to put together something outlining exactly how much of your usage was timesensitive and not time sensitive, and create an appropriate pricing structure. This, of course, would be way too exmensive to implenemt and they would have to abandon it altgether.
I hope they get run out of town on a rail.
I'm not really against network management, and maybe that is because I'm not a file-sharer. But I do find this kind of plane sight disregard for federal regulations a little discomforting.
1) Your ISP will determine what you can and can't see on the Internet by limiting your connection performance to areas of the Net they don't deem worthy. Your favorite Internet locations may appear on Cox's preferred "time sensitive" list today, but what happens when it's not there a week, a month a year from now.
2) ISPs like Cox have a monopoly on the market, so it's becoming increasingly more difficult to find suitable alternatives to their service. As a result they can implement whatever service policies they like, and the majority of their customers are stuck with them.
The FCC stopped Comcast from doing this last year, and the current administration appears to be a big supporter of net neutrality, so I'm hoping the latest announcement from Cox doesn't go unnoticed.
I thought the following article had an interesting take on this...
http://www.newsadmin.com/usenet_commentary/commentary_02092009.asp
techonova.com
What they're talking about is Layer 7 Quality of Service.
This is a *VERY* normal thing to do on a network -- take a look at the linksys DD-WRT or Tomato firmware's QoS settings.
Here's the thing. They're not the ones deciding what's time sensitive. *Your* computer is.
When packets leave your edge router, they're marked with a TOS byte (Type of Service) that identifies it as interactive traffic or non-interactive traffic. They're also marked with a ECN (Explicit Congestion Notification) tag.
http://en.wikipedia.org/wiki/Explicit_Congestion_Notification
Therefore, Cox is using simple language to inform people they're going to be supporting *STANDARD TCP/IP ROUTING FUNCTIONS THEY SHOULD ALREADY HAVE BEEN SUPPORTING FOR YEARS.*
This is actually kind of a good thing.
(By the way, most Bittorrent clients already mark their packets as low priority non-interactive traffic.)
Companies like Cox (with this time sensitive division), and Time Warner (with thier usage-based pricing with extremely low caps based on downloaded items) are getting away with this for one reason and one reason only. They are the ONLY game in town. And who is to blame for that? Our local counties/parishes, cities, villages, and towns. Years ago, when the cable TV industry was very young, they allowed cable companies to sign exclusivity agreements whereby another cable company would not be allowed into a market. That practice amounts to almost sanctioned monopolies in some areas, and, should be stopped to promote free and open competition between cable companies.
Perhaps it is time to deregulate the cable TV industry, much like the telephone industry was a few years ago. Imagine if Cox, Comcast, AND Time Warner ALL serviced one city, say, the size of Buffalo, NY? Cable rates would be lower, and there would be a much wider range of choice in channels, and services, offered. Just MAYBE we in the US would get the type of upload/download speeds that broadband users in Asian countries currently enjoy!
- by johndporter July 8, 2009 4:51 AM PDT
- People keep saying Cox can do this because they're "the only game in town".
- Reply to this comment
-
(20 Comments)Where is this true? It's certainly not true in my neck of the woods - Cox is up against Verizon and RCN (formerly Starpower)... and possibly Comcast as well.
I also caution people to look at the total customer experience when choosing a provider. I was with RCN for many years until I decided, recently, to take advantage of Verizon's hot deals on FiOS. What a mistake! RCN always treated me well; they're a small, regional company. They have weaknesses typical of a small company. For example, their support hotline is only up from 9-5, five days a week. A big company like Verizon, with their 24x7 help desk, was tempting. Reality: Verizon suffers from too-big syndrome. I had some problems in the transfer of my phone number (I had the three-way package), and Verizon was completely unable to sort it out. I had to talk to half a dozen different departments (going through endless phone menu trees) and none of them knew what the others were doing. It was a frustrating mess. After 3 days of no resolution (and no phone), I said, Screw it, and called Cox.
What a breath of fresh air. Cox is large enough to have their act together, yet small enough to offer personal, customized service and support. They handled all of my issues in a timely, successful manner, and most amazingly, you can reach a live human on their help line 24x7. This is something neither the juggernaut Verizon nor the scrappy RCN were able to do. Cox also didn't give me any BS about why they couldn't install my service on the appointed day, as Verizon did.
So, I don't know - maybe if you watch a lot of high-res video streaming, or play WoW constantly, or some such, Cox's bandwidth offerings might be insufficient. I don't do that, and I've had only positive experiences with them. They even diagnosed and fixed an *inside-the-house* phone line problem (red/green reversed) which I've had for years, at no charge.
Take this as one data point.
I don't really have an opinion on the whole net neutrality issue. I hope KamilionSchnook is right, and it's just about respecting ToS markers already in the packets. I do want to clarify one thing: the post above says Cox is going to "discriminate between Internet content." This is misleading. They are going to look at the protocol of each packet, and possibly other "meta-data" such as ToS markers. Yeah, at the data link layer, this info is "content", but it is not content as the user thinks of it. They're not going to look at the URL of your http request, and slow down accesses to playboy.com relative to other sites, for example. I do think it's strange that they consider email a time-sensitive protocol, however. Email is the ultimate NON-time-senstive protocol! I hope that's simply a mistake.