From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "Holland, Jake" <jholland@akamai.com>,
Cake List <cake@lists.bufferbloat.net>,
"ecn-sane@lists.bufferbloat.net"
<ecn-sane@lists.bufferbloat.net>,
"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat] The "Some Congestion Experienced" ECN codepoint - a new internet draft -
Date: Mon, 11 Mar 2019 08:08:06 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1903110800310.3161@uplift.swm.pp.se> (raw)
In-Reply-To: <1EE25778-8571-4506-A334-38C544470ACE@gmail.com>
On Sun, 10 Mar 2019, Jonathan Morton wrote:
> 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.
One way to handle this would be "buffering experienced" or something like
that. Ie if this packet is being enqueued into a buffer with non-trivial
number of packets in it, mark it.
The L4S proposal also has the property that their use of this last code
point combination in the entire packet header (and this is a big thing,
this is the last unicorn) also meant the packet was allowed to be
re-ordered. I thought this was a big and nice thing, for other areas. This
new proposal removes that property.
From what I can see, L4S actually is quite novel and has the chance to
seriously change the way queueing is done. This proposal seems more like
"a little more of what we had before" which I do not think warrants
claiming this last unicorn codepoint. I'd like its use to be truly novel
and be more than a tweak.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2019-03-11 7:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 18:04 [Cake] " Dave Taht
2019-03-10 18:53 ` Sebastian Moeller
2019-03-10 19:08 ` [Bloat] " Holland, Jake
2019-03-10 19:30 ` [Cake] " Jonathan Morton
2019-03-11 7:08 ` Mikael Abrahamsson [this message]
2019-03-11 7:35 ` 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 ` [Cake] [Codel] " Dave Taht
2019-03-11 16:14 ` Holland, Jake
2019-03-11 15:29 ` [Ecn-sane] " Holland, Jake
2019-03-11 16:13 ` [Cake] " Jonathan Morton
2019-03-11 7:43 ` [Cake] " Sebastian Moeller
2019-03-11 8:23 ` Mikael Abrahamsson
2019-03-13 4:39 ` David Lang
2019-03-10 21:11 ` Dave Taht
2019-03-10 21:28 ` Dave Taht
2019-03-10 21:49 ` Dave Taht
2019-03-10 22:37 ` [Ecn-sane] " Toke Høiland-Jørgensen
2019-03-11 3:23 ` [Cake] " 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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1903110800310.3161@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--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