Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Pete Heist <pete@heistp.net>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] Multiplicative Decrease Scaling (high-fidelity ECN in a single queue)
Date: Tue, 22 Oct 2024 09:10:28 +0200	[thread overview]
Message-ID: <87969c1dcff6f5d10bbba4564964e9b54d58c075.camel@heistp.net> (raw)
In-Reply-To: <344059A3-8DE7-424E-AD7B-EB2F69EB7EC9@gmx.de>

Thanks Sebastian, fixed that typo...

Pete

On Mon, 2024-10-21 at 23:46 +0200, Sebastian Moeller wrote:
> Hi Pete,
> 
> nice! I note that the legend for figure 8 b says: "Figure 8b: CUBIC-
> MDS at 100 Mbps, 600 ms path RTT" but the plot implies 1000 Mbps.
> 
> > On 21. Oct 2024, at 10:48, Pete Heist via Ecn-sane
> > <ecn-sane@lists.bufferbloat.net> wrote:
> > 
> > Hi all,
> > 
> > I'm looking for some feedback on a way to do early and frequent ECN
> > that retains compatibility with conventional CCAs in a single
> > queue.
> > Here's a write-up including simulation results:
> > 
> > https://github.com/heistp/md-scaling/blob/main/MD-Scaling.md
> > 
> > -----
> > Abstract:
> > 
> > Multiplicative Decrease Scaling (MDS or MD-Scaling) provides high-
> > fidelity Explicit Congestion Notification (ECN) in a way that's
> > compatible with conventional congestion control algorithms (CCAs)
> > in a
> > single queue. Using a signaling and response relationship that
> > allows
> > cwnd convergence with conventional CCAs, MDS aims to reduce
> > queueing
> > delay, and increase utilization for MDS CCAs, while supporting the
> > transition to scalable CCAs.
> > -----
> > 
> > I find the results interesting, and am looking to determine if this
> > idea is worth pursuing further.  Any feedback on the approach,
> > proposed
> > signaling mechanism or anything else is welcome.
> > 
> > Thanks!
> > Pete Heist
> > 
> > PS- I've also posted this to ICCRG in the IRTF, so apologies to
> > anyone
> > getting hit with it twice.
> > _______________________________________________
> > Ecn-sane mailing list
> > Ecn-sane@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/ecn-sane
> 


      reply	other threads:[~2024-10-22  7:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  8:48 Pete Heist
2024-10-21 21:46 ` Sebastian Moeller
2024-10-22  7:10   ` Pete Heist [this message]

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

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

  git send-email \
    --in-reply-to=87969c1dcff6f5d10bbba4564964e9b54d58c075.camel@heistp.net \
    --to=pete@heistp.net \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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