From: Wesley Eddy <wes@mti-systems.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Codel] RFC: Realtime Response Under Load (rrul) test specification
Date: Tue, 06 Nov 2012 10:40:38 -0500 [thread overview]
Message-ID: <50992F76.20406@mti-systems.com> (raw)
In-Reply-To: <CAA93jw6x_fru2PkUuj2-aFz5QN5eBHRiE-L9cg3EnH3SMX7x3w@mail.gmail.com>
On 11/6/2012 8:56 AM, Dave Taht wrote:
> On Tue, Nov 6, 2012 at 2:42 PM, Henrique de Moraes Holschuh
> <hmh@hmh.eng.br> wrote:
>> 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.
>
> It was my intent to write this as a real, standards track rfc, and
> also submit it as a prospective test to the ITU and other testing
> bodies such as nist, undewriter labratories, consumer reports, and so
> on.
>
> However I:
>
> A) got intimidated by the prospect of dealing with the rfc editor
>
> B) Have some sticky problems with two aspects of the test methodology
> (and that's just what I know about) which I am prototyping around.
> Running the prototype tests on various real networks has had very
> "interesting" results... (I do hope others try the prototype tests,
> too, on their networks)
>
> C) thought it would be clearer to write the shortest document possible
> on this go-round.
> D) Am not particularly fond of the "rrule" name. (suggestions?)
>
> I now plan (after feedback) to produce and submit this as a standards
> track RFC in the march timeframe.
>
> It would give me great joy to have this test series included in
> various SLA metrics, in the long run.
>
Hi Dave, in my role as IETF TSV AD, I would be happy to help
you get this into the IETF. Please note that you can't get
a Standards Track RFC published without a working group
adopting it or an AD sponsoring it.
This topic would be of interest for the IPPM and BMWG working
groups, and I know it is of interest to me as a TSV AD, so we
should be able to find a way to bring it in.
In fact, the timing is good, as FCC folks are at the IETF this
week talking about their vision for broadband test and
measurement architecture, and these tests may relate nicely
to that proposed work.
--
Wes Eddy
MTI Systems
next prev parent reply other threads:[~2012-11-06 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 12:42 [Bloat] " Dave Taht
2012-11-06 13:42 ` Henrique de Moraes Holschuh
2012-11-06 13:56 ` Dave Taht
2012-11-06 15:40 ` Wesley Eddy [this message]
2012-11-06 18:58 ` [Bloat] [Cerowrt-devel] " Michael Richardson
2012-11-06 18:14 ` [Bloat] [Codel] " Rick Jones
2012-11-09 10:34 ` Dave Taht
2012-11-09 17:57 ` Rick Jones
[not found] <mailman.3.1352232001.18990.codel@lists.bufferbloat.net>
[not found] ` <5099788B.1000704@rogers.com>
2012-11-09 10:21 ` 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/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=50992F76.20406@mti-systems.com \
--to=wes@mti-systems.com \
--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