From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>,
"hqjiang1988@gmail.com" <hqjiang1988@gmail.com>
Cc: "dada1@cosmosbay.com" <dada1@cosmosbay.com>
Subject: Re: [Bloat] Tackling bufferbloat in 3G/4G networks: A receiver-based TCP solution
Date: Tue, 5 Jun 2012 16:32:49 +0200 [thread overview]
Message-ID: <DBB1DC060375D147AC43F310AD987DCC4D6CF25618@ESESSCMS0366.eemea.ericsson.se> (raw)
In-Reply-To: <mailman.5.1338836403.6573.bloat@lists.bufferbloat.net>
Hi
And thanks for an interesting report. I must say that this resembles LEDBAT quite a lot, with the exception that LEDBAT is a (mainly) sender based modification and may thus be easier to deploy. Like commented on this list (by Jonathan Morton for instance) it could be interesting to see how they compare.
One flaw with delay based algos (which LEDBAT tries to solve) is the sensitivity to reverse path delay (similar issue with Vegas I believe), I guess your algorithm can have the same problem or. Does not mean that LEDBAT is free of problem...
Regards
/Ingemar Johansson
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 3 Jun 2012 18:32:49 -0700
> From: Haiqing Jiang <hqjiang1988@gmail.com>
> To: Eric Dumazet <dada1@cosmosbay.com>, Dave Taht
> <dave.taht@gmail.com>
> Cc: bloat@lists.bufferbloat.net
> Subject: [Bloat] Tackling bufferbloat in 3G/4G networks: A
> receiver-based TCP solution.
> Message-ID:
>
> <CAO-4OdHYZGkqd_XHqxSBiM9+Z93gx3rFYrv6i8zeO+9U_aQACA@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi, All,
>
> Recently the researchers from Networking Research Group of
> North Carolina State University (NCSU) have proposed an
> interesting receiver-based TCP solution to tackle bufferbloat
> in 3g/4g networks.
>
> They conducted extensive measurements in four major carriers
> in US and the largest carrier in Korea to verify the severe
> bufferbloat problem in currently commercial cellular
> networks. They cited the work from Bufferbloat group and
> further extended the work to cellular networks. Furthermore,
> they revealed the untold implementation of TCP, an ad-hoc
> solution to mitigate bufferbloat, in smartphone's network
> stack (Android platform). The ad-hoc solution is sub-optimal
> in many scenarios.
> Actually it merely mitigate bufferbloat problem in some scenarios.
> Therefore, the guys from NCSU propose a "Dynamic Receive
> Window Adjustment"
> scheme to tackle bufferbloat problem. The extensive
> experiment results prove that the scheme is efficient and
> light-weight.
>
> It's really excited to find the new direction to tackle
> bufferbloat, on TCP layer instead of routers (like AQM). The
> bufferbloat problem actually seems to be the most prominent,
> comparing with other networks.
> Therefore, we suggest the more efforts to tackling
> bufferbloat problem in cellular networks and seeking a good
> solution in TCP layer space.
>
> The link is attached:
> ftp://ftp.ncsu.edu/pub/unity/lockers/ftp/csc_anon/tech/2012/TR
> -2012-6.pdf
>
> Thanks,
>
> --
> -----------------------------------
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://lists.bufferbloat.net/pipermail/bloat/attachments/201
> 20603/e71887b8/attachment-0001.html>
>
> ------------------------------
>
next parent reply other threads:[~2012-06-05 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1338836403.6573.bloat@lists.bufferbloat.net>
2012-06-05 14:32 ` Ingemar Johansson S [this message]
[not found] <mailman.1.1338922801.461.bloat@lists.bufferbloat.net>
2012-06-06 12:30 ` [Bloat] Tackling bufferbloat in 3G/4G networks: A receiver-based, " David Collier-Brown
2012-06-04 1:32 [Bloat] Tackling bufferbloat in 3G/4G networks: A receiver-based " Haiqing Jiang
2012-06-04 3:06 ` Jonathan Morton
2012-06-04 9:01 ` Dave Taht
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=DBB1DC060375D147AC43F310AD987DCC4D6CF25618@ESESSCMS0366.eemea.ericsson.se \
--to=ingemar.s.johansson@ericsson.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dada1@cosmosbay.com \
--cc=hqjiang1988@gmail.com \
/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