Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] draft tsvwg slides #1
Date: Mon, 25 Mar 2019 08:27:13 -0400	[thread overview]
Message-ID: <A25B076F-2022-45A4-A732-A2BD0DFDA320@gmail.com> (raw)
In-Reply-To: <mailman.2171.1553499284.3538.ecn-sane@lists.bufferbloat.net>

[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]


> On Mar 25, 2019, at 3:34 AM, ecn-sane-request@lists.bufferbloat.net wrote:
> 
> Working on getting better plotable data
> 
> What do y'all think? https://lists.bufferbloat.net/pipermail/ecn-sane/attachments/20190325/2cbfe1a1/attachment.odp <https://lists.bufferbloat.net/pipermail/ecn-sane/attachments/20190325/2cbfe1a1/attachment.odp>
Here are a couple comments on the progression of the slides:

1: Intro - good
2: Blank - placeholder - you'll fix this
3: The Problem - good. Maybe say that *loss* only provides binary signal per RTT -> Oscillation -> Bang-bang control theory

Then... swap slides 4 & 5

4: Two Congestion Signals - major bullet points
	- Congestion should be an earlier signal than loss
	- Swap CE & SCE, noting CE gives coarse info
	- We propose SCE, to give high fidelity information

5: Rename heading - s/The Solution/The Implementation/

6: State Diagram - good
7: Experimental Plan - good

8: Plot - You need to have an explanation of the graph on the final slide. It's a bit hard to read the axes, but way more important is a clear description of what the heck we're looking at. It won't be as detailed as [Explaining RRUL Charts](https://www.bufferbloat.net/projects/bloat/wiki/RRUL_Chart_Explanation/) but someone reading (only) the slides should be able to understand what the plot shows.

9: Some kind of summary

Good luck!

Rich

[-- Attachment #2: Type: text/html, Size: 3725 bytes --]

       reply	other threads:[~2019-03-25 12:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2171.1553499284.3538.ecn-sane@lists.bufferbloat.net>
2019-03-25 12:27 ` Rich Brown [this message]
2019-03-25 12:34   ` Jonathan Morton
2019-03-25 12:47     ` Rich Brown
     [not found]       ` <CAJpr3FM+AZXN34j_KS0KA28Hax3rmpyV8PsVXnKn2XGYjkAkmA@mail.gmail.com>
2019-03-25 15:25         ` [Ecn-sane] Fwd: " Bruno George Moraes
2019-03-25 15:42           ` Dave Taht
2019-03-25 12:39   ` [Ecn-sane] " Jeremy Harris
2019-03-25  7:34 Dave Taht
2019-03-25  8:17 ` Dave Taht

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=A25B076F-2022-45A4-A732-A2BD0DFDA320@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=ecn-sane@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