3 ms·
> The way QoS works for VoLTE for example, is not by putting application layer knowledge at the link layer. Instead the services that activate and route a phone
by fennecfoxen 5y ago
> The way QoS works for VoLTE for example, is not by putting application layer knowledge at the link layer. Instead the services that activate and route a phone call, have the ability to send a rule, called a traffic flow template, to the underlying LTE network.
So you need to put link-layer knowledge in the application layer, and on anything in between the app and the network link. Your app needs some API to do this, and it surely isn't a transparent connect(2). And if you want full support, then when hook up your LTE access point to a consumer-grade wifi-router — or maybe your business's router, as a backup if the primary link fails — you'll need some way to relay support there as well, and to your desktop software running Windows, and to OSX and Linux, and your Docker container.
It's all doable, it's just a massive amount of coordination in exactly the way "throw me some packets!" isn't.
- kevin_nisbet 5y ago> So you need to put link-layer knowledge in the application layer, and on anything in between the app and the network link. Your app needs some API to do this, and it surely isn't a transparent connect(2). Well let's not lose sight of the problem being solved here. If I'm a phone operator, I don't want someone downloading bittorrent on the same cell to cause packet loss and garble my phone call so it's unusable. Throwing some packets over the fence doesn't tend to work so well when there are constraints on the magic tubes.