From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Jonathan Morton <chromatix99@gmail.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: [Codel] [Bloat] The "Some Congestion Experienced" ECN codepoint - a new internet draft -
Date: Mon, 11 Mar 2019 03:11:47 -0700 [thread overview]
Message-ID: <CAA93jw5TS1haVk_nF8O79eQOdSu1FovSNrKyzU8Z5bfPdTUgxg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1903111044210.3161@uplift.swm.pp.se>
Everybody, calm down. I put this out merely to get comment before we
submitted the first of several drafts. That draft is now submitted and
we've asked for a talk slot in the tsvwg for it. I cc'd the world to
get quick initial feedback, and I want to shut this overbroad
conversation down and move it to just the ecn-sane mailing list.
The l4s mailing list is dead, and the debates on the AQM mailing list and here,
unhelpful - for decades. So, back in august I started a new working
group here, under house rules that I thought would be more productive,
and asked that people that wanted to debate ecn more sanely, join. few
did.
And jon and I have been working for months (and largely not on the
list) to try and create a compromise proposal of which y'all just saw
the first output. There's more in the bufferbloat-rfcs repo.
The rules for joining the ecn-sane list are simple - take the time to
step back and write a write a short position paper, and join (or
create) a team. You needn't do that immediately. If you disagree with
the rules of operation of the ecn-sane working group, submit a pull
request or file a bug on the web site. where we can discuss it.
Ironically our ssl cert just expired and I don't remember how to fix it.
Please join the ecn-sane mailing list for discussing this stuff and
stop cc-ing the whole bufferbloat.net world on it, please.
next prev parent reply other threads:[~2019-03-11 10:12 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 ` [Codel] [Bloat] " Jonathan Morton
[not found] ` <alpine.DEB.2.20.1903110800310.3161@uplift.swm.pp.se>
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 ` Dave Taht [this message]
[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=CAA93jw5TS1haVk_nF8O79eQOdSu1FovSNrKyzU8Z5bfPdTUgxg@mail.gmail.com \
--to=dave.taht@gmail.com \
--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=swmike@swm.pp.se \
/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