From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Codel] [Bloat] RFC: Realtime Response Under Load (rrul) test specification
Date: Tue, 6 Nov 2012 11:42:45 -0200 [thread overview]
Message-ID: <20121106134245.GB22409@khazad-dum.debian.net> (raw)
In-Reply-To: <CAA93jw7kpMRkjQzaUsnd8mUHuimAZqZynfdVfV_gMRJ5ueSiTA@mail.gmail.com>
On Tue, 06 Nov 2012, Dave Taht wrote:
> I have been working on developing a specification for testing networks
> more effectively for various side effects of bufferbloat, notably
> gaming and voip performance, and especially web performance.... as
> well as a few other things that concerned me, such as IPv6 behavior,
> and the effects of packet classification.
When it is reasonably complete, it would be nice to have it as an
informational or better yet, standards-track IETF RFC.
IETF RFC non-experimental status allows us to require RRUL testing prior to
service acceptance, and even add it as one of the SLA metrics on public
tenders, which goes a long way into pushing anything into more widespread
usage.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2012-11-06 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 12:42 [Codel] " Dave Taht
2012-11-06 13:42 ` Henrique de Moraes Holschuh [this message]
2012-11-06 13:56 ` [Codel] [Bloat] " Dave Taht
2012-11-06 15:40 ` Wesley Eddy
2012-11-06 18:58 ` [Codel] [Cerowrt-devel] " Michael Richardson
2012-11-06 18:14 ` [Codel] " Rick Jones
2012-11-09 10:34 ` Dave Taht
2012-11-09 17:57 ` Rick Jones
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=20121106134245.GB22409@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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