From: Dave Taht <dave@taht.net>
To: ecn-sane@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: [Bloat] non queue building flows ietf draft review.
Date: Sat, 24 Aug 2019 07:57:12 -0700 [thread overview]
Message-ID: <87h866d31z.fsf@taht.net> (raw)
I decided that perhaps it would be best if we tried harder
to live within the ietf's processes for calm, reasoned discussion
But in trying to review this internet draft...
https://tools.ietf.org/id/draft-white-tsvwg-nqb-02.html
I couldn't help myself, and my review is here:
https://mailarchive.ietf.org/arch/msg/tsvwg/hZGjm899t87YZl9JJUOWQq4KBsk
If someone could make something constructive out of that, great. It
would be good to have a really clear definition of what we mean by
sparse, and good definition and defense on our website of the properties
and benefits of fair queueing.
And I'm going to go off today and try to do something nice for a small
animal, a widow, or an orphan. Maybe plant some flowers.
Some days it doesn't pay to read your accrued inbox messages. Today
was one of them. You needen't read mine either!
next reply other threads:[~2019-08-24 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 14:57 Dave Taht [this message]
2019-08-24 15:37 ` [Bloat] [Ecn-sane] " Sebastian Moeller
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h866d31z.fsf@taht.net \
--to=dave@taht.net \
--cc=bloat@lists.bufferbloat.net \
--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