[Bloat] [e2e] [aqm] What is a good burst? -- AQM evaluation guidelines

Fred Baker (fred) fred at cisco.com
Mon Dec 16 02:34:52 EST 2013

On Dec 15, 2013, at 2:57 PM, Bob Briscoe <bob.briscoe at bt.com>

> 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...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.bufferbloat.net/pipermail/bloat/attachments/20131216/5e7a7d35/attachment-0001.sig>

More information about the Bloat mailing list