ISP Breaking Net Neutrality? The FCC's Got a Complaint Form For That
Presto Vivace writes with news from The Consumerist that the FCC has updated its consumer help center with a revamped form for complaining about an unsatisfactory ISP. From the article: Among the issues concerned consumers can complain about, the form now contains "open internet/net neutrality," right there alphabetically between "interference" and "privacy." So what, specifically, qualifies as a net neutrality violation you can complain about? The FCC has guidance for that, too. In general, paraphrased, it's a problem if there's:
Blocking: ISPs may not block access to any lawful content, apps, services, or devices.
Throttling: ISPs may not slow down or degrade lawful internet traffic from any content, apps, sites, services, or devices.
Paid prioritization: ISPs may not enter into agreements to prioritize and benefit some lawful internet traffic over the rest of it on their networks.
Blocking: ISPs may not block access to any lawful content, apps, services, or devices.
Throttling: ISPs may not slow down or degrade lawful internet traffic from any content, apps, sites, services, or devices.
Paid prioritization: ISPs may not enter into agreements to prioritize and benefit some lawful internet traffic over the rest of it on their networks.
I really want to know so I can get people flagged for making false statements to that effect. We don't have a firewall at all on our internet customers. Its wide open and has been for years. We found throttling ports was self defeating in that the torrent hoarders used encryption and other means to hide their activity anyway. The filter we had was actually causing an additional 30ms of latency and I have missed it at all.
Almost no ISPs use any kind of AQMs. You could do a high sample trace route and watch for jitter and avg ping increases. In general, a health link's avg ping should not be more than 1-5ms over the minimum. If you do enough samples in a trace route, you should be able to see which hops are causing issues. If your ISP is doing high quality shaping along with an AQM, it would be much harder to watch for congestion because latency should be quite stable. Then you need to somehow measure a route's bandwidth.
The good news is most decent traffic shaping algorithms are very CPU intensive relative to the amount of bandwidth an ISP's core network must handle and the algorithms do not scale well with the number isolated groups. In other words, you should be able to detect jitter and avg ping increases.