From: "Bjørn Ivar Teigen" <bjorn@domos.no>
To: Dave Taht <dave.taht@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Network quality for rocket scientists
Date: Mon, 14 Feb 2022 15:47:44 +0000 [thread overview]
Message-ID: <CAKf5G6KPcyy_wXBsdZ5RUKw6CwFHLHsYx7u+K3fW8Rtrb1NeSQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5UwWoUSoFwk00KNJDxSuxoZsxLZwvChJF54yzWoW7zYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
Thanks Dave, appreciate the feedback!
Sorry to not mention fair queuing explicitly here (I did link people to
bufferbloat.net though! Don't know if that makes up for it).
I agree it solves the bulk of these problems.
/Bjørn Ivar
On Mon, 14 Feb 2022 at 15:30, Dave Taht <dave.taht@gmail.com> wrote:
> It is wonderful to see another take on this subject from another
> perspective!
>
> Only nit is at the conclusion... the benefits of applying fair queuing
> to level out apparent jitter is well demonstrated at this point, for
> most kinds of traffic. Wish you'd mentioned it.
>
>
> On Mon, Feb 14, 2022 at 7:07 AM Bjørn Ivar Teigen <bjorn@domos.no> wrote:
> >
> > Hi everyone,
> >
> > I was inspired by the latest Starship presentation to write a piece on
> network quality in the language of rocket science. The blog can be found
> here:
> https://www.domos.no/news-updates/network-quality-for-rocket-scientists
> >
> > Cheers,
> > Bjørn Ivar Teigen
> >
> > --
> > Bjørn Ivar Teigen
> > Head of Research
> > +47 47335952 | bjorn@domos.no | www.domos.no
> > WiFi Slicing by Domos
> > _______________________________________________
> > Starlink mailing list
> > Starlink@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/starlink
>
>
>
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
>
--
Bjørn Ivar Teigen
Head of Research
+47 47335952 | bjorn@domos.no <name@domos.no> | www.domos.no
WiFi Slicing by Domos
[-- Attachment #2: Type: text/html, Size: 4590 bytes --]
next prev parent reply other threads:[~2022-02-14 15:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 15:07 Bjørn Ivar Teigen
2022-02-14 15:30 ` Dave Taht
2022-02-14 15:47 ` Bjørn Ivar Teigen [this message]
2022-02-14 16:06 ` Sebastian Moeller
2022-02-14 16:32 ` Bjørn Ivar Teigen
2022-02-14 17:15 ` Sebastian Moeller
2022-02-14 17:52 ` Bjørn Ivar Teigen
2022-02-14 18:38 ` Sebastian Moeller
2022-02-14 19:21 ` Bjørn Ivar Teigen
2022-02-24 14:23 ` [Starlink] FQ " Dave Taht
2022-02-24 14:44 ` Michael Richardson
2022-02-14 18:08 ` [Starlink] Network quality " Dave Collier-Brown
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKf5G6KPcyy_wXBsdZ5RUKw6CwFHLHsYx7u+K3fW8Rtrb1NeSQ@mail.gmail.com \
--to=bjorn@domos.no \
--cc=dave.taht@gmail.com \
--cc=starlink@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