Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Jim Forster <jim@connectivitycap.com>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>,
	codel@lists.bufferbloat.net,
	libreqos <libreqos@lists.bufferbloat.net>,
	l4s-discuss@ietf.org, starlink@lists.bufferbloat.net
Subject: [LibreQoS] Re: [Starlink] Re: Keynote: QoE/QoS - Bandwidth Is A Lie! at WISPAPALOOZA 2025 (October 16)
Date: Fri, 7 Nov 2025 11:19:03 -0500	[thread overview]
Message-ID: <2036296F-1567-4B66-BD8C-3AB49EBD5AA3@connectivitycap.com> (raw)
In-Reply-To: <CAJUtOOhzJAymDiKsnRPho80B8GZ4wzd8W7FWccS=uhiQPd3KOg@mail.gmail.com>

Frank — I’m watching it now, Great job pulling this group together, and nice, balanced opening statement. 

  — Jim

> On Nov 7, 2025, at 5:53 AM, Frantisek Borsik via Starlink <starlink@lists.bufferbloat.net> wrote:
> 
> 
> Recording of our QoE/QoS panel discussion is out! It was really great and
> believe you will like it:
> 
> https://www.youtube.com/watch?v=T1VET0VYQ6c
> 
> We have touch bandwidth, L4S, Starlink and more.
> 
> Here are the slides with additional reading:
> https://docs.google.com/presentation/d/1ML0I3Av3DCtQDiP8Djr_YGH2r4-UDZP25VEk-xyJcZE/edit?slide=id.p#slide=id.p
> 
> We hope to continue this conversation into more practical, demo-like
> environment of sort, that we can see at IETF Hackathon and used to see in
> the early WISPA event days, with Animal Farm.


  reply	other threads:[~2025-11-07 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 20:24 [LibreQoS] Re: [Starlink] " James Forster
2025-09-30 20:48 ` Frantisek Borsik
2025-10-01 19:24   ` dan
2025-10-01 21:32     ` Frantisek Borsik
2025-11-07 10:53       ` Frantisek Borsik
2025-11-07 16:19         ` Jim Forster [this message]
2025-11-07 17:52           ` [LibreQoS] Re: [Starlink] Re: " J Pan
2025-11-07 18:55             ` [LibreQoS] Re: [Starlink] " Jim Forster
2025-11-07 19:50               ` J Pan
2025-11-08 16:00                 ` dan
2025-11-08 17:03                   ` J Pan
2025-11-08 18:11                     ` [LibreQoS] Re: [Starlink] " Sebastian Moeller

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/libreqos.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2036296F-1567-4B66-BD8C-3AB49EBD5AA3@connectivitycap.com \
    --to=jim@connectivitycap.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=frantisek.borsik@gmail.com \
    --cc=l4s-discuss@ietf.org \
    --cc=libreqos@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