Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

[ Create a new account ]

Comcast Defends Role As Internet Traffic Cop

Posted by CmdrTaco on Wed Feb 13, 2008 12:00 PM
from the this-is-going-to-get-worse-before-we-lose dept.
RCTrucker7 writes "Comcast said yesterday that it purposely slows down some traffic on its network, including some music and movie downloads, an admission that sparked more controversy in the debate over how much control network operators should have over the Internet. In a filing with the Federal Communications Commission, Comcast said such measures — which can slow the transfer of music or video between subscribers sharing files, for example — are necessary to ensure better flow of traffic over its network. In defending its actions, Comcast stepped into one of the technology industry's most divisive battles. Comcast argues that it should be able to direct traffic so networks don't get clogged; consumer groups and some Internet companies argue that the networks should not be permitted to block or slow users' access to the Web."

Related Stories

[+] Your Rights Online: New Legislation Could Eventually Lead to ISP Throttling Ban 191 comments
An anonymous reader writes "Comcast's response to the FCC may have triggered a new avenue of discussion on the subject of Net Neutrality. Rep. Ed Markey (D — Mass.), who chairs the House Subcommittee on Telecommunications and the Internet, introduced a bill yesterday whose end result could be the penalization of bandwidth throttling to paying customers. 'The bill, tentatively entitled the Internet Freedom Preservation Act of 2008, would not actually declare throttling illegal specifically. Instead, it would call upon the Federal Communications Commission to hold a hearing to determine whether or not throttling is a bad thing, and whether it has the right to take action to stop it.'"
[+] Comcast's FCC Filing Called Unfair, Not Good Enough 157 comments
Shoemaker brings us a follow-up to Comcast's recent defense of its traffic management procedures. The companies involved in the original FCC investigation are not satisfied with Comcast's response. From Ars Technica: "Comcast made an aggressive defense of its policies, claiming that it only resets P2P uploads made during peak times and when no download is also in progress. Free Press, BitTorrent, and Vuze all say that's not good enough. In a conference call, Vuze's general counsel Jay Monahan drew the starkest analogy. What Comcast is really doing, he said, wasn't at all comparable to limiting the number of cars that enter a highway. Instead, it was more like a horse race where the cable company owns one of the horses and the racetrack itself. By slowing down the horse of a competitor like Vuze, even for a few seconds, Comcast makes it harder for that horse to compete. 'Which horse would you bet on in a race like that?' asked Monahan."
[+] Technology: FCC Reports Comcast P2P Blocking Was More Widespread
bob charlton from 66 tips us to a ComputerWorld story about FCC Chairman Kevin Martin, who has testified that Comcast's P2P traffic management occurred even when network congestion wasn't an issue, contrary to the ISP's claims. After defending its actions and being investigated by the FCC over the past few months, Comcast has tried to repair its image by making nice with BitTorrent and working towards a P2P Bill of Rights. Quoting: "'It does not appear that this technique was used only to occasionally delay traffic at particular nodes suffering from network congestion at that time,' Martin told the Senate Commerce, Science and Transportation Committee. 'Based on testimony we've received thus far, this equipment was typically deployed over a wider geographic area or system, and is not even capable of knowing when an individual ... segment of the network is congested.'
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • Then they should not be protected from legal action regarding what flows over the network.

    Make that stipulation and they will stop in a heart beat.

    • by Aranykai (1053846) <lance@@@novabsi...com> on Wednesday February 13, @12:09PM (#22406908)
      Not a bad idea. If they are doing deep packet inspection to filter and slow traffic identified as peer to peer, are they not party responsible for the alleged infringment? I know if I offered a guy a ride in my car, then watched him shoot the person next to me, and continued to take him home, it would make me an accessory to murder
          • by Qzukk (229616) on Wednesday February 13, @12:59PM (#22407738)
            But in this case he paid you to drive him to the guy's house (located on Strained Analogy Place) and then home again. No force was applied.

            Well really it's more like I'm paying comcast to ship boxes back and forth from me to wherever they need to go, but rather than spending the money I give them for the service on buying more trucks or paying for gas, they just dump the boxes in a field somewhere, then run crying to mommy government when people demand to know why they're dumping boxes instead of buying enough trucks to handle the shipments.
            • by Thansal (999464) on Wednesday February 13, @01:21PM (#22408046)
              The argument here is this:

              ISPs are currently not liable for what illegal things their customers do with the service provided.
              One of the reasonings behind this is that they should not be mining traffic enough to know wth is going on. (IANAL, this is a bad explanation)
              Comcast says that they SHOULD be mining traffic to shape it and see wth is going on.
              Comcast should then be held liable for any illegal activities that they 'know' about because of this monitoring.

              get it now?

              Personally, I don't know if I agree or disagree. Mostly because I don't really understand how much monitoring they are doing, and just what the legal grounds are that protect the ISPs currently.

              On the note of them shaping traffic? I have not much of problem with Comcast shaping traffic as they see fit, well, at least now that they admit it. They are a company and can do what ever the hell they want so long as it is with in the law, and does not defraud/mislead customers/potential customers. I will never use their service, but I still think they are allowed to do what they want. Only problem is that many people have no choice, and there it IS a problem.
    • Then they should not be protected from legal action regarding what flows over the network.

      Make that stipulation and they will stop in a heart beat.
      Not at all. For cable internet service, an entire neighborhood typically shares the same chunk of bandwidth. Each cable modem has a bandwidth cap, but if you add the bandwidth for each subsriber in a neighborhood, it easily exceeds the available bandwidth. Also, there is a LOT less bandwidth alloted for upstream transmissions, so cable networks are a lot more sensitive to torrents, where up and down are roughly the same (or at least the should be). This has nothing to do with legality.

      So, from the cable company perspective, big downloaders affect the speeds of the entire neighborhood. I can certainly see their complaint.

      In fact, I have no problem with bandwidth limiting. When I grab torrents, I try to set reasonable bandwidth caps so as to not affect my neighbors (unless it is something that I need in a hurry, like when the latest Ubuntu is released).

      If Comcast wants to throttle the bandwidth on my torrents, so be it. I can live with that. But ABORTING a torrent is just plain nasty on their part. Delay the packets, fine. Drop a few packets, fine. But to inject an abort signal, dirty trick.
      • "..., it easily exceeds the available bandwidth"

        Then don't sell 'unlimited' sell a tiered system. Do NOT blame the consumer for your(Comcasts) bad business decisions.

        And if they were liable they would stop because no ISP wants to be liable for the consumers actions.

        • You are right about selling "unlimited" bandwidth. They do need to be more transparent with what they are offering.

          Their pricing is assuming that not all customers want to use their maximum available bandwidth at the same time, which is generally true. If they really DID beef up the system to handle ALL available bandwidth, then the price would likely double or more.

          Basicly, if you want cheaper prices, you have to make a sacrifice or two. If you really want dedicated bandwidth, pay for your own T3 to your house. Cable is marketed to typcial home user, where the use is rather bursty.

          This is kind of like an all-you-can-eat buffet having the local pro football team stopping by for supper after practice five times a week. After a while, the restaraunt starts to loose money. They then have three choices:
          1) Raise prices.
          2) Put limits on the service.
          3) Go out of business.
          None of the three are great options, #1 hurts everybody, not just the heavy users. #2 keeps the prices low for most, at the expense of the heavy users, and #3 hurts everybody in general.

          Note that I am NOT defending Comcast. I understand to need to do something about heavy usage. However, I am vehemently agains the WAY they have done things. Secret bandwidth caps and cancelling transfers are just plain decpetive and customer hostile. Now, if they had implemented a more reasonable policy, and actually advertised it, that would be good for everybody. I would be agreeable to temporary bandwith reductions (maybe 25% to 50%) for heavy useres during peak usage periods.

          To summarize: I understand the need for limits and bandwidth control. But, Comcast has done a crappy job of implementing it, and has done it in such a manner as to stir up customer wrath. They could have handled things MUCH better.
          • by Shakrai (717556) * on Wednesday February 13, @12:43PM (#22407464) Journal

            None of the three are great options, #1 hurts everybody, not just the heavy users. #2 keeps the prices low for most, at the expense of the heavy users, and #3 hurts everybody in general.

            Upgrading their network isn't an option?

            would be agreeable to temporary bandwith reductions (maybe 25% to 50%) for heavy useres during peak usage periods.

            I wouldn't be agreeable to those. The applications that are used by the minority of internet users today are going to become mainstream tomorrow. Everybody is slamming bittorrent but missing the point that internet video is probably going to be the next killer app.

            I don't know about you, but the typical "infringing" bittorrent download in my experience doesn't exceed 1 - 2Mbits because they usually have an unfavorable seeder/leecher ratio. Contrast that to Netflix instant view which consumes more then 2Mbits the entire time you are watching it.

            If they can't handle either of the above then how the hell are they going to handle HD video streams? Should we just give up on IP-Video because the cable companies say they can't handle it? Why did we even bother upgrading from dialup technology if they aren't going to be able to keep pace with the times?

              • by Shakrai (717556) * on Wednesday February 13, @01:24PM (#22408100) Journal

                The idea is that if 5% use 90% of the bandwidth its time to start adderssing that in a fair and honest manner.

                And what happens when the other 95% of your users discover internet video? Or do you think that these services are going to remain obscure forever?

          • by russ1337 (938915) on Wednesday February 13, @01:01PM (#22407764)

            This is kind of like an all-you-can-eat buffet having the local pro football team stopping by for supper after practice five times a week. After a while, the restaraunt starts to loose money. They then have three choices: 1) Raise prices. 2) Put limits on the service. 3) Go out of business. None of the three are great options, #1 hurts everybody, not just the heavy users. #2 keeps the prices low for most, at the expense of the heavy users, and #3 hurts everybody in general.
            I'm not sure I agree 100% with your analogy. It's more like you only have 100 seats, and every night paying customers are filling them, leaving cues of people waiting outside. The answer is get more seats -i.e spend some more of their 13 billion [google.com] gross profit on infrastructure to meet the growing demand.

            Interesting fact: The same number of Old people eat FAR more than a football team. This comes directly from a friend who ran a restaurant with a lunchtime buffet. I said to him I thought young people would take advantage, but he reckons young people tend to eat during the day, so 'all you can eat' is less. Old people however: They *plan* to go to an all you can eat and get the most for their money. They don't eat breakfast, and make that their only meal of the day - and they're usually have much larger stomachs from years of practice and riding those little cart things. He had busloads of sports teams stopping in, but was much more fearful of bus loads of oldies on a tour coach. - He tried serving more slowly, but they just stayed longer till they were full. - same as p2p. Someone downloading at their full rate will do so even if that rate is lower - just for longer. p2p downloading a movie will still 'eat' the same number of bits. If you want to sell more bandwidth, then you have to *have more to sell*. So more seats - more pipes.

      • by Shakrai (717556) * on Wednesday February 13, @12:33PM (#22407316) Journal

        For cable internet service, an entire neighborhood typically shares the same chunk of bandwidth

        And they can get around this by splitting their network into smaller nodes, devoting more channels on the HFC network to HSI services and investing in new technologies (DOCSIS 3.0) as they become available.

        Also, there is a LOT less bandwidth alloted for upstream transmissions, so cable networks are a lot more sensitive to torrents

        That's not as important as you might think. On DOCSIS 1.1 it's 38Mbits down/9Mbits up. On DOCSIS 2.0 it's 38/27. Even with DOCSIS 1.1 though it's not really a limitation because they typically have multiple upstream channels on the same node. In my area Roadrunner always uses the same channel/frequency for downstream (609mhz) but they have multiple upstream channels on each node that the cable modems are randomly assigned to. My neighbor is connected to the exact same cable drop as I am -- yet her modem is on a different upstream channel then mine is.

        I can certainly see their complaint.

        I can see their complaint too, but they need to be investing in upgrades. They don't have an interest in doing that though because the next killer-app on the internet is going to be video that directly competes with their own video offerings. They'll try to kill it by instituting bandwidth caps (like Time Warner is trying to do) and when that fails they will offer a "video-grade" service that costs a shitload more then a regular internet connection.

        Where would the internet be if nobody had invested in upgrading beyond dialup technology?

      • Not traffic shaping (Score:5, Informative)

        by Akaihiryuu (786040) on Wednesday February 13, @12:36PM (#22407362)
        For the trillionth time...what Comcast SAYS they are doing is NOT what they are doing. Traffic shaping is fine, as long as it does not differentiate by source. Even if they were just throttling or "slowing down" bittorrent, it wouldn't be nearly as bad as what they are doing. They are doing man-in-the-middle attacks on bittorrent connections, and actively impersonating one of the parties in the connection. This is actually illegal.
  • Slowdown (Score:5, Funny)

    by Stanistani (808333) on Wednesday February 13, @12:03PM (#22406796) Homepage Journal
    >Comcast... purposely slows down some traffic on its network, including some music and movie downloads...

    Perhaps Comcast will experience a 'slowdown' in its profits...

    At least it's all coming out in the open, instead of the issue being met with bland denials.
    • Re:Slowdown (Score:5, Insightful)

      by Pojut (1027544) on Wednesday February 13, @12:06PM (#22406866) Homepage
      That's just the thing though...it's not coming out in the open. Numerous studies have shown that they are in fact BLOCKING some types of traffic, which is backed up by countless consumer complaints both online and in print.

      Comcast seems to be hoping that your average everyday joe says "oh, they are just slowing it" and that be the end of it. Well, when downloading one version of Ubuntu was nearly 500k a second and then a few months later the next version downloaded at 2 KB per second from my house and roughly 400 KB from the same torrent at a friend's house that DIDN'T have comcast...yeah. I've seen it first hand. This isn't delaying or throttling...this is damn near blocking.

      Besides, injecting their own packets into the communication between my computer and another computer...shit, if I did that to two random people, I would be brought up on criminal charges.
        • Re:Slowdown (Score:5, Insightful)

          by Shakrai (717556) * on Wednesday February 13, @12:51PM (#22407614) Journal

          What makes you think Verizon (or whomever) won't throttle traffic on a FiOS network in the same way?

          Because Verizon's main source of revenue isn't derived from video or intellectual property. Because they are losing POTS customers left and right and need SOMETHING to use as a contrast between themselves and the cable cos that are kicking their ass. And because they've come out and said that they don't think bandwidth caps are the "right direction for us".

          I fucking loathe Verizon for some of their actions (especially those of Verizon Wireless) but they've been on the right side of this issue for as long as I can remember. If that changes they will deserve our scorn but I don't think it's fair to give it to them just yet.

  • by Aranykai (1053846) <lance@@@novabsi...com> on Wednesday February 13, @12:04PM (#22406832)
    The situation in most places is unfortunately this: There is ONE cable company offering high speed access, and perhaps ONE dsl company that servers your next door neighbor but not you. Theres not enough competition yet, so these idiotic companies stay in business simply because they have a monopoly.

    So, until that changes, theres no point in bitching and moaning every time some company admits to doing what we all know they are doing. You can always go back to dial-up...
  • Here we go again (Score:5, Insightful)

    by Trailer Trash (60756) on Wednesday February 13, @12:05PM (#22406846) Homepage
    There's a world of difference between "slowing traffic down" and spoofing rst packets. I don't mind them slowing down huge downloads or whatever to allow faster web browsing. That's not the issue at hand. I can't use bittorrent to download legal torrents. *That* is the issue at hand.

    Trying to change the subject isn't going to help them.
  • by TripMaster Monkey (862126) on Wednesday February 13, @12:09PM (#22406912)
    From TFA:

    The FCC prohibits network operators from blocking applications but opens the door to interpretation with a footnote in a policy statement that provides for an exemption for "reasonable management."

    So who determines what measures fall under the vague umbrella of "reasonable management"? Sure, Comcast can't block applications, but if they slow throughput from said applications down to a crawl, it constitutes a de facto block.

    This should be interesting to watch unfold, especially since I myself use Charter. ^_^
  • WSJ doesn't get it. (Score:5, Informative)

    by robkill (259732) on Wednesday February 13, @12:12PM (#22406958)
    It's distortions, statements, and mindsets like this [wsj.com] that have to be refuted.

    From the editorial:

    Big broadband companies are headed for a clash with Washington over whether consumers have a right to get as much as they want from the Internet, as fast as they want it, without paying extra for the privilege.
    The editorial goes on to conflate neutral treatment of packets with "neutral pricing" (their term for flat rate).
  • What is the web? (Score:5, Insightful)

    by ScentCone (795499) on Wednesday February 13, @12:14PM (#22406976)
    consumer groups and some Internet companies argue that the networks should not be permitted to block or slow users' access to the Web

    It's precisely so that what most users ARE trying to do (access "the web") will continuie to work that some giant, bandwidth-hogging apps are throttled. A crush of bittorrent traffic isn't, for most people, "the web." They want their mail to flow, and their CNN.com and facebook etc to work. The audience here on this message board are way, way outside the norm in terms of the type of traffic they'd rather burn bandwidth on. But here in my town yesterday and this morning, we had a nasty ice storm. I'm sure a lot of people were very glad to have a workable RDP session, and would certainly prefer that the chunk of router they're sharing with their fellow neighborhood broadband users didn't dry up because one kid three doors down is busy "sharing" his anime collection.
  • First post (Score:5, Funny)

    by Goffee71 (628501) on Wednesday February 13, @12:18PM (#22407054) Homepage
    First post man, woot, woot, wo**** *** Post intercepted by Comcast bandwidth preservation system! ACK*Metacheck - Checking for music, video, first post messages... DELAY*Post... 5... 4... 3... 2... 1... Service now resuming
  • by Hoplite3 (671379) on Wednesday February 13, @12:20PM (#22407096)
    Comcast: Sorry, our video-on-demand has used up all of the bandwidth. You can't watch that video-over-ip site now. Have you thought about getting a digital dvr from comcast? And while you're at it, why not a digital phone? We know you've been having problems with Skype...
  • Slowing down traffic (Score:5, Interesting)

    by CopaceticOpus (965603) on Wednesday February 13, @12:29PM (#22407254)
    Comcast is taking over my current cable provider, which is a less than pleasing fact given all the news about them lately. Still, I don't have a problem with them slowing down certain traffic, so long as certain conditions are met:

    1. They clearly disclose their policies about slowing traffic.
    2. They don't discriminate by specific domains, IPs, or traffic content. They should only discriminate by broad categories, such as prioritizing all http traffic over all p2p traffic.
    3. They don't interfere with packets, drop them, or modify them. They don't force connections to end as they have been accused of lately. They apply a speed limit and that is it.
    4. They only limit speeds when necessary based on network traffic. If the network can handle the current traffic load, don't slow anything down.

    It makes sense that perhaps my p2p download (of linux isos of course) shouldn't slow my neighbors' web surfing to a crawl. But it shouldn't be restricted if there is plenty of bandwidth available. And the Comcast Sports website definitely should have no advantage over espn.com.
  • by Animats (122034) on Wednesday February 13, @12:45PM (#22407510) Homepage

    Yes, they have to do some traffic shaping, but it can be done better.

    If the problem is bandwidth hogging by individual residential users, the answer is probably some variation on fair queuing. There's class-based fair queueing in most Cisco edge routers; it just has to be used correctly.

    I'd argue that, for residential connections, you need only two basic classes of service - high bandwidth, high latency, and low-bandwidth, low latency. VoIP and real-time game transactions should be low-bandwidth, low-latency; everything else should be high-bandwidth, high latency.

    For the low-bandwidth, low-latency streams, the per-IP-address queue should have priority, but the maximum number of buffers on the queue should be deliberately limited. If you try to send too much too fast with low latency, you lose packets. The high-bandwidth, high-latency streams have lower priority but can buffer up to available router memory. That works for streaming video, music piracy, and similar non-time-critical loads.

    Note that putting a high precedence on a high-bandwidth stream increases the packet loss rate, so there's no win in doing that. VoIP should request high precedence, but video should not. Clever game developers should put a high precedence on the traffic that needs it, while letting the background traffic that loads assets run at a lower precedence.

    High-bandwidth, low-latency is really needed only for real-time interactive video, and that's a premium service, because it really does need more capacity behind it.

    Multiple consumers on the same cable segment contend for upstream bandwidth at the router that connects the cable segment to the larger network. That's where fair queuing has to be applied. Similarly, it has to be applied at the router that connects the backbone to the downlink to the cable segment. Fair queuing is only useful at choke points where the number of streams is limited, but the cable modem industry has exactly that situation.

    The cable industry problem, I suspect, is that many of the routers out on the pole are still too dumb to do this. This is a killer for P2P traffic, which saturates upstream bandwidth. Upstream bandwidth has to be properly queued at the router on the pole; it can't be managed from the head end of the cable system. The Comcast "fake RST" interference with connections was an attempt to deal with the problem from the head end, which is the wrong answer.

    If the players in cable and DSL would agree on policy in this area, or the FCC mandated a standard, cable performance would degrade gracefully under heavy load. Without idiocy like faking connection resets.

    A standard on residential IP precedence handling would be a big help. If application developers could rely on the rules, VoIP traffic would work better. Games could get better latency; only some game traffic, the actual user action traffic, needs high precedence. The background loading of game assets should be running at lower priority. When there's a penalty for requesting too much bandwidth at high precedence, it gets used properly.

    From a technical perspective, that's how to do "network neutrality".

  • Port 25 egress (Score:5, Insightful)

    by nsayer (86181) * <nsayer AT kfu DOT com> on Wednesday February 13, @01:22PM (#22408054) Homepage
    Here's the issue. I'm all for net neutrality, myself. But a legitimate argument against it is that it would eliminate the ability of ISPs to block port 25 egress, which would lead to a multiplication of the number of spam bots out there. So do we say that ISPs must be net-neutral except for TCP port 25? It's the camel's nose.