Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: OS wish-list feature - QoS marking preference  (Read 275 times)

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 7453
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
OS wish-list feature - QoS marking preference
« on: January 03, 2019, 08:50:38 AM »

I wish Santa would add a feature to my o/s next year. An app looks up a domain name. The IP address results come back. Now that app and certain domain names (or ip addresses), plus protocols and ports match a rule defined in a database owned by the o/s. When there is a hit on the tuple of app + ip + protocol + port, the o/s QoS-marks outgoing packets and if possible arranges for the incoming packets to get QoS-marked as well. The o/s puts a QoS-aware queuing system in front of outbound packets too.

It should be possible in a settings UI for the user to override apps and add QoS to apps after the fact, so that even if they do not support it, QoS-marking gets applied by the o/s, without the app knowing.

I would love it if Apple were to do this. Of course doing it in a router would be better and having a standard router control protocol for this would be excellent. And then the ultimate would be ISPs, unless it doesn’t matter and routers could effectively manage downstream traffic even from the ‘wrong end’.
« Last Edit: January 03, 2019, 09:01:24 AM by Weaver »
Logged

CarlT

  • Kitizen
  • ****
  • Posts: 1153
  • Next generation network design and deployment
Re: OS wish-list feature - QoS marking preference
« Reply #1 on: January 03, 2019, 11:37:46 AM »

I would suggest hell will freeze over before Apple implement this. Linux can and does already do most of it, though.

Various proprietary software does too, especially in the software defined feature set, but QoS policy downstream is decided on by the router there, not CPE.

Router control protocol communicating with ISPs not happening, though there are signalling facilities already present on ISP-managed kit on customer sites. These are, however, for flows originating from that kit, or the part of the flow in that direction, the remote kit makes its own decision on how to handle outbound traffic if it sees the flow first.

A wishlist indeed.
Logged
-----
Deploying better networks, not just faster ones.
 

anything