|
|
|
|
|
by josho
4420 days ago
|
|
> Can anyone think of any advantages to a non-neutral internet? Yes. In the early days there was a competing networking technology called ATM. It provided quality of service (QoS) aspects in the protocol. So, you could prioritize packets, e.g. protocols affected by latency could be prioritized (e.g. VOIP, gaming), while those that weren't could be given a low priority (FTP, email). The beauty of ATM was that on a relatively low bandwidth connection you could utilize all of your bandwidth and services like VOIP would still work beautifully. TCP/IP still today struggles with this. So, as a consumer, I'd be happy to pay for QoS so that my VOIP packets had an expressway on my 2Mbps connection. However, that ship (for many) has sailed. With my largely under utilized 50Mbps connection there is no reason to pay for QoS because we've largely solved latency by throwing bandwidth at the problem. However, with the approach that the FCC/comcast/et al are taking, I see no benefit. |
|
That's what non-neutral means. QoS is different, that's applications behaving themselves. BitTorrent, for instance, led to the development of uTP (micro transport protocol). One of its nicest features for torrent users is that it will slow itself down now in response to congestion and play nice with other network-using processes on the client side.
Putting this into the underlying connection like ATM did just means that you at least have to pick a default QoS and hopefully applications/systems pick a sensible assignment for the traffic. Rather than the default being to treat every connection as equal.