Slashdot Mirror

← Back to Stories (view on slashdot.org)

Comcast Outlines New Broadband Policy

Posted by timothy on from the knowledge-is-power dept.

Slatterz writes "US cable provider Comcast has presented its long-term solution for managing broadband traffic. The new system is set at putting to bed a minor scandal that erupted around the company when it was found that Comcast deliberately limited traffic for certain applications. The company said that under its new system, traffic will be analyzed every fifteen minutes. Users who are found to be occupying large amounts of bandwidth will be placed at a lower priority for network access behind users with less bandwidth-intensive traffic. The new system will not replace or be related to the company's earlier installment of bandwidth caps, which limited a user's data intake to 250GB per month."

12 of 350 comments (clear)

  1. Dang... by Kid+Zero · · Score: 5, Insightful

    There are only two games in town: ATT's DSL (slow) and Comcast (Fast, but with strings).

    What's the point of having the internet when you can't do anything on it?

    1. Re:Dang... by Kadin2048 · · Score: 5, Insightful

      The solution then is to rate-limit at the router or TCP stack, or for applications to start being more careful about how much bandwidth they use -- just because a user has 6.0Mbps available for peak speed, doesn't mean that applications should assume that they can or should use as much of it as possible, all the time.

      P2P applications have had rate-limiting controls for a long time; it's probably about time for Skype and video-chat applications to have them too. Skype is particularly bad in this regard because it automatically defaults to the highest-quality codec that a connection supports. While this might make sense on fixed-bandwidth connections, it's not great for the majority of broadband connections, which have the capability of pushing a high peak speed, but shouldn't be expected to sustain that peak for very long. (And this isn't a bad thing or rare, either; lots of "real" internet connections are the same way. You can buy a 100Mb pipe because you occasionally need the full 100 megabits, even though you can't afford to saturate it 24/7. I'd wager most SLAed connections at .coms and .edus are like this.)

      In general, it's a pretty fair policy, especially because it only goes into effect when a neighborhood node starts to become congested. (Unlike their 250GB/mo cap and their old policy, which didn't care whether you were actually competing for resources with anyone else.) If I'm using huge amounts of bandwidth for Skype or video-chat, to the point where my neighbors are being affected even though they're just trying to check their mail and log off, they're not going to care what application I'm using. It's fundamentally no different, to anyone else in my neighborhood, if I'm taking up all the bandwidth on the upstream node with VoIP calls, Linux ISOs, or midget porn. They all have the same effect on my network neighbors, and all should get me throttled.

      What needs to happen, is applications need to get smarter about their bandwidth consumption. If a VoIP program finds itself getting throttled (increased latency), it should try dialing down its bandwidth usage -- by choosing a tighter codec, perhaps -- and seeing if the situation improves.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    2. Re:Dang... by B'Trey · · Score: 5, Informative

      Here's an email from one of Comcast's engineers recently sent to Dave Farber's Interesting People mailing list. It clarifies the policy quite well:

      From: "Livingood, Jason"
      Subject: Clarifying Misconceptions of the New Comcast Congestion Mgmt Syste

      Hi Dave

      I wanted to try to clear up a misconception about how the new Comcast congestion management system works. I believe we have both heard people complain that they fear that they will be unable to use their provisioned speeds during off-peak hours, for example, or at all times of the day, or that users are somehow throttled to a set speed. Neither of these two things are correct. Part of the problem appears to be confusion over how a user's traffic enters a lower priority QoS state, so I hope to clarify that here

      In order for any traffic to be placed in a lower priority state, there must first be relatively high utilization on a given CMTS port. A CMTS port is an upstream or downstream link, or interface, on the CMTS in our network. The CMTS is basically an access network router, with HFC interfaces on the subscriber side, and GigE interfaces on the WAN/Internet side. Today, on average, about 275 cable modems share the same downstream port, and about 100 cable modems share the same upstream port (see page 5 of Attachment B of our Future Practices filing with the FCC, available at http://downloads.comcast.net/docs/Attachment_B_Future_Practices.pdf). We define a utilization threshold for downstream and upstream separately. For downstream traffic, a port must average over 80% utilization for 15 minutes or more. For upstream traffic, a port must average over 70% utilization for 15 minutes or more

      When one of these threshold conditions has been met, we consider that individual port (not all ports on the CMTS) to be in a so-called Near Congestion State. This simply means that the pattern of usage is predictive of that network port approaching a point of high utilization, where congestion could soon occur. Then, and only then, do we search the most recent 15 minutes of user traffic on that specific port, in order to determine if a user has consumed more that 70% of their provisioned speed for greater than 15 minutes. By provisioned speed, we mean the "up to" or "burst to" speed of their service tier. This is typically something like (1) 8Mbps downstream / 2Mbps upstream or (2) 6Mbps downstream / 1Mbps upstream

      So how does this work in action? Let's say that a downstream port has been at 85% utilization for more than 15 minutes. That specific downstream port is identified as being in a Near Congestion State since it exceeded an average of 80% over that time. We then look at the downstream usage of the ~275 cable modems using that downstream port. That port has a mix of users that have been provisioned either 8Mbps or 6Mbps, so 70% of their provisioned speed would be either 5.6Mbps or 4.2Mbps, respectively. So let's use the example of a user with 8Mbps/2Mbps service on this port. In order for their traffic to be marked with a lower priority on this downstream port, they must be consuming 5.6Mbps in the downstream direction for 15 minutes or more, while said port is highly utilized

      Once that condition has been met, that user's downstream traffic is now tagged with the lower priority QoS level. This will have *no* effect whatsoever on the traffic of that user, until such time as an actual congestion moment subsequently occurs (IF it even occurs). Should congestion subsequently occur, traffic with a higher priority is handled first, followed by lower priority (and this is not a throttle to X speed)

      I hope this helps. You can others can feel free to contact me directly if you have any questions
      Regards
      Jason Livingood
        - Engineering & Technical Operation

      For verification, you can find the original in the IP Archives. Date of the email is 2008-09-24 12:37:35

      --

      "The legitimate powers of government extend only to such acts as are injurious to others." Thomas Jefferson.

    3. Re:Dang... by skroops · · Score: 5, Insightful

      So this only hurts the dumb.

      Every bittorrent client I've ever used has easy to set upstream and downstream limits. Simply set your upstream and downstream to 65% and 75% of you're max connection and you'll never be slowed down.

    4. Re:Dang... by Anonymous Coward · · Score: 5, Funny

      never? you'll be slowed down by 25-35%, all the time ^_^

    5. Re:Dang... by ChuBie · · Score: 5, Insightful

      I hate to say it, but the above email sounds fair.

      I just hope Comcast implements it as laid out in their email.

  2. Legal use of big bandwidth paying the price... by eepok · · Score: 5, Insightful

    1) User pays for their own broadband access (cost of bandwidth). $$
    2) User pay for Netflix a service contract (which includes more bandwidth costs). $$
    3) User uses the bandwidth for which he paid by watching streaming movies and suddenly the movies don't load anymore... because it takes a bit of bandwidth to download movies.
    4) User buys digital movies from Amazon et al? $$
    5) User gets kicked from ISP because he paid enough to use what bandwidth he used.

    Sounds like a scam to me!

    Why offer high speed internet if you're not going to provide high speed internet?

  3. Cool! by BigBlueOx · · Score: 5, Funny

    So when NBC or ABC/ESPN/Disney or CBS/Viacom or Sony Pictures or Time Warner comes to me and says "Look at our really great new streaming movie/TV/video service! Pay only $29.95/mo and you can watch anything anyTIME ALL THE TIME!!!", I'll say "Sorry. Can't do streaming video. It puts me in the Comcast doghouse. I just play Nethack."?

    Ok

  4. Re:What...? by Fulcrum+of+Evil · · Score: 5, Insightful

    So suddenly any large use of BW is illegal? Way to distract from the point.

    --
    "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
  5. Re:Pretty sure this was in place for a while now by Z34107 · · Score: 5, Informative

    ...As my cable modem service slows to a CRAWL if I have a torrent open for more than 20-25 minutes. Once you terminate the d/l, it stays that way for 20-25 minutes or so... The throttling is so severe that DNS requests time-out... Not really that awesome of a solution, IMO.

    That's probably not throttling. Same thing happens to my cousin, and the same thing happens to me (though not as bad.) Every seed and leech in that torrent is still hammering your connection and timing out, requesting what parts you're advertising. At least that's what my firewall logs seem to suggest.

    Power cycle your cable modem and get a new IP address. Your former cloud will no longer be DDoSing your connection.

    --
    DATABASE WOW WOW
  6. Re:What...? by HiVizDiver · · Score: 5, Insightful

    I'm not sure why this was modded -1, Flamebait. The parent makes a good point - as I posted in a semi-related thread a couple of days ago, I rented a movie from the Playstation store as an HD rental. The filesize was 6275 MB (around 6 GB). This download definitely saturated my connection, as I had the whole thing in around 2 hours. I realize that Comcast has a way of telling (or maybe they don't, who knows) P2P traffic from a straight download, but ultimately the question is the same - if I'm blasting a 6 GB file download in an hour or two, does that piss them off? Because I'm going to be mad if it does, since it was a perfectly legitimate use of the service that I'm paying for (vs. some "gray area" activities).

  7. Re:What...? by vux984 · · Score: 5, Insightful

    You could always upgrade to a class of service that doesn't have the caps, or has caps in line with what you require.

    A system in which people like you who use 100s or thousands of gigabytes per month pay more than people who use 10 or 15 a year seems entirely fair to me.