General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: Steffan Norberhuis <steffan@norberhuis.nl>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Solving bufferbloat with TCP using packet delay
Date: Wed, 03 Apr 2013 20:14:46 +0200	[thread overview]
Message-ID: <87zjxfscq1.wl%jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <CADC3P9nHcmb214w7edufkkdqhS14EG9AigUqzC_4cLhcY7fDzQ@mail.gmail.com>

> - Is TCP using packet delay considered as part of the solution for
> bufferbloat?

Not on this list, apparently.  However, there has been a fair amount
of research on that approach in the late noughts.  I'd suggest
you search for papers on TCP Vegas, TCP-LP and LEDBAT.

In particular, LEDBAT is very widely deployed as part of uTP.  (Your
students are probably using it right now for making a backup of their
DVD collection.)

> - What are the problems of TCP delay variants that keep it from
> solving bufferbloat?

The main issue is the so-called late joiner advantage: these
algorithms tend to give an unfair advantage to flows that only joined
when the network was already congested, as compared to older flows.
I don't know if the issue has been solved yet, it's been some time
since I last looked at that stuff.

> - What are the drawbacks of the TCP delay variants that would favor
> AQM over TCP?

> - What are the advantages of TCP delay varaints that would favor TCP
> over AQM?

Please be aware that they are not competitors: the two can coexist in
the same network.  I would say that there is consensus that AQM is
necessary, and that delay-based congestion control is a nice thing to
have for low-priority traffic (e.g. uTP).  In other words, you cannot
do without AQM, but that certainly doesn't mean there aren't people
interested in deploying low-delay congestion control.

-- Juliusz

      parent reply	other threads:[~2013-04-03 18:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 15:36 Steffan Norberhuis
2013-03-20 15:55 ` Dave Taht
2013-03-20 16:12 ` Oliver Hohlfeld
2013-03-20 16:35 ` Michael Richardson
2013-03-20 20:21 ` grenville armitage
2013-03-20 23:16   ` Stephen Hemminger
2013-03-21  1:01     ` Jonathan Morton
2013-03-26 13:10       ` Maarten de Vries
2013-03-26 13:24         ` Jonathan Morton
2013-04-04  0:10       ` Simon Barber
2013-03-21  8:26     ` Hagen Paul Pfeifer
2013-04-03 18:16     ` Juliusz Chroboczek
2013-04-03 18:23       ` Hagen Paul Pfeifer
2013-04-03 19:35         ` Juliusz Chroboczek
2013-04-03 18:14 ` Juliusz Chroboczek [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=87zjxfscq1.wl%jch@pps.univ-paris-diderot.fr \
    --to=jch@pps.jussieu.fr \
    --cc=bloat@lists.bufferbloat.net \
    --cc=steffan@norberhuis.nl \
    /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