I think what he's trying to say is that if they are able to throttle traffic (they're imposing a limit to how much traffic traverses their network) then they wouldn't have to push hard on data caps (they're imposing a financial penalty on the user, thus causing the user to self-impose how much traffic they will put on the network). Either way it achieves basically the same thing for them, less traffic on their equipment.
There are two aspects to this. First, they can place Netflix on the bottom of QoS, thus allowing all other traffic higher priority. Secondly, they can throttle Netflix to force a lower bit rate, aka, a lower quality picture which in turns lowers the bandwidth usage. If this was the case, what would the point of NN be? Drop the "s". My bad. Yes, its suppose to be GB.
All I want for them to do is to stop over compensating connections and causing massive buffer bloat. Almost all residential accounts I've encountered have a big amount of buffer bloat. Their own routers can't even handle it properly. Do a speedtest, and monitor a constant ping. When it gets to the upload, your latency goes through the roof. Only way to really get around it is to enable qos to only give you 80 percent of your connection
To me it sounds like they already have QoS enabled and that's why your ping goes through the roof during an upload. Unless you think your ICMP traffic should be the same priority as your upload.
