From: Matt Mathis <mattmathis@google.com>
To: dpreed@reed.com
Cc: Wesley Eddy <wes@mti-systems.com>,
bloat-announce@lists.bufferbloat.net,
cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] some good bloat related stuff on the ICCRG agenda, IETF #86 Tuesday, March 12 2013, 13:00-15:00, room Caribbean 6
Date: Thu, 28 Feb 2013 19:55:20 -0000 [thread overview]
Message-ID: <CAH56bmCkuqWzLY1ojJYY6xjmO9hUx11YKKGQD3K0VOnJSpgS+Q@mail.gmail.com> (raw)
In-Reply-To: <1362077224.256114355@apps.rackspace.com>
Two of the tests in my model based metrics draft (for IPPM) are for
AQM (like) tests. One we have pretty good theory for (preventing
standing queues in congestion avoidance) and the other we don't
(exiting from slowstart at a reasonable window).
See: draft-mathis-ippm-model-based-metrics-01.txt
My intent is that these tests will become part of a future IPPM
standard on what a network must do in order to support modern
applications at specific performance levels. Although the draft
will not specify AQM algorithms at all, it will forbid some non-AQM
behaviors such as unreasonable standing queues. To the extent that
it gets traction as a standard, it will strongly encourage deployment,
even if we are not totally convinced that our current AQM algorithms
are 100% correct.
However, It is not clear that we need to standardize AQM - It strikes
me as one area where we can permit pretty much unfettered diversity in
the operational Internet as long as it meets a pretty low "it seems
to work" bar.
For this reason it is important to deploy your favorite algorithm(s)
ASAP, because they are all infinitely better than none, and future
improvements will be relatively minor by comparison.
Thanks,
--MM--
The best way to predict the future is to create it. - Alan Kay
Privacy matters! We know from recent events that people are using our
services to speak in defiance of unjust governments. We treat
privacy and security as matters of life and death, because for some
users, they are.
On Thu, Feb 28, 2013 at 10:47 AM, <dpreed@reed.com> wrote:
>
> A small suggestion. Instead of working on *algorithms*, focus on getting something actually *deployed* to fix the very real issues that we have today (preserving the option to upgrade later if need be).
>
>
>
> The folks who built the Internet (I was there, as you probably know) focused on making stuff that worked and interoperated, not publishing papers or RFCs.
>
>
>
> -----Original Message-----
> From: "Wesley Eddy" <wes@mti-systems.com>
> Sent: Thursday, February 28, 2013 1:11pm
> To: "Dave Taht" <dave.taht@gmail.com>
> Cc: bloat-announce@lists.bufferbloat.net, "Martin Stiemerling" <Martin.Stiemerling@neclab.eu>, cerowrt-devel@lists.bufferbloat.net, "bloat" <bloat@lists.bufferbloat.net>
> Subject: Re: [Cerowrt-devel] [Bloat] some good bloat related stuff on the ICCRG agenda, IETF #86 Tuesday, March 12 2013, 13:00-15:00, room Caribbean 6
>
> On 2/28/2013 10:53 AM, Dave Taht wrote:
> >
> > For those that don't attend ietf meetings in person, there is usually
> > live audio and jabber chat hooked up into the presentations.
> >
> > See y'all there, next month, in one form or another.
> >
>
>
> In the TSVAREA meeting, we've also set aside some time to talk
> about AQM and whether there's interest and energy to do some
> more specific work on AQM algs in the IETF (e.g. like CoDel and
> PIE):
>
> https://datatracker.ietf.org/meeting/86/agenda/tsvarea
>
> I'm working with Martin on some slides to seed the discussion,
> but we hope that it's mostly the community that we hear from,
> following up in the higher-bandwidth face-to-face time from
> the thread we had on the tsv-area@ietf.org mailing list a few
> months ago.
>
>
> --
> Wes Eddy
> MTI Systems
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
next prev parent reply other threads:[~2013-02-28 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 15:53 [Cerowrt-devel] " Dave Taht
2013-02-28 18:11 ` [Cerowrt-devel] [Bloat] " Wesley Eddy
2013-02-28 18:47 ` dpreed
2013-02-28 19:55 ` Matt Mathis [this message]
2013-03-01 18:29 ` Wesley Eddy
2013-03-01 18:40 ` dpreed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH56bmCkuqWzLY1ojJYY6xjmO9hUx11YKKGQD3K0VOnJSpgS+Q@mail.gmail.com \
--to=mattmathis@google.com \
--cc=bloat-announce@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.com \
--cc=wes@mti-systems.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