From: Rick Jones <rick.jones2@hp.com>
To: Jim Gettys <jg@freedesktop.org>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Traffic patterns for AQM testing.... Bursty behaviour of video players.
Date: Fri, 27 Jan 2012 13:42:39 -0800 [thread overview]
Message-ID: <4F231A4F.1040006@hp.com> (raw)
In-Reply-To: <4F22DA7F.6090302@freedesktop.org>
> In the short term, I need to understand what current TCP systems
> *should* do in the face of long idle periods, which invalidate the
> congestion information.
Is your glass half-empty and/or has a leak? Then TCP should decay or
reset its cwnd while/when idle.
Is your glass half-full? Then TCP should leave the cwnd alone.
Both are ass-u-me-ing something about the state of the path between the
sender and the receiver.
rick jones
prev parent reply other threads:[~2012-01-27 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 20:04 Jim Gettys
2012-01-26 20:14 ` Justin McCann
2012-01-26 20:48 ` Paul Gleichauf
2012-01-27 17:10 ` Jim Gettys
2012-01-27 18:11 ` Eggert, Lars
2012-01-27 21:42 ` Rick Jones [this message]
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=4F231A4F.1040006@hp.com \
--to=rick.jones2@hp.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jg@freedesktop.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