Because priority in a network is a scarce resource and there are situations where people would like to pay for it -- VOIP, video calling, gaming.
If turning on your faucet took an average of twenty minutes before the water showed up you'd probably want a high-cost low-latency spigot in case of a fire.
Nobody cares if an ISP wants to offer 2 "packages":
1. High latency, high bandwidth
2. Low latency, low bandwidth
Just like the metaphor of a water pipe, an ISP could offer "normal" where the water takes 20 minutes, or "fast" where it takes a second, but you have to pay 10x or have a much lower limit.
What NN is all about is preventing the ISP from saying HOW you are using the data. In the "water" analogy it would be like your water company saying you can ONLY use their "fast" water in their proprietary "soup making system", then they slow down all other water if they detect you are using it in any non-compliant pots.
I'm more than fine with an ISP that wants to offer a special low-latency VOIP option, but when they slow down all their competitors VOIP services and only allow you to get their VOIP service with low-latency, then it's a problem. Or the all too real possibility of Comcast allowing something like HULU to not apply to the data-caps, while not offering that option to Netflix, Youtube, Amazon Prime Video, or even your own startup or self-hosted option.
That's what I want my government protecting me against, that's the kind of thing that should be heavily regulated.
How do you feel about the middle ground where you pay a fixed price and your bandwidth/latency is determined by the application? VOIP gets low-bandwidth low-latency, web surfing gets the middle ground, and video streaming gets high-latency high-bandwidth with the expectation that over a large enough population that the usage of each type will roughly average out.
I know this forum is full of people who want total control of everything but I would bet this would provide a better experience since it doesn't have to be managed by the customer.
> Or the all too real possibility of Comcast allowing something like HULU to not apply to the data-caps
This doesn't technically fall under NN but I agree it's pretty scummy. I think it's a tough argument to make the ISPs shouldn't be allowed to do this though. If Hulu wants to make a deal with an ISP where they pay for their customer's data usage and pay more to be exclusive I don't see why that should be forbidden.
An example outside of ISPs. Spotify used to integrate Musixmatch into their app which would otherwise cost users $12/year. I wouldn't feel comfortable saying that Spotify can't make an exclusive deal or that Musixmatch must allow GPM to integrate with them as well.
>How do you feel about the middle ground where you pay a fixed price and your bandwidth/latency is determined by the application?
I'm perfectly okay, as long as you are using the word "application" as a synonym for "type" and not as another word for "service or platform".
In other words, it's okay if VOIP service is prioritized via QoS rules, much of the internet as we know it won't work without this kind of thing, and it's a good thing for everyone involved.
What's NOT okay is when ComcastVOIP is allowed low-bandwidth, low-latency, but GoogleVOIP isn't. Or when each VOIP company needs to "apply" to get approved for the special consideration, or there are additional "rules" that have to be followed that deal with where the data is going, what it's doing, or how it's being used (like saying "VOIP that is used for business must pay more" is not okay in my book).
>This doesn't technically fall under NN but I agree it's pretty scummy. I think it's a tough argument to make the ISPs shouldn't be allowed to do this though. If Hulu wants to make a deal with an ISP where they pay for their customer's data usage and pay more to be exclusive I don't see why that should be forbidden.
It may not, but it absolutely should. At this point nothing falls under NN as it's not a law any more, so I'm not buying this "excuse" any more.
un-limiting one companies data is the same as limiting all other companies data in my opinion.
Again, if that data-cap-bypassing stuff works on a protocol level (as in VOIP data doesn't count toward your limit), then i'm perfectly fine with it, but when it deals with who owns the server, what content it's displaying, and who you are paying to get the service/data, then it should be heavily regulated.
>I wouldn't feel comfortable saying that Spotify can't make an exclusive deal or that Musixmatch must allow GPM to integrate with them as well.
neither would I, but that's not what i'm worried about. Bundling and deals including other services is fine, but what isn't is when those bundles bleed over into the actual data being sent. Just like how i'm fine if my water company provides a free water filter service with their water service. But when they start interfering with other companies water filters, or start making their core service (the water itself) cheaper when used with their provided water filter, then it's in what I consider anti-competitive territory.
And I guess that's the core of the problem I have with things like "unlimited for one service" deals. It's not just including another service with your internet, it's the ISP actively changing the price of their own core service when you use another unrelated service.
While I understand that a policy prohibiting this might end up slowing or stopping some innovative or new ways of providing internet access to people how they want it, I truly feel that the upsides of not allowing the ISPs to play gatekeeper (whether intentional or otherwise) will greatly outweigh the lost innovation.
I also want to point out that i'm not calling for these "shady" practices to be outright illegal, just that they should be "heavily regulated". Meaning there should be quite a lot of oversight, time should be spent determining if there is a conflict of interest or if the specific practice will end up harming competition or innovation.
If turning on your faucet took an average of twenty minutes before the water showed up you'd probably want a high-cost low-latency spigot in case of a fire.