Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] congestion control info off the datapath
Date: Thu, 29 Jul 2021 17:31:54 -0400	[thread overview]
Message-ID: <2362.1627594314@localhost> (raw)
In-Reply-To: <CAP4ODMdF-6s4sRYL7fPe5r_2NDA4YPrRi30NDB7_Ctp4F+6ncA@mail.gmail.com>

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


< Please? newer folk here, please briefly introduce yourselves and your
< interests in starlink's stuff?

I live in downtown Ottawa, and I have VDSL2 (because the other options have
no IPv6, and are massively bufferbloated).

But, my relatives choose to live in partially off the grid (at the edge of
the grid?), eat "organic" and drive hundreds of kilometers a week for work.
(I walk to the store, am mostly car-free, and think vegetables that consume
huge amounts of CO2 to get to me can never be more healthy for the planet).

I care about Starlink because it might let my relatives stop driving,
and because it likely will give the Canadian bufferbloated duopoly a serious challenge.

But, it's gotta be real terminal-to-terminal, or it will just result in more
"bent fiber" pervasive attacks .

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide





[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2021-07-29 21:31 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 [this message]
2021-07-29 14:57 ` Jared Mauch
2021-07-31 13:04 ` Srinivas Narayana
2021-08-11 17:59 ` Nick Buraglio

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=2362.1627594314@localhost \
    --to=mcr+ietf@sandelman.ca \
    --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