Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>,
	Rpm <rpm@lists.bufferbloat.net>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>
Subject: [Starlink] net neutrality back in the news
Date: Wed, 27 Sep 2023 11:21:05 -0700	[thread overview]
Message-ID: <CAA93jw6Hex+piOSz2UygrUYcrCC8qoJA6NfL-vTtnZsP7o8N+g@mail.gmail.com> (raw)

Jason just did a beautiful thread as to what was the original source
of the network neutrality
bittorrent vs voip bufferbloat blowup.

https://twitter.com/jlivingood/status/1707078242857849244

Seeing all the political activity tied onto it since (and now again)
reminds of two families at war about an incident that had happened
generations and generations before, where the two sides no longer
remembered why they hated each other so, but just went on hating, and
not forgiving, and not moving on.

Yes, there are entirely separate and additional NN issues, but the
technical problem of providing common carriage between two very
different network application types (voip/gaming vs file transfer) is
thoroughly solved now, and if only all sides recognised at least this
much, and made peace over it, and worked together to deploy those
solutions, maybe, just maybe, we could find mutually satisfactory
solutions to the other problems that plague the internet today, like
security, and the ipv6 rollout.

If anyone here knows anyone more political, still vibrating with 10+
years of outrage about NN on this fronts, on one side or the other, if
you could sit them down, over a beer, and try to explain that at the
start it was a technical problem nobody understood at the time, maybe
that would help.

-- 
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos

             reply	other threads:[~2023-09-27 18:21 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 18:21 Dave Taht [this message]
2023-09-28  3:33 ` [Starlink] [Rpm] " rjmcmahon
2023-09-28  6:06   ` Dave Taht
2023-10-01 17:08     ` Sebastian Moeller
2023-10-05 19:22       ` Dave Taht
2023-09-28  6:25 ` Sebastian Moeller
2023-09-28  6:36   ` Gert Doering
2023-09-28  7:14     ` Sebastian Moeller
2023-09-28  7:33       ` Gert Doering
2023-09-28  7:38         ` Sebastian Moeller
2023-09-28 16:38   ` Dave Taht
2023-09-28 16:52     ` Livingood, Jason
2023-09-28 17:04       ` rjmcmahon
2023-09-28 19:31     ` Sebastian Moeller
2023-09-28 19:39       ` Dave Taht
2023-09-28 20:08         ` [Starlink] [LibreQoS] " dan
2023-09-28 20:18           ` Dave Taht
2023-09-29 19:00             ` [Starlink] Getting Google to index. was:Re: " Rodney W. Grimes
2023-09-28 20:36           ` [Starlink] " Jeremy Austin
2023-09-28 20:54             ` [Starlink] [Bloat] " Livingood, Jason
2023-09-28 20:48           ` [Starlink] " Livingood, Jason
2023-09-28 22:19             ` [Starlink] [Bloat] " David Lang
2023-09-29  4:54               ` Jonathan Morton
2023-09-29 12:28                 ` [Starlink] [Rpm] [Bloat] [LibreQoS] " Rich Brown
2023-09-29 16:15                   ` dan
2023-09-30 12:00                     ` Frantisek Borsik
2023-09-30 12:19                       ` Sebastian Moeller
2023-09-30 12:42                         ` Vint Cerf
2023-09-30 14:07                           ` Sebastian Moeller
2023-09-30 14:41                         ` Mike Conlow
     [not found]                           ` <4129491C-FFC7-4E5E-A5A4-8CBE9B5C5255@gmx.de>
2023-09-30 15:23                             ` [Starlink] [LibreQoS] [Rpm] [Bloat] " Dave Taht
2023-09-30 17:35                               ` Dave Taht
2023-09-30 21:57                                 ` [Starlink] New email list: NNagain for network neutrality Dave Taht
2023-10-04 22:19                           ` [Starlink] [Bloat] [Rpm] [LibreQoS] net neutrality back in the news Michael Richardson
2023-09-29  6:24               ` [Starlink] [Rpm] [Bloat] " Sebastian Moeller
2023-09-29  6:31                 ` Gert Doering
2023-09-29  7:07                   ` Sebastian Moeller
2023-09-28 22:25           ` [Starlink] [Bloat] [LibreQoS] [Rpm] " David Lang
2023-09-28 17:10   ` [Starlink] [Bloat] " Livingood, Jason
2023-09-28 19:30     ` Dave Taht
2023-09-28 20:05     ` Sebastian Moeller
2023-09-28 21:07       ` [Starlink] [EXTERNAL] " Livingood, Jason
2023-09-28 21:08         ` Livingood, Jason
2023-09-29  8:56         ` [Starlink] [Bloat] [EXTERNAL] " Erik Auerswald

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=CAA93jw6Hex+piOSz2UygrUYcrCC8qoJA6NfL-vTtnZsP7o8N+g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=jhs@mojatatu.com \
    --cc=rpm@lists.bufferbloat.net \
    --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