FCC Chief Says Comcast Violated Internet Rules
Several readers sent in word that the FCC chairman, Kevin Martin, is calling for sanctions and enforcement actions against Comcast for resetting BitTorrent traffic. "Mr. Martin will circulate an order recommending enforcement action against the company on Friday among his fellow commissioners, who will vote on the measure at an open meeting on Aug. 1... Martin, a Republican, will likely get support from the two Democrats on the commission, who are both proponents of the network neutrality concept. Those three votes would be enough for a majority on the five-member commission."
Since so many people enabled BT encryption, this whole idea of theirs has really backfired. Now, even if they were to shape some traffic to try to keep BT traffic in the network, so many people will now keep this encryption on that it won't work as well as it would have if they would have, in the first place, worked with the technology instead of against.
So, what sort of precedent might this set for other attempts to block access? Numerous states have attempted to block access, by law, to what they deem to be illegal content. Would a ruling like this tie the hands of companies like Comcast so that they're in a "damned if you do damned if you don't" position, or would one ruling likely supercede the other?
I also find this amusing. Comcast is whining about it, but they're effectively been told off and punished for not disclosing to their customers what they were doing to paid services. It really says a lot about the company that they're complaining that they have to inform their customers before they make significant service changes.
Hell if customers should be informed and able to make competent purchasing decisions... informed and self-interested customers would utterly destroy Comcast's entire business model.
Weird slashbug #455
With Net Neutrality being a hotly debated issue at the moment, it seems a bit forward of Martin to act on either side of the issue. Comcast has not violated the law, and while it might be against Martin's view of the FCC's "principles", it cannot be held liable for actions that are not illegal.
If he goes ahead with this action and Net Neutrality is struck down, Comcast would have a good lawsuit to bring against the FCC and Martin personally.
It's not bittorrent comcast needs to worry about. It's Tiger Woods
Don't get too excited yet. "Penalty" could be a slap-on-the-wrist drop-in-the-bucket fine per infraction... something small enough that could reasonably be passed on to the customer.
Actually, this isn't entirely surprising. What we may be looking at here is less a fully-developed FCC position on net neutrality and more of a turf war between federal agencies.
Both the FCC and the FTC have expressed concern about Comcast's activities. The FCC is concerned as the federal telecommunications infrastructure regulator. The FTC is concerned as the chief consumer protection agency. The FCC really doesn't want the FTC getting in the way of regulating the Internet, which the FCC has been struggling with since the 1996 Act was first passed (you try applying what is essentially a voice communications act to any IP network, let alone all of them!). By acting now, even arguably prematurely, the FCC has essentially staked a claim to the issue, signaling to the FTC to keep away.
Look at this, the FCC taking action --- don't look at the man behind the curtain listening to your phone calls, scanning your emails, etc. without a warrant.
The real "Libtards" are the Libertarians!
So, what sort of precedent might this set for other attempts to block access? Numerous states have attempted to block access, by law, to what they deem to be illegal content.
Comcast wasn't blocking illegal traffic - they were blocking traffic they felt was expensive to handle and a plausible threat to their video content business.
On the first point, I use BitTorrent every few weeks and it's always to download FLOSS. I set my upload ratio to 3 to be reasonable but helpful. There's nothing illegal about this - compare with doing a Google search for My_Favorite_Song.mp3 and downloading it over HTTP.
On the second point, the FCC has previously barred a DSL ISP (ILEC) from interfering with VOIP traffic as an anti-competitive measure.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
Hmm. I'm not convinced. What about VoIP? I *like* my low-latency reliable VoIP, and I like the fact that my ISP is able to prioritize it over bulk traffic like BT. Ditto small HTTP traffic bursts, DNS requests, etc.
One solution would be per-user bandwidth allocation - as it has been on the proposed list for ages now... Then all you have to do, is you yourself decide not to run BT when you are making a VoIP call... How hard is that? Yours is the responsibility and yours is the power to decide what is important for you, and not the ISP, which has no business whatsoever, deciding your preferences for you...
I still can't figure out how sending a forged packet is not a denial of service attack. If I started putting forged packets on Comcast's network, wouldn't they treat it as a criminal matter? Why doesn't somebody report them to the FBI?
What is going on? Did I wake up in a parallel universe this week? Are we going to die?
That sounds nice, but it relies on ISPs not overselling capacity.
You can get service with ISPs that don't oversell, and actually have enough upstream bandwidth to service all their customers downloading and uploading at max speed all the time. It costs 20-30 times as much, but it's available. After all, most ISPs operate at a contention ratio of between 10:1 and 30:1, where they have enough bandwidth for 1 fully utilized connection for every 10-30 signed customers.
What might be a more reasonable compromise is for ISPs to reserve a fixed 64kbps or so per user. Even that, though, will quickly get expensive. They really need to be allowed to use QoS to provide acceptable performance for latency-sensitive applications while continuing to service bulk traffic - and doing it all cheaply.
Hmm. I'm not convinced. What about VoIP? I *like* my low-latency reliable VoIP, and I like the fact that my ISP is able to prioritize it over bulk traffic like BT. Ditto small HTTP traffic bursts, DNS requests, etc.
Prioritizing (i.e., QoS) is OK, but what Comcast did wasn't any sort of QoS...it was forging packets to say "please permanently disconnect". I know that some people may define cutting off connections as QoS, but it isn't. QoS implies that every connection gets to send all of its data, eventually.
Hmm. I'm not convinced. What about VoIP? I *like* my low-latency reliable VoIP, and I like the fact that my ISP is able to prioritize it over bulk traffic like BT. Ditto small HTTP traffic bursts, DNS requests, etc.
This is not an issue of prioritization; this is a forced destruction of undesired (by ISP standards) streams.
Besides your ISP more than likely uses hot-potato routing http://en.wikipedia.org/wiki/Hot-potato_routing which does its best to take the shortest path _out_ of their network regardless of increase in latency caused by taking a longer path once out of their network. Unless you have a SLA, you're getting the worst service available. Oddly, with hot-potato routing, you even have a chance of some streams taking a shorter path when the network gets more congested (depending on topology, of course).
Also, congestion is hardly an issue with modern ISPs (in the US, tax dollars funded development of new optical backbones): http://www.wired.com/techbiz/media/news/2004/09/65121
IMHO, if I purchase a "bulk" link, I expect all traffic to be treated equally and the ISP to not cancel streams. I do like you're idea of users flagging traffic as bulk but wonder about the implementation, incentive and enforcement details.