Net Neutrality, Comcast and QoS
There are some misunderstandings and some issues that need to be worked out, and a lot of FUD in the market that confuses the conversation.
I just read through Gary Audin's article on Net Neutrality and want to put in my comments. I agree with Gary that net neutrality will overall be beneficial to consumers. But there are some misunderstandings and some issues that need to be worked out, and there is a lot of FUD in the market that confuses the conversation.
Comcast: First let's talk about Comcast. Articles across the blogosphere keep referring to the time when Comcast was "blocking" peer to peer traffic. While this is technically correct, it does not really portray what was going on.
Comcast found that a small percentage of their users were consuming a very high percentage of the network bandwidth, and they were predominantly using peer-to-peer transfer protocols like BitTorrent, swapping music or video files. They took the view that users consuming high volumes of traffic was fine unless it impacted their neighbors. The cable plant shares bandwidth between a group of neighbors. In a typical scenario there might be 6 Mbps of uplink bandwidth that is shared by 100 or 150 users, each of which is allowed to use as much as 1 Mbps of upload bandwidth on a momentary basis. Obviously not all the users can use 1 Mbps concurrently, but in most cases this is not a problem. Uplink bandwidth is typically small unless you are uploading pictures, updating websites, or transferring music using BitTorrent.
If six people, in the scenario above, are all using BitTorrent, it is possible for them to fill the uplink pipe, and then cause performance problems for the other 144 neighbors using the same bandwidth.
Comcast chose to alleviate this problem by slowing down BitTorrent for heavy users. BitTorrent does not consume all its bandwidth with one TCP connection, but instead opens many connections to many different PCs around the world, and sends off pieces of a file to each one. Comcast monitored those connections, and limited the number of links a PC could open by killing TCP connections beyond that limit. So BitTorrent was being slowed down by blocking some of the many threads it opened. But BitTorrent was still operating. Most of the music transfers got through, they just took a little longer.
After receiving criticism for this approach, Comcast changed their methodology. The new approach monitors the utilization of each user (total bandwidth consumed over a measurement period) and then lowers the priority of all traffic from that user if the uplink is congested and if the user has been a heavy user. Priority is reset to normal after the user demand or the total uplink demand drops to a less congested state. The effect of this approach is that heavy users can use the network when they are not in contention with their neighbors. When they are in contention with neighbors, the lower volume neighbors are given priority, but the heavy user is still given every possible byte of available bandwidth to continue to upload their files.
The same algorithm applies to downlink bandwidth, except the bandwidth numbers are much higher. Management of uplink and downlink bandwidth is independent.






