From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eugene Y Chang <eugene.chang@ieee.org>
Cc: David Lang <david@lang.hm>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
Colin_Higbie <CHigbie1@Higbie.name>
Subject: Re: [Starlink] Itʼs the Latency, FCC
Date: Thu, 02 May 2024 15:17:17 -0400 [thread overview]
Message-ID: <30070.1714677437@obiwan.sandelman.ca> (raw)
In-Reply-To: <79C02ABB-B2A6-4B4D-98F4-6540D3F96EBB@ieee.org>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
Eugene Y Chang via Starlink <starlink@lists.bufferbloat.net> wrote:
> Shouldn’t we create a demo to show the solution? To show is more
> effective than to debate. It is impossible to explain to some people.
There were demos of fq_codel doing a visible *to the eye* improvement on
straight browsing at a number of IETF Hackathons. The kit involved was an
entire CMTS+CM head-end. The improvements were due to DNS not having to wait.
--
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: 515 bytes --]
next prev parent reply other threads:[~2024-05-02 19:17 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2773.1714488060.1074.starlink@lists.bufferbloat.net>
2024-04-30 18:05 ` [Starlink] It’s " Colin_Higbie
2024-04-30 19:04 ` Eugene Y Chang
2024-05-01 0:36 ` David Lang
2024-05-01 1:30 ` [Starlink] Itʼs " Eugene Y Chang
2024-05-01 1:52 ` Jim Forster
2024-05-01 3:59 ` Eugene Y Chang
2024-05-01 4:12 ` David Lang
2024-05-01 10:15 ` Frantisek Borsik
2024-05-01 18:51 ` Eugene Y Chang
2024-05-01 19:18 ` David Lang
2024-05-01 21:11 ` Frantisek Borsik
2024-05-01 22:10 ` Eugene Y Chang
2024-05-01 21:12 ` Eugene Y Chang
2024-05-01 21:27 ` Sebastian Moeller
2024-05-01 22:19 ` Eugene Y Chang
2024-05-06 11:25 ` [Starlink] The "reasons" that bufferbloat isn't a problem Rich Brown
2024-05-06 12:11 ` Dave Collier-Brown
2024-05-07 0:43 ` Eugene Y Chang
2024-05-07 12:05 ` Dave Collier-Brown
[not found] ` <CAJUtOOhH3oPDCyo=mk=kwzm5DiFp7OZPiFu+0MzajTQqps==_g@mail.gmail.com>
2024-05-06 19:47 ` Rich Brown
2024-05-07 0:38 ` Eugene Y Chang
2024-05-07 10:50 ` Rich Brown
2024-05-08 1:48 ` Dave Taht
2024-05-08 7:58 ` Frantisek Borsik
2024-05-08 8:01 ` Frantisek Borsik
2024-05-08 18:29 ` Eugene Y Chang
2024-06-04 18:19 ` Stuart Cheshire
2024-06-04 20:06 ` Sauli Kiviranta
2024-06-04 20:58 ` Eugene Y Chang
2024-06-05 11:36 ` Alexandre Petrescu
2024-06-05 13:08 ` Aidan Van Dyk
2024-06-05 13:28 ` Alexandre Petrescu
2024-06-05 13:40 ` Gert Doering
2024-06-05 13:43 ` Alexandre Petrescu
2024-06-05 14:16 ` David Lang
2024-06-05 15:10 ` Sebastian Moeller
2024-06-05 16:21 ` Alexandre Petrescu
2024-06-05 19:17 ` Eugene Y Chang
2024-06-04 23:03 ` Rich Brown
2024-06-04 23:36 ` [Starlink] Consumer Reportes (was: The "reasons" that bufferbloat isn't a problem) David Collier-Brown
2024-06-06 17:51 ` [Starlink] The "reasons" that bufferbloat isn't a problem Stuart Cheshire
2024-06-07 2:28 ` Dave Taht
2024-06-07 5:36 ` Sebastian Moeller
2024-06-07 7:51 ` Gert Doering
2024-05-02 19:17 ` Michael Richardson [this message]
2024-05-02 9:09 ` [Starlink] It’s the Latency, FCC Alexandre Petrescu
2024-05-02 9:28 ` Ulrich Speidel
2024-04-30 20:05 ` Sebastian Moeller
2024-05-02 9:21 ` Alexandre Petrescu
[not found] <mailman.2785.1714507537.1074.starlink@lists.bufferbloat.net>
2024-04-30 20:48 ` Colin Higbie
2024-05-01 0:51 ` David Lang
2024-05-01 2:46 ` [Starlink] Itʼs " Colin_Higbie
2024-05-01 3:18 ` David Lang
2024-05-01 3:38 ` Colin_Higbie
2024-05-01 3:51 ` David Lang
2024-05-01 4:16 ` Colin_Higbie
2024-05-01 7:40 ` David Lang
2024-05-01 15:13 ` Colin_Higbie
2024-05-01 3:54 ` James Forster
[not found] <mailman.11.1710518402.17089.starlink@lists.bufferbloat.net>
2024-03-15 18:32 ` [Starlink] It’s " Colin Higbie
2024-03-15 18:41 ` Colin_Higbie
2024-03-15 19:53 ` Spencer Sevilla
2024-03-15 23:07 ` David Lang
2024-03-16 18:45 ` [Starlink] Itʼs " Colin_Higbie
2024-03-16 19:09 ` Sebastian Moeller
2024-03-16 19:26 ` Colin_Higbie
2024-03-16 19:45 ` Sebastian Moeller
2024-03-16 23:05 ` David Lang
2024-04-30 0:39 ` [Starlink] It’s " David Lang
2024-04-30 1:30 ` [Starlink] Itʼs " Colin_Higbie
2024-04-30 2:16 ` David Lang
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=30070.1714677437@obiwan.sandelman.ca \
--to=mcr+ietf@sandelman.ca \
--cc=CHigbie1@Higbie.name \
--cc=david@lang.hm \
--cc=eugene.chang@ieee.org \
--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