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

> found babel, corresponded with (and frankly thoroughly annoyed) the
> author,

Being said author, I can confirm that you did thoroughly annoy me.  But
then, you also made me think.

> Babel is so simple that toke wrote a near complete implementation from
> the spec, in python, during a string of extremely boring IETF
> meetings, over the course of a week. He later took on the bird port.

This is not correct.  Babel was first reimplemented in Python during two
nights during an IETF meeting by Markus Stenberg.  As to Toke, he did the
BIRD reimplementation in C during a Battlemesh meeting, and it took him
a whole four days.  I later did a minimal implementation in C, which
compiled to 20kB of x86 code.

> I forget what happened to toke's python version).

Markus Stenberg's.  It's still available, but fairly obsolete due to
advances in babeld and BIRD.

  https://github.com/fingon/pybabel

> Althea is using babel and fq_codel in their blockchain routing thing
> (I reserve comment), and I don't know where else, besides as part of
> wireguard tunnels, babel is being used today.

Now that Babel is no longer a legitimate research project, the main user
and main source of funding for Babel are Nexedi, who use it in their
distributed cloud

  https://www.nexedi.com/

But I agree with you, Dave, Babel did not take over the world.  The main
reason, I suspect, is that OSPF is very good, and that most people are
happy enough with it.

Notwithstanding that, we're still maintaining both the standalone babeld
and Toke's BIRD module, and we've been busy extending the protocol with
source-specific routing, with v4-via-v6 routing, with MAC protection.

-- Juliusz

  parent reply	other threads:[~2022-10-28 21:45 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
2022-10-28 21:45     ` Juliusz Chroboczek [this message]
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=87sfj7vczj.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --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