Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: dan <dandenson@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
	Herbert Wolverson <herberticus@gmail.com>,
	libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] routing protocols and daemons
Date: Fri, 28 Oct 2022 23:47:33 +0200	[thread overview]
Message-ID: <87r0yrvcwa.wl-jch@irif.fr> (raw)
In-Reply-To: <CAA_JP8WqKsn7R_34qWe15dyB-b8E2PEO2SJhNfuArCUwdqHudg@mail.gmail.com>

> What I think we're missing is the integration of network attributes and class
> of service.  For instance, user to 'internet' has 3 potential paths with each
> having these end-to-end latency, upload throughput, download throughput, and
> say 'quality' or packet loss.  Then having your QoS engine able to tag packets
> for how it perceives them to need routed and then have the routing engine pick
> routes based on availability.

We did implement something like that in Babel:

  https://datatracker.ietf.org/doc/html/draft-chouasne-babel-tos-specific

However, we never merged the code into babeld, due to lack of interest
from our users.  It turns out that it is seldom the case that there is
enough path diversity to make ToS-specific routing worthwile.

-- Juliusz
<

  parent reply	other threads:[~2022-10-28 21:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 20:29 Dave Taht
2022-10-26 20:53 ` Herbert Wolverson
2022-10-26 21:38   ` Dave Taht
2022-10-26 22:35     ` dan
2022-10-27 13:29       ` Herbert Wolverson
2022-10-27 15:29         ` Mark Steckel
2022-10-27 16:35           ` Dave Taht
2022-10-28 21:47       ` Juliusz Chroboczek [this message]
2022-10-28 21:45     ` Juliusz Chroboczek
2022-10-29  0:01       ` Dave Taht
2022-10-29  0:34         ` Dave Taht
2022-10-29  9:15         ` Juliusz Chroboczek
2022-10-29 13:48           ` Herbert Wolverson
2022-10-29 14:13             ` dan
2022-10-29 22:18               ` Juliusz Chroboczek
2022-10-30  0:09                 ` dan
2022-10-30 13:42                   ` Juliusz Chroboczek
2022-10-29 20:11             ` Juliusz Chroboczek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0yrvcwa.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=dandenson@gmail.com \
    --cc=dave.taht@gmail.com \
    --cc=herberticus@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox