From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Dave Taht <dave.taht@gmail.com>,
Sebastian Moeller <moeller0@gmx.de>,
libreqos <libreqos@lists.bufferbloat.net>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>,
Jamal Hadi Salim <jhs@mojatatu.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Starlink] [Rpm] net neutrality back in the news
Date: Thu, 28 Sep 2023 16:52:00 +0000 [thread overview]
Message-ID: <3A241A2C-4D92-4F6B-A155-27AF43675ECD@cable.comcast.com> (raw)
In-Reply-To: <CAA93jw4T_XGieTDH+oU8Z0beNkVLRS=d4-P=BiOKg_9=uH86dg@mail.gmail.com>
On 9/28/23, 12:45, "Starlink on behalf of Dave Taht via Starlink" <starlink-bounces@lists.bufferbloat.net <mailto:starlink-bounces@lists.bufferbloat.net> on behalf of starlink@lists.bufferbloat.net <mailto:starlink@lists.bufferbloat.net>> wrote:
> It would be nice, if as a (dis)organisation... the bufferbloat team
could focus on somehow getting both sides of the network neutrality
debate deeplying understanding the technological problem their
pre-conceptions face, and the (now readily available and inexpensive)
solutions that could be deployed, by most ISPs, over a weekend. We are
regularly bringing up a few thousand people a week on libreqos (that
we know of), and then of course, there are all the home routers and
CPE that are increasingly capable of doing the right thing.
[JL] The FCC will soon (maybe today) open a notice of proposed rulemaking - aka NPRM. That process provides an opportunity for anyone to file and filings from technical experts are always highly valued.
next prev parent reply other threads:[~2023-09-28 16:52 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 18:21 [Bloat] " Dave Taht
2023-09-28 3:33 ` [Bloat] [Rpm] " rjmcmahon
2023-09-28 6:06 ` Dave Taht
2023-10-01 17:08 ` [Bloat] [Starlink] " Sebastian Moeller
2023-10-05 19:22 ` Dave Taht
2023-09-28 6:25 ` [Bloat] " Sebastian Moeller
[not found] ` <ZRUe_5uiRJyDxb9Z@Space.Net>
2023-09-28 7:14 ` [Bloat] [Starlink] " Sebastian Moeller
[not found] ` <ZRUsLalRicJpQoXH@Space.Net>
2023-09-28 7:38 ` Sebastian Moeller
2023-09-28 16:38 ` [Bloat] " Dave Taht
2023-09-28 16:52 ` Livingood, Jason [this message]
2023-09-28 17:04 ` [Bloat] [Rpm] [Starlink] " rjmcmahon
2023-09-28 19:31 ` [Bloat] [Rpm] " Sebastian Moeller
2023-09-28 19:39 ` Dave Taht
2023-09-28 20:08 ` [Bloat] [LibreQoS] " dan
2023-09-28 20:18 ` Dave Taht
2023-09-29 19:00 ` [Bloat] Getting Google to index. was:Re: [Starlink] " Rodney W. Grimes
2023-09-28 20:36 ` [Bloat] " Jeremy Austin
2023-09-28 20:54 ` Livingood, Jason
2023-09-28 20:48 ` [Bloat] [Starlink] " Livingood, Jason
2023-09-28 22:19 ` David Lang
2023-09-29 4:54 ` Jonathan Morton
2023-09-29 12:28 ` [Bloat] [Rpm] [Starlink] [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 ` [Bloat] [Starlink] [Rpm] " Vint Cerf
2023-09-30 14:07 ` Sebastian Moeller
2023-09-30 14:28 ` [Bloat] [Rpm] [Starlink] " Jan Ceuleers
2023-09-30 14:35 ` Sebastian Moeller
2023-09-30 14:41 ` Mike Conlow
2023-09-30 15:20 ` Sebastian Moeller
2023-09-30 15:23 ` [Bloat] [LibreQoS] [Rpm] [Starlink] " Dave Taht
2023-09-30 17:35 ` Dave Taht
2023-09-30 21:57 ` [Bloat] New email list: NNagain for network neutrality Dave Taht
2023-10-04 22:19 ` [Bloat] [Rpm] [Starlink] [LibreQoS] net neutrality back in the news Michael Richardson
2023-09-29 6:24 ` Sebastian Moeller
[not found] ` <ZRZvMLtKhkd6-16m@Space.Net>
2023-09-29 7:07 ` [Bloat] [Starlink] [Rpm] " Sebastian Moeller
2023-09-28 22:25 ` [Bloat] [LibreQoS] [Rpm] " David Lang
2023-09-28 17:10 ` [Bloat] " Livingood, Jason
2023-09-28 19:30 ` Dave Taht
2023-09-28 20:05 ` Sebastian Moeller
2023-09-28 21:07 ` [Bloat] [EXTERNAL] " Livingood, Jason
2023-09-28 21:08 ` Livingood, Jason
2023-09-29 8:56 ` 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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A241A2C-4D92-4F6B-A155-27AF43675ECD@cable.comcast.com \
--to=jason_livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=jhs@mojatatu.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--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