From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] ect(1) queue selector question
Date: Sun, 21 Feb 2021 02:51:03 +0100 [thread overview]
Message-ID: <D092B242-4986-4F0C-BC55-42B708349DA6@gmx.de> (raw)
In-Reply-To: <CAA93jw4P1hoR1N9c17JG030kBymZnYT8VSvy4vsmrzqSN++phQ@mail.gmail.com>
Hi Dave,
> On Feb 20, 2021, at 20:27, Dave Taht <dave.taht@gmail.com> wrote:
>
> I note that I have done my best to stay out of this for a while, so
> long that I (thankfully) mis-remember various aspects of the debate.
> Today I have a question about l4s vs SCE as it's come up again.
>
> l4s uses both a dscp codepoint AND ect(1) to indicate dctcp style
> congestion control
> is in use, and also can dump other protocols into that queue lacking
> any ecn markings.
Mmmh, according to the L4S internet drafts, L4S does not want to use a DSCP at all. Interestingly enough, Greg White is proposing a related internet draft about the NQB PHB and DSCP that sounds awfully like the missing DSCP in the L4S drafts. IMHO if the whole thing would be guarded behind a DSCP I would be less annoyed by the design and process of L4S....
>
> SCE proposes to use ect(1) as an indicator of some congestion and does
> not explictly
> require a dscp codepoint in a FQ'd implementation.
Pretty much. I do think that a demonstration using an additional DSCP to create a similar HOV lane for SCE would have gone miles in convincing people in the WG that L4S might really not be as swell as its proponents argue, IMHO it won the day more with its attractive promise of low latency for all instead of what it delivers.
>
> Do I have that right? Now, my question was, simply, in MPLS or X-G are
> they out of bits, and
> that's why they want to use up this one in L4S?
I do not think that MPLS folks are a driver in all of this, no? No idea what X-G is.
>
> --
> "For a successful technology, reality must take precedence over public
> relations, for Mother Nature cannot be fooled" - Richard Feynman
>
> dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
> _______________________________________________
> Ecn-sane mailing list
> Ecn-sane@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/ecn-sane
next prev parent reply other threads:[~2021-02-21 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 19:27 Dave Taht
2021-02-21 1:51 ` Sebastian Moeller [this message]
2021-02-21 17:14 ` Rodney W. Grimes
2021-02-21 20:26 ` Dave Taht
2021-03-09 0:36 Pete Heist
2021-03-09 1:18 ` Dave Taht
2021-03-09 9:11 ` Pete Heist
2021-03-09 15:19 ` Rodney W. Grimes
2021-03-09 15:28 ` Dave Taht
2021-03-09 15:38 ` Rodney W. Grimes
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=D092B242-4986-4F0C-BC55-42B708349DA6@gmx.de \
--to=moeller0@gmx.de \
--cc=dave.taht@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