From: Dave Taht <dave.taht@gmail.com>
To: David Collier-Brown <davec-b@rogers.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Fwd: [CCWG] ETC: An Elastic Transmission Control Using End-to-End Available Bandwidth Perception
Date: Wed, 10 Jul 2024 15:28:28 -0700 [thread overview]
Message-ID: <CAA93jw407ukrN7BJoXQTDS8Fz0+g8+LLx1WMvkDjQsRArd_kqg@mail.gmail.com> (raw)
In-Reply-To: <9c5cb462-56ab-4a1d-a971-6cb1f437ced8@rogers.com>
[-- Attachment #1: Type: text/plain, Size: 3637 bytes --]
On Wed, Jul 10, 2024 at 3:11 PM David Collier-Brown via Bloat <
bloat@lists.bufferbloat.net> wrote:
> One of those papers that make you go "why didn't I think of that?"
>
> Of course, it does have to work (;-))
>
No sources, no email addresses, I am tempted to drop in on the conference
to see if any source is available.
There are a lot of ideas in there that I have been advocating a while -
varying the pacing rate (e!) to get an early estimate of congestion - and
quite a few more newer ones that seem excellent, like just treating the
leading edge of an ack as part of the estimator. Love how well it competes
with itself!
It's just a paper... no sources... agggh....
> --dave
> On 2024-07-10 16:40, Dave Taht via Bloat wrote:
>
> 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
>
> _______________________________________________
> Bloat mailing listBloat@lists.bufferbloat.nethttps://lists.bufferbloat.net/listinfo/bloat
>
> --
> David Collier-Brown, | Always do right. This will gratify
> System Programmer and Author | some people and astonish the restdavecb@spamcop.net | -- Mark Twain
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
https://www.linkedin.com/feed/update/urn:li:activity:7203400057172180992/
Donations Drive.
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 7003 bytes --]
next prev parent reply other threads:[~2024-07-10 22:28 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
2024-07-10 22:11 ` David Collier-Brown
2024-07-10 22:28 ` Dave Taht [this message]
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=CAA93jw407ukrN7BJoXQTDS8Fz0+g8+LLx1WMvkDjQsRArd_kqg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davec-b@rogers.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