Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: "Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>,
	Cake List <cake@lists.bufferbloat.net>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] three new internet drafts regarding SCE
Date: Wed, 17 Jul 2019 08:07:56 -0700 (PDT)	[thread overview]
Message-ID: <201907171507.x6HF7u7o082245@gndrsh.dnsmgr.net> (raw)
In-Reply-To: <CAA93jw7yn2B6LfUP_Q_5cqqJfxMH0T3hSZiH4VMUYg=qSE33_A@mail.gmail.com>

> IETF 105 runs from July 20-27th in Montreal.
> 
> https://datatracker.ietf.org/meeting/105/agenda/
> 
> tsvwg meets thursday morning 10-12, and friday 12:20-
> 
> Remote attendance via videconferencing tools is straightforward. There
> are of course dozens of other wg meetings of possible interest, in my
> case, I'm still tracking babel's progress through the ietf, in
> particular, and I always try to
> check in on iccrg, also in case anything interesting comes up.
> 
> Since not all members of our mailing lists are on the relevant tsvwg
> or tcpmwg  mailing lists, here are some drafts
> from those working on the SCE front (I'm not, but I do read things)
> for aqm and transport enhancements.
> 
> https://tools.ietf.org/html/draft-grimes-tcpmwg-tcpsce-00
> 
> https://tools.ietf.org/html/draft-morton-tsvwg-sce-00
> 
> https://tools.ietf.org/html/draft-heist-tsvwg-sce-one-and-two-flow-tests-00

There is actually a 4th related draft which is a new Q algorithm:

https://tools.ietf.org/html/draft-morton-tsvwg-lightweight-fair-queueing

> I would have liked it if the the actual scripts, & flent data files
> were published and referenced in this last draft. (I think the
> pictures were published on some other email thread (?), and I look
> forward to the slides)

We are working towards this, part of the problem is the tools
and the data was evolving at a pace faster than we could publish them.

We have now validated that an independent person can build,
install and run a SCE capable linux kernel avaliable at:

	https://github.com/chromi/sce

Note that this is evolving code, so expect to see updates,
as well as complete notes on new sysctl's avaliable to
enable/disable features for testing purposes.

> My own
> (eventual) contribution to this work might be on the wifi front, but
> neither l4s or sce are baked enough yet to bother trying,
> IMHO. My analysis of the battlemesh fq_codel + ecn over wifi data I
> hope to finish this week, but I'll find an other outlet for
> publication. (smallest subset of observations is that we can reduce
> the codel target to 6ms on wifi networks that have powersave disabled,
> and that serious 802.11e queue use still massively sucks. details to
> come later)
> 
> There are many, many, many other drafts in progress in tsvwg, of note might be:
> 
> https://tools.ietf.org/id/draft-white-tsvwg-lld-00.txt
> 
> https://tools.ietf.org/id/draft-white-tsvwg-nqb-02.txt
> 
> In addition to the perpetually revised l4s related ones.
> 
> -- 
> 
> Dave T?ht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-205-9740

-- 
Rod Grimes                                                 rgrimes@freebsd.org

  parent reply	other threads:[~2019-07-17 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17 13:12 Dave Taht
2019-07-17 13:17 ` Luca Muscariello
2019-07-17 15:07 ` Rodney W. Grimes [this message]
2019-07-17 19:04   ` 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/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=201907171507.x6HF7u7o082245@gndrsh.dnsmgr.net \
    --to=4bone@gndrsh.dnsmgr.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=ecn-sane@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