Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	Cake List <cake@lists.bufferbloat.net>,
	cerowrt-devel@lists.bufferbloat.net,
	 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: [Cerowrt-devel] The new ecn-sane project and mailing list
Date: Thu, 6 Sep 2018 13:11:00 -0700	[thread overview]
Message-ID: <CAA93jw6QQK2e1xdRM6kc_tvw2euhpJ3jkNUxfBdq4dpFFkjZbA@mail.gmail.com> (raw)

After clearing my plate for the past few months, I wanted to tackle
something that keeps me awake at night.

We just started an attempt to start taking a hard look at deployed ECN
behaviors over the fq_codel, fq_pie, and fq_codel for wifi
deployments:

https://www.bufferbloat.net/projects/ecn-sane/wiki/

As ECN has long been a sensitive topic... The mailing list has
sprouted a few new rules to try to keep the noise level down:

https://www.bufferbloat.net/projects/ecn-sane/wiki/rules/

And there''s a "team" concept that may or may not work. I have so much
data and papers in my head that somehow having a way to apply a stamp,
a tag, to all that, that my hope was to try and tag and comment on
papers and experiments to keep them all straight.

List is here:

https://lists.bufferbloat.net/listinfo/ecn-sane

If anyone would like to "formally" join the project, join a team, and
write a position statement, please fork
https://github.com/tohojo/bufferbloat-net or supply
a markdown formatted file for it. Suggestions for additional "colors",
behaviors and protocol options to look at, gladly discussed on the new
mailing list.

--

                 reply	other threads:[~2018-09-06 20:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw6QQK2e1xdRM6kc_tvw2euhpJ3jkNUxfBdq4dpFFkjZbA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=make-wifi-fast@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