Comment Re:It will get changed (Score 1) 350
The difference between fast lanes and throttling is, if you have paid for an advertised 10mbps internet connection and an ISP decides or is paid to serve traffic from sites/apps that compete with Amazon at 56k while leaving Amazon the full 10mbps, that's throttling. If you're paying for 10mbps connection and Amazon pays your ISP to allow traffic from their sites/apps to be fed to you at 50mbps, while their competitors and everyone else gets served at the advertised 10mbps, that's a fast-lane.
There's also a couple core 'fast-lane' scenarios.
One, a company could partner with an ISP, or an ISP could decide on their own to host servers locally on their network(s) to ensure optimum performance. This used to happen quite often in the early days of the internet when ISPs routinely hosted game, email and Usenet servers. Today it could be used for things like Netflix just as readily.
Another option is ISPs could simply exempt certain traffic from bandwidth caps.
While another is that certain traffic could be prioritized over other traffic. This could apply to everything from weather and traffic alerts to Disney's video service streams so that they aren't slowed by network congestion.
Thottling also has several potential implementations. There's the previous Amazon example I mentioned where companies essentially pay an ISP to sabotage the performance of their competitors, but there's also blanket throttling of things like bittorrent and Usenet traffic under the presumed mission of curbing piracy.