General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Wesley Eddy <wes@mti-systems.com>
To: curtis@ipv6.occnc.com, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "Akhtar, Shahid \(Shahid\)" <shahid.akhtar@alcatel-lucent.com>,
	"iccrg@irtf.org" <iccrg@irtf.org>, "aqm@ietf.org" <aqm@ietf.org>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [aqm]  [iccrg] AQM deployment status?
Date: Tue, 15 Oct 2013 21:00:16 -0400	[thread overview]
Message-ID: <525DE520.7040501@mti-systems.com> (raw)
In-Reply-To: <201310141707.r9EH7wC7068478@gateway1.orleans.occnc.com>

On 10/14/2013 1:07 PM, Curtis Villamizar wrote:
> So my first question to the AQM WG is "what is the scope of AQM WG
> work in terms of where in the network this WG wants to focus?"  If the
> answer to that question is "everywhere", then we have to be aware that
> conditions in core and conditions in home or enterprise are very
> different.  If the focus is on home, soho, and small business, then
> the charter should say so (I don't think it is).


The charter says:
"""
  It is expected that some classes of algorithms will focus on software
  implementations, while others on existing or new hardware
  deployments, and algorithms may be specific to distinct scenarios.
"""

I would say anywhere that AQM algorithms can have a positive impact
is in scope, and that it's understood and accepted that particular
algorithms or tuning rules may not be ideal across different
environments (or may not be easily implemented in different kinds of
platforms).  There was at least some talk of "applicability
statements" for things that wind up being recommended by the working
group.

In my opinion, the home broadband router is one well-known case that
may hold a lot of the initial attention in the working group, because
the barriers to implementing/testing/deploying new algorithms for this
case are less than for many others.  We definitely did not want to
limit the charter to this scenario though, and it is intentionally
open to others.

I hope this clears it up!


-- 
Wes Eddy
MTI Systems

       reply	other threads:[~2013-10-16  1:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Your message of "Fri, 11 Oct 2013 23:18:05 EDT." <12845.1381547885@sandelman.ca>
     [not found] ` <201310141707.r9EH7wC7068478@gateway1.orleans.occnc.com>
2013-10-16  1:00   ` Wesley Eddy [this message]
2013-11-05  2:56   ` Bob Briscoe
2013-09-24 17:21 [Bloat] " Naeem Khademi
2013-09-25 14:20 ` [Bloat] [aqm] " Akhtar, Shahid (Shahid)
2013-09-25 14:31   ` [Bloat] [iccrg] " Eggert, Lars
2013-09-25 14:35     ` Steinar H. Gunderson
2013-09-25 18:51       ` Akhtar, Shahid (Shahid)
2013-09-25 19:19         ` [Bloat] [aqm] [iccrg] " Naeem Khademi
2013-09-27 16:49           ` Akhtar, Shahid (Shahid)
2013-09-25 19:24         ` Mikael Abrahamsson
2013-09-26  9:39           ` [Bloat] [iccrg] [aqm] " Scheffenegger, Richard
2013-09-27  2:59             ` Mikael Abrahamsson
2013-09-27  9:06               ` Eggert, Lars
2013-09-28  7:01                 ` Mikael Abrahamsson
2013-09-28  7:04                   ` Eggert, Lars
2013-09-29  1:16                     ` [Bloat] [aqm] [iccrg] " Bob Briscoe
2013-09-29  9:37                       ` Mikael Abrahamsson
2013-11-13 17:50           ` Fred Baker (fred)

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=525DE520.7040501@mti-systems.com \
    --to=wes@mti-systems.com \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=curtis@ipv6.occnc.com \
    --cc=iccrg@irtf.org \
    --cc=mcr+ietf@sandelman.ca \
    --cc=shahid.akhtar@alcatel-lucent.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