And yes, there's a whole list of individual token offenses ISPs have committed that people will spam out when you point this out, but it doesn't change the fact that the fears and horrors propping up this movement on a large scale do not exist.
And yes, there's a whole list of individual token offenses ISPs have committed that people will spam out when you point this out, but it doesn't change the fact that the fears and horrors propping up this movement on a large scale do not exist.
No they aren't; many of them are things that the FCC responded to in if years of enforcing net neutrality principles through case by case actions, such as mobile and fixed broadband ISPs blocking services that competed with their offerings, and blocking other lawful services or content, sometimes for political reasons.
> Nobody offers "fast lanes" now, is planning to introduce them in the near future, and nobody offered fast lanes before the regulation was put into place. And yet, it's the top net neutrality supporter panic call.
“Fast lanes” have gotten blown out of proportion because of discussion of a possible weakness in an earlier draft of the 2015 order. They aren't actually a concern for the non-neutral net, they are a concern about a potential end-run around a net regulated for neutrality but with a loophole. Unfortunately, a popular distortion side that that draft was designed by enemies of neutrality rather than people trying to save it who might have designed the draft insufficiently tightly, and so “fast lanes” have become associated with the goals and plans of the anti-neutrality camp rather than just a potential weakness in a no-longer-relevant pro-neutrality draft regulation.
I mostly blame John Oliver for that.
Although, in point of fact, edge provider preference much like fast lanes exists in the form of zero rating, which is occurring in the mobile broadband space. It's not precisely the same thing, but had much the same issue.
But for example, the paid fast lane situation... does not currently exist. The whole "you might have to pay for the social media package to see this tweet" nonsense? Not only doesn't actually exist but has no chance of even remotely existing.
"Fast lanes" as a general product aren't likely going to be offers on the company home page, they're going to be in the private peering agreements they have with larger companies. This has already happened. [Netflix had to pay Comcast](https://consumerist.com/2014/02/23/netflix-agrees-to-pay-com...), and [Comcast throttled their VoIP competitor Vonage](https://www.wired.com/2006/03/comcast_throttling_vonage_user...). Vonage and Netflix started working again but the why was never made public. It seems likely that paying for fast lanes was involved. These aren't the cold hard facts we'd like to have about what exactly happened, but they're clear violations of Net Neutrality that were resolved ambiguously.
As far as negative effects in general, beyond fast lanes, there's more than a few examples:
* [AT&T blocked FaceTime](https://www.savetheinternet.com/att-facetime) * [Verizon blocked Google Wallet](http://money.cnn.com/2011/12/06/technology/verizon_blocks_go...) * [Verizon throttles video](https://arstechnica.com/tech-policy/2017/07/verizons-throttl...) * And [a lot more](https://www.freepress.net/blog/2017/04/25/net-neutrality-vio...).
The violations are often subtle, and haven't always affected everyone, but the negative effects of the lack of NN are not hypothetical.
Netflix gets free colocation from ISPs through Netflix Open Connect. (Hilariously, Netflix claims it "offers this for free to ISPs", whereas if you realize it is colocation, it is obviously Netflix should be paying for it.) Net neutrality cripples ISPs' negotiating position with Netflix (since it prevents ISPs from controlling their traffic in other ways), which protects their special treatment, ironically, since only Netflix has the market share to dictate terms to ISPs. If you made a startup video competitor, you'd have to pay for the service net neutrality guarantees Netflix gets for free. ISPs must host Netflix's boxes for free, or get hit by a deluge of upstream Netflix traffic.
FaceTime is an excellent example of a reasonable reason a provider may wish to get involved in content for performance reasons: Everyone switching to video chat would have a massive and immediate impact on that ISP's network traffic. With "unlimited data" models, ISPs don't necessarily get increased revenue to offset massively increased bandwidth use and network congestion. It's understandable why AT&T moved here. I actually prefer a pay-as-you-go data model, because it incentivizes carriers to provide neutral data as fast as possible: The more you use, the more money they make.
Verizon blocking Google Wallet stands in a long line of incidents where good PR has reversed the blame. ;) Google refused to allow competitors' payment systems from using the secure element in phones... a market Google has monopoly control of. Eventually, Verizon's hardline stance on being able to offer a competing service forced Google to rework Wallet to be more fair, and not get an exclusive security feature everyone else was prohibited from using. Of course, Google just moved to kill their competition another way: They bought out Softcard/ISIS and turned it into Android Pay. (And kicked Windows Mobile Softcard users to the curb too, hurting a second competitor in the process! Efficiency!) NFC payment competitors to Android Pay on Android phones like Samsung Pay only exist today thanks to Verizon's hardline stance.
You’re argument is probably false. The fears are real we’ve seen ISPs provide tired bandwidth in the past. Everything except BitTorrent traffic was in the fast lane and BitTorrent traffic was in the slow lane.
Today this might be a bit more interesting of a case since a lot of software patchers from major protocols now use the BitTorrent protocol to patch software. I believe Star Citizen does, Blizzard games may as well. Windows Update at the very least now uses a similar system, though I don't know if it's specifically BitTorrent based or not.
Most BitTorrent traffic may not be, but that's a matter of content not protocol. Most of the people physically located in the death row wing of a particular prison may be condemned convicts but if a government says it's not going to kill anyone not duly sentenced to execution and just drops a bomb on that wing, killing mostly condemned criminals, but also a few correctional officers and service workers, the action would be clearly out of line with the commitment.
If you're going to throttle a protocol to keep your network optimized for legitimate users, crippling a piracy protocol seems pretty practical, wouldn't you say?