From: "Fred Baker (fred)" <fred@cisco.com>
To: Bob Briscoe <bob.briscoe@bt.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
"aqm@ietf.org" <aqm@ietf.org>,
"<end2end-interest@postel.org>" <end2end-interest@postel.org>
Subject: Re: [Bloat] [e2e] [aqm] What is a good burst? -- AQM evaluation guidelines
Date: Mon, 16 Dec 2013 07:34:52 +0000 [thread overview]
Message-ID: <80CEFF86-8687-4266-B87C-8FB5B894D4DF@cisco.com> (raw)
In-Reply-To: <201312152257.rBFMveZO022075@bagheera.jungle.bt.co.uk>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
On Dec 15, 2013, at 2:57 PM, Bob Briscoe <bob.briscoe@bt.com>
wrote:
> Fred,
>
> Jonathan Morton, Michael Scharf & I took Naeem's question to mean "What should an AQM assume the size of a good burst is?" whereas I think you and David C-B took the question to mean "What should an end-system take the size of a good burst to be?".
I can't comment on what he means. I took the question as "what should a system that is in receipt of what it might consider a 'burst', and more especially a 'good burst', to be?"
I don't know that a sending transport (which is to be distinguished from the queueing arrangement in that same system) or a receiving system *has* a definition of a "good" or "bad" burst. The one is sending data, which in the context of y two examples might be a good or bad idea, and the other is receiving it. From the receiver's perspective, the data either arrived or it didn't; if it arrived, there is no real argument for not delivering it to its application...
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2013-12-16 7:34 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)
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) [this message]
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=80CEFF86-8687-4266-B87C-8FB5B894D4DF@cisco.com \
--to=fred@cisco.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=bob.briscoe@bt.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