It seems like a victory for many to see Comcast punished for throttling BitTorrent, but now it seems the FCC has become confused about what to do at this point on the case.There was already word that there is some dissent on the FCC ruling over throttling BitTorrent, but commentary from CNET seems to point out that there is much more going on at the FCC then originally thought. Apparently, after the FCC issued a press release on the matter (DOC, PDF), Comcast basically cried foul over it - no fines, just a measly press release. The interesting part is the idea that prioritizing Voice Over IP is actually perfectly fine - so does BitTorrent need to be left alone? You can read the comments yourself: Critics correctly note that Congress still has not given the FCC explicit authority to decide Internet policy. Even as the FCC issued its decision, Chairman Kevin Martin went on record writing that while Comcast had no right to prioritize Internet traffic, it's fine to prioritize voice over IP: It seems there is a lot of confusion about this ruling. It may be possible that the theory from the FCC is that ISPs can do something to give priority to a packet, but it's not OK to take priority away from a packet. Put it in another way, it's fine to add carpool lanes, but it's unfair to put speed limits on the other lanes. Either way, one may wonder if Comcasts punishment is simply some bad publicity and a subliminal note saying they can keep doing what they are doing. With some suggesting that the FCC can't do much with little legal authority (a fact that contributed to the downfall of the broadcast flag originally), there isn't much that can be done at this point. |
![]() |
members that voted for this story
|










