From: "Fred Baker (fred)" <fred@cisco.com>
To: "<curtis@ipv6.occnc.com>" <curtis@ipv6.occnc.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
"aqm@ietf.org" <aqm@ietf.org>,
"<end2end-interest@postel.org>" <end2end-interest@postel.org>
Subject: Re: [Bloat] [aqm] What is a good burst? -- AQM evaluation guidelines
Date: Thu, 2 Jan 2014 06:31:20 +0000 [thread overview]
Message-ID: <533BE7A9-7804-4A74-BBFB-C75CCE212434@cisco.com> (raw)
In-Reply-To: <201312151857.rBFIuuea043478@gateway0.ipv6.occnc.com>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Dec 15, 2013, at 10:56 AM, Curtis Villamizar <curtis@ipv6.occnc.com> wrote:
> So briefly, my answer is: as a WG, I don't think we want to go there.
> If we do go there at all, then we should define "good AQM" in terms of
> acheving a "good" tradeoff between fairness, bulk transfer goodput,
> and bounded delay. IMHO sometimes vague is better.
As you may have worked out from my previous comments in these threads, I agree with you. I don't think this can be nailed down in a universal sense. What can be described is the result in the network, in that delays build up that persist, as opposed to coming and going, and as a result applications don't work as well as they might - and at that point, it is appropriate for the network to inform the transport.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2014-01-02 6:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 5:35 [Bloat] " Naeem Khademi
2013-12-15 12:26 ` Jonathan Morton
2013-12-15 15:16 ` Scharf, Michael (Michael)
[not found] ` <655C07320163294895BBADA28372AF5D14C5DF@FR712WXCHMBA15.zeu. alcatel-lucent.com>
2013-12-15 20:56 ` Bob Briscoe
2013-12-15 18:56 ` [Bloat] [aqm] " Curtis Villamizar
2014-01-02 6:31 ` Fred Baker (fred) [this message]
2014-01-03 18:17 ` [Bloat] [e2e] " dpreed
2014-01-30 19:27 ` [Bloat] [aqm] [e2e] " Dave Taht
2013-12-15 21:42 ` [Bloat] [aqm] " Fred Baker (fred)
2013-12-15 22:57 ` [Bloat] [e2e] " Bob Briscoe
2013-12-16 7:34 ` Fred Baker (fred)
2013-12-16 13:47 ` Naeem Khademi
2013-12-16 14:05 ` Naeem Khademi
2013-12-16 17:30 ` Fred Baker (fred)
2013-12-16 14:28 ` Jonathan Morton
2013-12-16 14:50 ` Steinar H. Gunderson
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=533BE7A9-7804-4A74-BBFB-C75CCE212434@cisco.com \
--to=fred@cisco.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=curtis@ipv6.occnc.com \
--cc=end2end-interest@postel.org \
/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