General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd: [iccrg] Musings on the future of Internet Congestion Control
Date: Wed, 15 Jun 2022 10:49:22 -0700	[thread overview]
Message-ID: <CAA93jw6bE2NYSHeAcqL+w_j0Mv4KMxRWJR_AwRVT+vGCYiXg7A@mail.gmail.com> (raw)
In-Reply-To: <6458C1E6-14CB-4A36-8BB3-740525755A95@ifi.uio.no>

---------- Forwarded message ---------
From: Michael Welzl <michawe@ifi.uio.no>
Date: Wed, Jun 15, 2022 at 1:02 AM
Subject: [iccrg] Musings on the future of Internet Congestion Control
To: <iccrg@irtf.org>
Cc: Peyman Teymoori <peymant@ifi.uio.no>, Md Safiqul Islam
<safiquli@ifi.uio.no>, Hutchison, David <d.hutchison@lancaster.ac.uk>,
Stein Gjessing <steing@ifi.uio.no>


Dear ICCRGers,

We just got a paper accepted that I wanted to share:
Michael Welzl, Peyman Teymoori, Safiqul Islam, David Hutchison, Stein
Gjessing: "Future Internet Congestion Control: The Diminishing
Feedback Problem", accepted for publication in IEEE Communications
Magazine, 2022.

The preprint is available at:
https://arxiv.org/abs/2206.06642
I thought that it could provoke an interesting discussion in this group.

Figures 4 and 5 in this paper show that, across the world, network
links do not just become "faster”: the range between the low end and
the high end grows too.
This, I think, is problematic for a global end-to-end standard - e.g.,
it means that we cannot simply keep scaling IW along forever (or, if
we do, utilization will decline more and more).

So, we ask: what is the way ahead?  Should congestion control really
stay end-to-end?

Cheers,
Michael

_______________________________________________
iccrg mailing list
iccrg@irtf.org
https://www.irtf.org/mailman/listinfo/iccrg


-- 
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC

       reply	other threads:[~2022-06-15 17:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6458C1E6-14CB-4A36-8BB3-740525755A95@ifi.uio.no>
2022-06-15 17:49 ` Dave Taht [this message]
2022-06-19 16:53   ` [Bloat] " Sebastian Moeller
2022-06-20 12:58     ` Michael Welzl
2022-07-10 17:27       ` Sebastian Moeller
2022-07-10 20:01         ` Michael Welzl
2022-07-10 21:29           ` Sebastian Moeller
2022-07-11  6:24             ` Michael Welzl
2022-07-11  7:33               ` Sebastian Moeller
2022-07-11  8:49                 ` Michael Welzl
2022-07-12  9:47                   ` Sebastian Moeller
2022-07-12 17:56                     ` David Lang
2022-07-12 19:12                       ` Sebastian Moeller
2022-07-12 19:22                         ` David Lang
2022-07-13  6:54                           ` Sebastian Moeller
2022-07-13 15:43                             ` David Lang
2022-07-12 22:27                     ` Michael Welzl
2022-07-13  6:16                       ` 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/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=CAA93jw6bE2NYSHeAcqL+w_j0Mv4KMxRWJR_AwRVT+vGCYiXg7A@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@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