From: Jonathan Morton <chromatix99@gmail.com>
To: "Holland, Jake" <jholland@akamai.com>
Cc: Dave Taht <dave.taht@gmail.com>,
bloat <bloat@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>,
"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
"ecn-sane@lists.bufferbloat.net" <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Codel] [Bloat] The "Some Congestion Experienced" ECN codepoint - a new internet draft -
Date: Sun, 10 Mar 2019 21:30:30 +0200 [thread overview]
Message-ID: <1EE25778-8571-4506-A334-38C544470ACE@gmail.com> (raw)
In-Reply-To: <550C0248-1704-49DA-ABDC-49A91E0AC6F3@akamai.com>
> On 10 Mar, 2019, at 9:08 pm, Holland, Jake <jholland@akamai.com> wrote:
>
> It's easy to accidently read section 5 as underspecified concrete
> proposals instead of rough sketches for future direction that might
> be worth investigating.
This is something I noticed as well, and have edited to match the intended tone of the document (which is to leave specific implementation details to other documents, and to focus on the information conveyed).
> New SCE-aware receivers and transport protocols must continue to
I had already changed this to SHOULD, among other edits.
> "Some" in "Some Congestion Experienced" is maybe misleading, and
> arguably has the same meaning as "Congestion Experienced".
>
> I was thinking maybe "Pre-Congestion Experienced" or "Queue
> Utilization Observed", or if you want to preserve "SCE" and the
> link to CE (which I do agree is nice), maybe "Slight" or "Sub"
> instead of "Some", just to try to make it more obvious it's
> flagging a lesser situation than "there is some congestion".
An interesting idea, but SCE marks will appear even when there's a lot of congestion (at high rates, ie. probably every packet that doesn't carry CE), as well as showing up at low frequency when the level of congestion only warrants reducing the growth rate. I think the word "Some" is sufficiently descriptive, while "Slight" might cause people to ignore it completely.
I think other points are less urgent to address in the first submission.
- Jonathan Morton
next prev parent reply other threads:[~2019-03-10 19:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 18:04 [Codel] " Dave Taht
2019-03-10 18:53 ` [Codel] [Cake] " Sebastian Moeller
[not found] ` <550C0248-1704-49DA-ABDC-49A91E0AC6F3@akamai.com>
2019-03-10 19:30 ` Jonathan Morton [this message]
[not found] ` <alpine.DEB.2.20.1903110800310.3161@uplift.swm.pp.se>
2019-03-11 7:35 ` [Codel] [Bloat] " Richard Scheffenegger
2019-03-11 7:54 ` Sebastian Moeller
2019-03-11 8:59 ` Jonathan Morton
2019-03-11 9:07 ` Mikael Abrahamsson
2019-03-11 9:10 ` Jonathan Morton
2019-03-11 9:47 ` Mikael Abrahamsson
2019-03-11 10:11 ` Dave Taht
[not found] ` <9C165094-DE2D-42AA-85F3-71760F01BD92@akamai.com>
2019-03-11 16:13 ` [Codel] [Ecn-sane] " Jonathan Morton
2019-03-11 7:43 ` [Codel] [Cake] " Sebastian Moeller
2019-03-13 4:39 ` David Lang
2019-03-10 21:11 ` [Codel] " Dave Taht
2019-03-10 21:28 ` Dave Taht
2019-03-10 21:49 ` Dave Taht
2019-03-10 22:37 ` [Codel] [Ecn-sane] " Toke Høiland-Jørgensen
2019-03-11 3:23 ` [Codel] " Michael Richardson
2019-03-11 3:26 ` 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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1EE25778-8571-4506-A334-38C544470ACE@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=jholland@akamai.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