General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Naeem Khademi <naeem.khademi@gmail.com>
To: "aqm@ietf.org" <aqm@ietf.org>,
	bloat <bloat@lists.bufferbloat.net>,
	 end2end-interest@postel.org
Subject: [Bloat] What is a good burst? -- AQM evaluation guidelines
Date: Sun, 15 Dec 2013 06:35:04 +0100	[thread overview]
Message-ID: <CAEjQQ5XPiqL9ywD3zXGKvUb_FoWmgJ3Zq_g_b8ONfHieHaRWzg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 454 bytes --]

Hi all

I'm not sure if this has already been covered in any of the other threads,
but looking at http://www.ietf.org/proceedings/88/slides/slides-88-aqm-5.pdfand
draft-ietf-aqm-recommendation-00, the question remains: "what is a
good
burst (size) that AQMs should allow?" and/or "how an AQM can have a notion
of the right burst size?".

and how "naturally-occuring bursts" mentioned in
draft-ietf-aqm-recommendation-00
can be defined?



Regards,
Naeem

[-- Attachment #2: Type: text/html, Size: 800 bytes --]

             reply	other threads:[~2013-12-15  5:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-15  5:35 Naeem Khademi [this message]
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)
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=CAEjQQ5XPiqL9ywD3zXGKvUb_FoWmgJ3Zq_g_b8ONfHieHaRWzg@mail.gmail.com \
    --to=naeem.khademi@gmail.com \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --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