public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Injong Rhee" <rhee@eos.ncsu.edu>
To: <end2end-interest@postel.org>
Cc: netdev@vger.kernel.org
Subject: Stability of various TCP protocols [CUBIC, BIC, HTCP, HSTCP, STCP]
Date: Thu, 28 Sep 2006 12:58:02 -0400	[thread overview]
Message-ID: <00d301c6e31f$4304fed0$4a580e98@ncsu2cc0c3fa00> (raw)

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

Hi,
I'd like to report on a measurement study regarding the stability of various TCP variant protocols. Although we can find quite a bit of work on fairness and convergence of protocols (including some theoretical studies on the topic as well), there is relatively little work on measuring the stability of protocols and its impact on protocol performance and overall health of the networks (e.g., the overall queue fluctions and link utilization). We have measured the degree of rate oscillation and fluctuation of protocols to have some understanding of protocol stability. 
We would like to share our results with you to get some feedback from the community. 

We have some theoretical results and also experimental results. Here is the link to the experimental results. You can find links to all of our experimental data that include results from several hundred experiments.

http://netsrv.csc.ncsu.edu/convex-ordering/

If you need our report on theoretical results,  we can e-mail you the report.
Injong Rhee

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

             reply	other threads:[~2006-09-28 16:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28 16:58 Injong Rhee [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-28 17:00 Stability of various TCP protocols [CUBIC, BIC, HTCP, HSTCP, STCP] Injong Rhee

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00d301c6e31f$4304fed0$4a580e98@ncsu2cc0c3fa00' \
    --to=rhee@eos.ncsu.edu \
    --cc=end2end-interest@postel.org \
    --cc=netdev@vger.kernel.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