Cox Gets Aggressive With Traffic Shaping

from the taunting-the-fcc dept

In a move that's basically baiting the FCC and Congress to see if they will act, Cox has announced that it's going to experiment with rather aggressive traffic shaping, granting priority to bits that it feels have a great priority. Why Cox gets to describe what gets a priority and what doesn't seems pretty questionable. Cox is also the company that implemented a three strikes policy on file sharing without telling anyone.

To be honest, this seems like a really tone deaf move by Cox -- and I'd imagine that plenty of telcos and cable companies are pissed off about Cox calling extra attention to the topic right now. There's been plenty of talk of new net neutrality regulations in Congress, and with Cox putting the issue so squarely on the table, it's as if they're begging for such regulations (or at least to be slapped down by the FCC). You would think they would at least wait until it wasn't an issue getting so much attention before drawing extra scrutiny and daring regulators to act.

Filed Under: net neutrality, regulation, traffic shaping
Companies: cox, fcc

Reader Comments

Subscribe: RSS

View by: Time | Thread

  1. icon
    GeneralEmergency (profile), 28 Jan 2009 @ 3:10pm

    The a-ha momment...

    This could represent the beginning of a whole new kind of ISP.

    Imagine a "TDISP" or Tunnel Destination ISP, (or better yet for marketing purposes a "Privacy Management ISP",) whom you contract with who serves to anchor the far end of an always on VPN session that tunnels through your RAT-BASTARD, PACKET SPYING, RIAA LACKEY, TRAFFIC SHAPING, ASSHAT primary ISP like Comcast or AT$T and releases your spring-fresh, unmolested packets onto the internet. As A. L. Flanagan correctly points out above, we can all encrypt our traffic, but usually this is done at the application level. To REALLY slap these invasive ISPs in the face, we need to encrypt all of our traffic.

    I suppose an ISP could then block or throttle traffic to these end points but how would they distinguish your connection as a TDISP customer or an Employee?? What if the TDISP was a collective, customer owned enterprise?

    If my ISP blocked my VPN connection to my employer, there would be hell to pay.


Add Your Comment

Have a Techdirt Account? Sign in now. Want one? Register here

Subscribe to the Techdirt Daily newsletter

Comment Options:

  • Use markdown. Use plain text.
  • Remember name/email/url (set a cookie)

Follow Techdirt
Techdirt Gear
Show Now: Takedown
Report this ad  |  Hide Techdirt ads
Essential Reading
Techdirt Deals
Report this ad  |  Hide Techdirt ads
Techdirt Insider Chat
Report this ad  |  Hide Techdirt ads
Recent Stories
Report this ad  |  Hide Techdirt ads


Email This

This feature is only available to registered users. Register or sign in to use it.