[Bloat] Cascading proportionality, not fairness.

[David Collier-Brown <davec-b@rogers.com>]

Jim Gettys <jg@freedesktop.org> wrote:
> at an ISP, you must to be "fair" between customers; it is best to leave
> the judgement of "fairness" at finer granularity (e.g. host and TCP flows)
> to the points closer to the customer's systems, so that they can enforce
> whatever definition of "fair" they need to themselves.

I too hate the overloaded term, and would argue it's just wrong.
Instead, we are discussing /proportionality/, and what we know about the
ISP is very generally applicable.

The ISP deliver proportional amounts of latency (or freedom from
latency) to a community of customer devices, one of which might be a
home router.

The router delivers the upstream services proportionally to a kid's
machine, to dad and mom, and to the TV or perhaps the dedicated skype phone.

The latter two devices have some fixed requirements: a certain number of
frames per second, a certain number of seconds of audio and the like.
This is the hardest, but it has limits. Delivering much more than X
frames a second over a long period is wasted effort. Delivering less
than X for a short period yields dropouts. Therefor such a service can
be statically provisioned, and rejected if there are already too many
sessions to leave enough resources meet its needs.

Fq_codel only has to deliver its usual guarantees: statically
oversubscribing the link isn't its problem. The router does have to have
the smarts to not commit logical suicide, or over-commit too greatly in
cases where an over-commitment is allowable, but that's a different
problem than fq addresses. That's an issue of capacity planning.

Similarly, delivering a guaranteed minimum of service to each subscriber
isn't a fair queuing or a fairness problem. It's one of setting a policy
and enforcing it. It, like the audio/video problem is one of capacity
planning, and proportionality.  The parents can say "same service to
anyone", or they can say "no A/V during homework hours". Outside of
homework hours, they can say "gaming takes precedence over the PVR, but
not over skype", and so on.

On the kid's machine, we still want to use fq to keep downloads from
messing up gaming and A/V, but the kid has to set the policy as to who
ultimately wins.

Jim is right: this really isn't fairness.  I'd reserve that term for
fq_codel and friends, call all the capacity planning considerations
"proportionality". I'd also assume every node in the net thinks like an
ISP and wants to start off by handing out equal response times to its
entire set of "customers", and change that only if explicitly told to.

--dave