From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] [Bloat] sce materials from ietf
Date: Fri, 29 Nov 2019 23:20:56 +0200 [thread overview]
Message-ID: <63E9C0E4-C913-4B2F-8AFC-64E12489BC65@gmail.com> (raw)
In-Reply-To: <CAA93jw7e_TwWPh3eovcZSMfwJh_V-E9YP6T=-TrU_r5DS0j3Kw@mail.gmail.com>
> On 29 Nov, 2019, at 10:08 pm, Dave Taht <dave.taht@gmail.com> wrote:
>
> there are no minutes posted.
>
> https://datatracker.ietf.org/meeting/106/materials/slides-106-tsvwg-sessa-81-some-congestion-experienced-00
>
> https://datatracker.ietf.org/meeting/106/materials/slides-106-tcpm-some-congestion-experienced-in-tcp-00
Those should both be the same slide deck. We got squeezed out of over half our expected talk time in TSVWG, and didn't get to present at all in TCPM (though we were able to comment from the floor on related AccECN matters) - we were just expecting to focus on one or two slides from the deck there.
I think we got two big takeaways from IETF-106:
First, that L4S is really floundering in their fundamental problems and has not yet been able to demonstrate any genuine solutions to them, and instead they're trying to bog us down in process. However, there is growing interest in SCE, despite the relatively small footprint we still have officially.
Second, I gained a couple of key insights that I think will help to solve SCE's remaining shortcomings. If we can apply them successfully by Vancouver, we'll be able to stand up and say not only that SCE meets *all* of the Prague Requirements, while L4S is currently missing two of them, but that we've also solved the single-queue problem. I'm deliberately leaving the technical details vague until we've done some testing, but I will say that the name we've come up with is amusing.
Now if you'll excuse me, I need to fix a computer…
- Jonathan Morton
next prev parent reply other threads:[~2019-11-29 21:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 20:08 [Ecn-sane] " Dave Taht
2019-11-29 21:20 ` Jonathan Morton [this message]
2019-11-29 23:10 ` [Ecn-sane] [Bloat] " alex.burr
2019-11-30 1:39 ` Jonathan Morton
2019-11-30 7:27 ` Sebastian Moeller
2019-11-30 14:32 ` Jonathan Morton
2019-11-30 15:42 ` Sebastian Moeller
2019-11-30 17:11 ` Jonathan Morton
2019-12-02 5:38 ` Dave Taht
2019-12-02 7:54 ` Sebastian Moeller
2019-12-02 9:57 ` Pete Heist
2019-11-30 22:17 ` Carsten Bormann
2019-11-30 22:23 ` Jonathan Morton
2019-12-01 16:35 ` Sebastian Moeller
2019-12-01 16:54 ` Jonathan Morton
2019-12-01 19:03 ` Sebastian Moeller
2019-12-01 19:27 ` Jonathan Morton
2019-12-01 19:32 ` Sebastian Moeller
2019-12-01 20:30 ` Jonathan Morton
2019-12-01 17:30 ` Rodney W. Grimes
2019-12-01 19:17 ` Sebastian Moeller
2019-12-02 5:10 ` Dave Taht
2019-12-02 7:18 ` Sebastian Moeller
2019-11-29 22:55 ` [Ecn-sane] " Rodney W. Grimes
2019-11-29 22:58 ` Rodney W. Grimes
2019-11-30 2:37 ` Dave Taht
2019-11-30 3:10 ` 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=63E9C0E4-C913-4B2F-8AFC-64E12489BC65@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--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