From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] (SCE) Some Congestion Experienced
Date: Sun, 6 Jan 2019 10:43:47 -0800 [thread overview]
Message-ID: <CAA93jw43b=A863S=cq5ai3pmOBt=66d6xn2p-2YLQk1iUk_=gQ@mail.gmail.com> (raw)
I am thinking of making a go at jon's alternate ecn approach in the
ietf, before the dual-q draft gets any further. It's not just that the
latest draft specifes that all classic traffic get 1/4th the
bandwidth, but the total lack of analyzable source code and the frand
patent...
https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-tsvwg-aqm-dualq-coupled
thing is, I can't remember what he called it (EWR?), nor when/where it
was discussed. Nor if there was a novel solution to the ece bit on the
ack side?
It turns out to be really easy to gradually mark packets by modifying
the one line in item 3 (ce_threshold) here:
https://lists.bufferbloat.net/pipermail/codel/2018-August/002367.html
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next reply other threads:[~2019-01-06 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 18:43 Dave Taht [this message]
2019-01-06 20:21 ` Jonathan Morton
2019-01-19 14:33 ` 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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw43b=A863S=cq5ai3pmOBt=66d6xn2p-2YLQk1iUk_=gQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@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