Re:Wikipedia Zero and Net Neutrality: Protecting the Interne...
by GauntletWizard on Sunday August 03, 2014 @02:51AM
(#8127287)
Yes; QOS has no place crossing the boundaries of a network segment - It should allow me to control the ingress and egress of my network, but be stripped before it gets to a network "trunk" like an ISP.
Further on that; If bandwidth on a segment is constrained, the ISP should divide it as fairly as possible, while also trying to maximize throughput. Each user should get an equal share, and if they're using less than that, the remainder should be apportioned to the other users evenly.
Re:Wikipedia Zero and Net Neutrality: Protecting the Interne...
by nitrogen on Sunday August 03, 2014 @02:57AM
(#8127295)
It seems to me that some level of either user-controlled QoS or congestion notification is desirable at the ISP level, since your software (e.g. Netflix, VoIP) might not know that the ISP network is congested, but you'd still prefer to tell your ISP's routers to prioritize the VoIP over the Netflix (within your allotted share of bandwidth, of course).
Re:Wikipedia Zero and Net Neutrality: Protecting the Interne...
by pessimizer on Sunday August 03, 2014 @08:06AM
(#8127718)
>QoS is a highly desirable feature of a network, iff you, the end user, control the QoS selection.
Agreed, although I think of that as something that I do at my own router, but that only covers my outbound. Being able to control what comes down to me would only be an improvement.
I've mentioned this strategy a few times before on HN, starting ~4 years ago:
https://news.ycombinator.com/item?id=2049784
https://news.ycombinator.com/item?id=4860164
https://news.ycombinator.com/item?id=4860180
https://news.ycombinator.com/item?id=7711264
https://news.ycombinator.com/item?id=7911677
https://news.ycombinator.com/item?id=8058319