General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd: [CCWG] ETC: An Elastic Transmission Control Using End-to-End Available Bandwidth Perception
Date: Wed, 10 Jul 2024 13:40:24 -0700	[thread overview]
Message-ID: <CAA93jw5BKtnB7LRnu+r1C2oBNh6aSbHZ7MY3q3D_FgW-e4XF0w@mail.gmail.com> (raw)
In-Reply-To: <CAFvDQ9pPf8eUoTEGYTELQpf2yGG10vF3ADsnk2oeca1dFrsBEQ@mail.gmail.com>

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

very encouraging

---------- Forwarded message ---------
From: Hesham ElBakoury <helbakoury@gmail.com>
Date: Wed, Jul 10, 2024 at 1:34 PM
Subject: [CCWG] ETC: An Elastic Transmission Control Using End-to-End
Available Bandwidth Perception
To: <ccwg@ietf.org>


This paper [1] is published in this week USENIX ATC 2024. It is an
interesting paper with surprising results.

*Paper Abstract*
"Researchers and practitioners have proposed various transport protocols to
keep up with advances in networks and the applications that use them.
Current Wide Area Network protocols strive to identify a congestion signal
to make distributed but fair judgments. However, existing congestion
signals such as RTT and packet loss can only be observed after congestion
occurs. We therefore propose Elastic Transmission Control (ETC). ETC
exploits the instantaneous receipt rate of N consecutive packets as the
congestion signal. We refer to this as the pulling rate, as we posit that
the receipt rate can be used to “pull” the sending rate towards a fair
share of the capacity. Naturally, this signal can be measured prior to
congestion, as senders can access it immediately after the acknowledgment
of the first N packets. Exploiting the pulling rate measurements, ETC
calculates the optimal rate update steps following a simple elastic
principle: the further away from the pulling rate, the faster the sending
rate increases. We conduct extensive experiments using both simulated and
real networks. Our results show that ETC outperforms the state-of-the-art
protocols in terms of both throughput (15% higher than Copa) and latency
(20% lower than BBR). Besides, ETC shows superiority in convergence speed
and fairness, with a 10× im-provement in convergence time even compared to
the protocol with the best convergence performance."

Hesham
[1] https://www.usenix.org/conference/atc24/presentation/han
-- 
CCWG mailing list -- ccwg@ietf.org
To unsubscribe send an email to ccwg-leave@ietf.org


-- 
https://www.linkedin.com/feed/update/urn:li:activity:7203400057172180992/
Donations Drive.
Dave Täht CSO, LibreQos

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

       reply	other threads:[~2024-07-10 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFvDQ9pPf8eUoTEGYTELQpf2yGG10vF3ADsnk2oeca1dFrsBEQ@mail.gmail.com>
2024-07-10 20:40 ` Dave Taht [this message]
2024-07-10 22:11   ` David Collier-Brown
2024-07-10 22:28     ` Dave Taht
2024-07-10 22:44       ` Stephen Hemminger
2024-07-11  0:28         ` David Collier-Brown

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=CAA93jw5BKtnB7LRnu+r1C2oBNh6aSbHZ7MY3q3D_FgW-e4XF0w@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    /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