Slashdot Mirror


CRTC Says Rogers Violating Federal Net Neutrality Rules

beaverdownunder writes "A Canadian CRTC investigation in partnership with Cisco has found that Rogers Communications has violated federal net-neutrality rules by throttling connections related to P2P applications. Rogers has until noon on February 3rd to reply to the accusations or face a hearing." Quoting the letter sent to Rogers: "On the basis of our evidence to date, any traffic from an unidentified time-sensitive application making use of P2P ports will be throttled resulting in noticeable degradation of such traffic."

14 of 165 comments (clear)

  1. Finally by iONiUM · · Score: 4, Informative

    Rogers (and Bell) have been abusing their customers since the beginning, this is just another example. I hope the CRTC sticks it to them, and I really hope this becomes very public. Please share this everywhere, so the hatred towards this duopoly in Canada can grow even more.

    And yes, I use Rogers, because I literally don't have another choice. And they definitely throttle torrents, during "prime" hours, which is apparently 8am-11pm.

    1. Re:Finally by atlasdropperofworlds · · Score: 5, Interesting

      So does Shaw. I get bizarre behavior with Skype (distortions, connection problems) at non-peak hours. If I run speed test at those times, both my download and upload capacity max out. It's all very annoying. I also have inside information that Shaw has had throttling equipment in for almost 10 years now, and that they do use it.

    2. Re:Finally by Anonymous Coward · · Score: 5, Informative

      RTFA before you get too excited. They do throttle bit torrent, openly, because it is legal for them to do so. FTFA:

      The Telecommunications Act and CRTC regulations allow throttling of peer-to-peer file sharing programs like BitTorrent, but not of time-sensitive internet traffic like video chatting or gaming.

    3. Re:Finally by phoenix_rizzen · · Score: 3, Interesting

      And it's done on a per-IP basis, not a per-household or per-account basis. Since you get (at least) 2 dynamic IPs per Shaw Internet account, all you have to do is separate your "normal" traffic from your "excessive" traffic.

      For example, we setup to routers at our house, with a switch between them and the cable router. They each get a different IP via DHCP.

      Torrents and other "bandwidth hogs" go through one router. All other traffic goes through the other router.

      That way, when they throttle all traffic through one IP, it doesn't affect our normal web browsing activities.

    4. Re:Finally by compro01 · · Score: 3, Insightful

      Your experience is probably because their 100 Mb is only available as "unlimited" (500GB cap).

      --
      upon the advice of my lawyer, i have no sig at this time
  2. Someone's gonna get fired! by TheSpoom · · Score: 3, Insightful

    From the CRTC, that is. Apparently they didn't get the memo stating who their masters were.

    --
    It's better to vote for what you want and not get it than to vote for what you don't want and get it.
    - E. Debs
  3. Re:It should be throttled. by danbob999 · · Score: 5, Insightful

    Why?

    Let say we both pay $40/month for our internet connection.
    I use only 1GB P2P/month, and you use only 1GB VoIP/month. We both have no other traffic.

    Why should you get priority over me? I paid as much as you and deserve what I paid for, at full speed.
    If an ISP can't offer unlimited traffic for $40/month, then they only have to put data usage caps (preferably only during peak time since that's when there is congestion).
    Until I bust my usage cap, I should be able to do what I want without being throttled.

  4. Re:It should be throttled. by Anonymous Coward · · Score: 5, Insightful

    Because a VOIP phone call will suck if the network is congested. Whereas your P2P download can take an extra 30 seconds to keep my call quality good. FYI, I worked on SNA and traffic prioritization was baked into the protocol for exactly these purposes -- TCP/IP is actually quite a dumb protocol in this regard.

  5. Re:It should be throttled. by tonywong · · Score: 4, Informative

    Why is this common sense? Might need to download a manual shouldn't have a lower priority than your need to talk to Gramma over the interwebs. If your portion of the service you contracted was throttled because _you_ wanted it, that's fine, but my service shouldn't be throttled to your needs. Besides, I manage my QoS with my own firewall, and which packets get prioritized are none of your business, nor should it be my provider's unless I ask them to.

  6. Oh noes! by Anonymous Coward · · Score: 3, Insightful

    A hearing!

    Come back to me when there is actually a penalty involved.

  7. Re:It should be throttled. by Anonymous Coward · · Score: 4, Informative

    Because VoIP is sensitive to things like latency spikes. P2P isn't. If the packets are given the correct priorities, your download finishes in just about the same amount of time while the other person has a nice audio quality. If the VoIP packets aren't given priority your download won't be significantly faster (the same amount of data is still being sent over the same pipes), but the call quality will be abismal.

  8. Re:It should be throttled. by Anonymous Coward · · Score: 5, Insightful

    But the network is congested because the provider has sold what they don't have. Why you think any other users should be punished because of that fact is beyond me. Fact is, overselling with 10-20:1 ratios on network connections is no longer tenable.

  9. Missing Information by magamiako1 · · Score: 5, Informative

    A lot of the comments here are missing some information, so let's put it this way:

    The throttling argument started a while ago when gamers detected problems with World of Warcraft on the Rogers network. In fact, Blizzard Entertainment personally spent a ridiculous amount of resources to try contact Rogers but Rogers spent the whole time insisting that their throttling was not affecting WoW, even though gamers and Blizzard had found concrete proof otherwise.

    Interestingly enough, if you switch your connection to a wholesale distributors of Rogers Internet, TekSavvy, in the affected areas, the throttling problem goes away--even though it's going over the same network backbone as if you were provided a Rogers pipe directly.

    Blizzard also attempted to limit the ports used for WoW back to the original game ports (3724), but this was only a temporary solution as they wanted the other connections to help with reliability.

    Long story short, a WoW community member living in Canada kind of spearheaded this and has been a part of this from the absolute very beginning.

    It grew to the point that the CRTC has investigated itself, and this is where we stand now.

  10. Re:It should be throttled. by tepples · · Score: 5, Insightful

    If your VoIP call suck, then switch to a better ISP.

    How is this possible if only one wired broadband ISP serves your area?