Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Dave Täht" <davet@teklibre.net>
Cc: Ulrich Speidel <u.speidel@auckland.ac.nz>,
	starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink Digest, Vol 12, Issue 6
Date: Fri, 4 Mar 2022 12:10:34 -0500	[thread overview]
Message-ID: <CAA93jw4HWzrVxyD01M3AsWtnsdT3-LFv8KeuSVvNmAMOxS8YCw@mail.gmail.com> (raw)
In-Reply-To: <20220304170811.GA16708@mail.taht.net>

please see: https://twitter.com/capacitymedia/status/1499777574058274823
as for means to track some of those disruptions.

On Fri, Mar 4, 2022 at 12:08 PM Dave Täht <davet@teklibre.net> wrote:
>
> Taking control of 1/3 the electrical power potentially disrupts
> most communication technologies. Distributed power collection
> and generation is also identifiable from above.
>
> There has been a very good discussion about preserving communications
> and infrastructure on the nanog mailing list, with among other things
> ripe and ICANNs refusal to disrupt the dns on behalf of any party.
>
> However the cloud providers and major companies are coming down
> hard against russia.
>
> These three aspects of a fresh war in europe I confess to not
> having thought about much before this week.
>
> A fourth is that I know very little about the other countries
> formerly of the USSR and their infrastructures and alignments,
> and have been trying to find out, as I think those are the
> major wild cards moving forward through this week.
>
>
> _______________________________________________
> 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

  reply	other threads:[~2022-03-04 17:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1943.1646344903.1267.starlink@lists.bufferbloat.net>
2022-03-03 23:47 ` David P. Reed
2022-03-04  5:06   ` Ulrich Speidel
2022-03-04  7:00     ` Mike Puchol
2022-03-04  8:41       ` David Lang
2022-03-04  9:44         ` Ulrich Speidel
2022-03-04 17:07           ` Larry Press
2022-03-04 23:58             ` Ulrich Speidel
2022-03-04 17:08           ` Dave Täht
2022-03-04 17:10             ` Dave Taht [this message]
2022-03-04 18:14           ` David Lang
2022-03-04 18:21             ` Ben Greear
2022-03-04 18:30               ` David Lang
2022-03-05  0:14             ` Ulrich Speidel
2022-03-05  6:38               ` Dick Roy
2022-03-05  9:42                 ` Ulrich Speidel
2022-03-05 10:10                   ` David Lang
2022-03-05 18:26                   ` Dick Roy
2022-03-05 15:25               ` Larry Press
2022-03-06  1:50                 ` Ulrich Speidel

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=CAA93jw4HWzrVxyD01M3AsWtnsdT3-LFv8KeuSVvNmAMOxS8YCw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=davet@teklibre.net \
    --cc=starlink@lists.bufferbloat.net \
    --cc=u.speidel@auckland.ac.nz \
    /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