Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Dave Taht <dave.taht@gmail.com>,
	Cake List <cake@lists.bufferbloat.net>,
	 bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] bbr vs all the aqms, cake winning...
Date: Fri, 27 Sep 2024 14:43:30 -0700 (PDT)	[thread overview]
Message-ID: <qpr4r78o-9640-ps6p-qpo2-94p0897298n5@ynat.uz> (raw)
In-Reply-To: <1727471439.369527853@apps.rackspace.com>

David P. Reed wrote:

> 2. Google is actively pushing QUIC to replace all of TCP, and its congestion 
> management is not even implemented much less tested - and BBR isn't relevant 
> to QUIC at all. Similarly, there's more and more WebRTC traffic and RTP 
> traffic - many SMB's are seeing very high percentages of such traffic at their 
> interconnect point. Why no consideration of that at all? These guys are living 
> in an ancient past - networking as it was 2 decades ago. Again, to do simple, 
> controlled research, that's OK. But dammit, why is the research community 
> focusing in their 20 year rearview mirror?

because they don't have real-world experience to know the difference between 
networking as it is taught (and how it may exist on a simple network with well 
behaved traffic) and the wild-wild-west of the public web that desktop/mobile 
users experience.

> I know there are no research funds available, unless you can use GPT or some 
> other "Generative AI" name in the title. Hell, I bet Comcast will even take 
> its own research budget and give it over to some projects with AI in the name 
> and GPUs in the hardware. (Jason Livingood, I feel sorry for you, but I'd 
> recommend turning your attention to optimizing audio chat services research 
> rather than congestion, if you want to save your job).

could the community try and produce 'traffic simulators' that implement these 
various protocols with a more realistic traffic pattern? something that can be 
turned up or down with a few presets of the mix that we can make available for 
the academics to use for their testing?

David Lang

  reply	other threads:[~2024-09-27 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 22:21 Dave Taht
2024-09-27 21:10 ` David P. Reed
2024-09-27 21:43   ` David Lang [this message]
2024-09-28 21:07     ` David P. Reed
2024-09-29  1:35       ` David Lang
2024-09-30 14:49         ` [Cake] [Bloat] " Livingood, Jason
2024-09-30 14:47   ` Juliusz Chroboczek

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

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

  git send-email \
    --in-reply-to=qpr4r78o-9640-ps6p-qpo2-94p0897298n5@ynat.uz \
    --to=david@lang.hm \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=dpreed@deepplum.com \
    /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