From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht via Bloat <bloat@lists.bufferbloat.net>
Cc: Dave Taht <dave.taht@gmail.com>,
David Collier-Brown <davec-b@rogers.com>
Subject: Re: [Bloat] Fwd: [CCWG] ETC: An Elastic Transmission Control Using End-to-End Available Bandwidth Perception
Date: Wed, 10 Jul 2024 15:44:03 -0700 [thread overview]
Message-ID: <20240710154403.5b49c902@hermes.local> (raw)
In-Reply-To: <CAA93jw407ukrN7BJoXQTDS8Fz0+g8+LLx1WMvkDjQsRArd_kqg@mail.gmail.com>
On Wed, 10 Jul 2024 15:28:28 -0700
Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
> 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....
Poking around a little, author seems to be associated with:
FutureWei Technolgies http://futurewei.com
Which has various Open Source marketing stuff in their vision but no
github or download links.
next prev parent reply other threads:[~2024-07-10 22:44 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
2024-07-10 22:44 ` Stephen Hemminger [this message]
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=20240710154403.5b49c902@hermes.local \
--to=stephen@networkplumber.org \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--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