QoS doesn’t work, except for one specific scenario:
Where QoS works is where one organisation controls both ends of a connection AND also tightly-defines and controls the applications:
- A fixed-broadband provider can protect IP telephony & IPTV on home broadband between central office & the home gateway.An enterprise can build a private network & prioritise its most important application(s), plus maybe a connection to a public cloud or UCaaS service.
- Mobile operators can tune a 4G network to prioritise VoLTE.
- Telco core and transport networks can apply differential QoS to particular wholesale customers, or to their own various retail requirements (eg enterprise users’ data vs. low-end consumers, or cell-site timing signals and backhaul vs. user data).
- Industrial process & control systems use a variety of special realtime connection protocols and networks. Vendors of “OT” (operational technology) tend to view IT/telecoms and TCP/IP as quaint. The IT/OT boundary is the real “edge”.
Source: [WayBack] Dean Bubley’s Disruptive Wireless: Debunking the Network QoS myth
Via: [WayBack] This is not news, but it’s worthwhile repeating… – Kristian Köhntopp – Google+:
This is not news, but it’s worthwhile repeating: it is actually cheaper to build a network that can carry the traffic than building a network that keeps quality promises on a backbone that is undersized or close to capacity. Overprovisioning works, everything else does not, economically as well as technically.
–jeroen
