Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Nick Buraglio <buraglio@forwardingplane.net>
To: starlink@lists.bufferbloat.net, Dave Taht <dave.taht@gmail.com>
Subject: Re: [Starlink] congestion control info off the datapath
Date: Wed, 11 Aug 2021 12:59:27 -0500	[thread overview]
Message-ID: <CAGB08_cPYjFRLqG2OGadVeG9iray-pu7-xeHDS+D+oTBh9J6gA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6FKvw-A8nH8Py5Np-dnt+NJ=gN0oYGBYoYTrXF3PLXKQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3067 bytes --]

Brief introduction from me:
I'm Nick Buraglio.I've been building service provider networks in one way
or another since the 90s. My day job is on the planning and architecture
team for the Energy Sciences Network  (es.net). I've been doing HPC and LFN
networks for about 20 years now, having worked on almost every aspect from
security policy and implementation to fiber planning and optical wave
multiplexing, and most things in between (Layer 1 to Layer 8). My interest
in StarLink is mostly personal, as I have long been a strong proponent of
providing useful resources to underserved areas, but also from an
academic perspective in dealing with the technical pieces. Traffic
engineering, IPv6 proliferation, as well as performance testing are a big
part of my drivers and personal interests. Sometimes I do a podcast called
modem.show that talks about technical edge cases and deeper dive
take-aparts.

nb


On Sat, Jul 24, 2021 at 12:02 PM Dave Taht <dave.taht@gmail.com> wrote:

> One of our newer members is one of the authors of this:
>
> https://people.cs.rutgers.edu/~sn624/papers/ccp-sigcomm18.pdf
>
> I will reserve comment for now. I don't grok the intersection with ebpf as
> yet.
>
> Please? newer folk here, please briefly introduce yourselves and your
> interests in starlink's stuff?
> I very much approve of lurkers - even aliases! for those that cannot
> talk due to various NDAs, etc, but...
>
> For those here that don't know me already, well, I'm this renegade
> that has long lived
> outside of the vogon-industrial-military-academic complex with more
> key open source
> networking contributions to the world than most. These days I'm best
> known for the bufferbloat
> project and multiple congestion control algorithms/packet schedulers and
> AQMs
>
> ( Please put a copy of https://bufferbloat-and-beyond.net/ in your
> reading queue)
>
> but I have a long history going back to 1982 of kicking the tires of
> the internet,
> creating a RUD, and then fixing it.
>
> My own personal mission (as per the podcast) is to merely see starlink
> get sch_cake up on outbound
> on the dishy but long term I care a lot about just about anything
> networked and in
> space from here out to the edges fo the solar system. I'm really low
> on spare time
> at the moment personally, but if newer folk here would like to
> introduce themselves
> and point a link at a key paper of theirs or at their work in
> progress, perhaps the
> conversation will get rolling a bit more. We're still looking for more
> folkable  to do
> our measurement suite in particular.
>
> (we also need to put up the mailing list archive so far for new folk.
> Am short an
>  mailman expert for that if anyone has those chops?)
>
> --
> Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
>
> Dave Täht CTO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>

[-- Attachment #2: Type: text/html, Size: 4004 bytes --]

      parent reply	other threads:[~2021-08-11 17:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 17:02 Dave Taht
2021-07-26  5:26 ` Ulrich Speidel
2021-07-28 21:00 ` Andrew Crane
2021-07-29 21:31   ` Michael Richardson
2021-07-29 14:57 ` Jared Mauch
2021-07-31 13:04 ` Srinivas Narayana
2021-08-11 17:59 ` Nick Buraglio [this message]

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=CAGB08_cPYjFRLqG2OGadVeG9iray-pu7-xeHDS+D+oTBh9J6gA@mail.gmail.com \
    --to=buraglio@forwardingplane.net \
    --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