Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Michael Welzl <michawe@ifi.uio.no>,
	ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] rtt-fairness question
Date: Thu, 14 Apr 2022 10:16:59 -0700	[thread overview]
Message-ID: <CAA93jw5J2TqryL2hbjj8-jxGScV3DZ8XTxUVgBRd-AkFdoTt3g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5DoOEkeavQPmZ=MHQtKp1q1Av6BLrpEY6jSNZPsD55=w@mail.gmail.com>

Actually, in looking back at what I wrote, I was

A) comparing a recent rtt-fairness result I'd got without ECN with
multiple flows at 20ms to 260ms RTT that I was insanely pleased with.

B) while trying to understand and asking about what sort of
RTT-fairness results were being achieved with early ECN marking in the
dctcp world. which until recently was mostly shooting for fairness in
the sub-us to 2ms range.  I was laboriously starting over from
scratch, reading the original papers, tracking the breadcrumbs from
2009 until today, so I'd stumbled on some thoughts in the next paper
after the dctcp paper that I was too lazy to try and correlate to
present day "prague" and BBRv2 thinking.

  reply	other threads:[~2022-04-14 17:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 16:33 Dave Taht
2022-04-08 18:03 ` Michael Welzl
2022-04-12 15:51   ` David P. Reed
2022-04-12 16:00     ` Michael Welzl
2022-04-12 18:52       ` Sebastian Moeller
2022-04-12 19:07         ` Michael Welzl
2022-04-14 16:54           ` David P. Reed
2022-04-14 17:08             ` Dave Taht
2022-04-14 17:16               ` Dave Taht [this message]
2022-04-14 20:49                 ` David P. Reed
2022-04-14 21:25             ` Sebastian Moeller
2022-04-19 20:40               ` David P. Reed
2022-04-19 21:36                 ` Vint Cerf
2022-04-19 23:55                   ` Rodney W. Grimes
2022-04-20 12:54                 ` Sebastian Moeller
2022-04-20 22:21                   ` David P. Reed

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=CAA93jw5J2TqryL2hbjj8-jxGScV3DZ8XTxUVgBRd-AkFdoTt3g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=dpreed@deepplum.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=michawe@ifi.uio.no \
    /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