From: Michael Richardson <mcr@sandelman.ca>
To: codel@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: [Codel] keynote talk at devnetconf
Date: Wed, 07 Jul 2021 15:57:31 -0400 [thread overview]
Message-ID: <4243.1625687851@localhost> (raw)
https://netdevconf.info/0x15/session.html?keynote-balakrishnan
Hari Balakrishnan did a 1hr keynote on the "bundler-project", which aims
basically to generate a estimate of available bandwidth between sites.
i.e. between your corporate network or DC, and some other DC (e.g. EC2 us-west-1)
The goal being that, if one can estimate the available bandwidth, then one
can move your congestion from some unknown cloud router to one's edge router
where one can better control it with, e.g. fq_codel.
Of course, this only works for traffic to the places where you've deployed
bundler, and there is the problem of other people's traffic also going to
that destination ("cross-traffic" he called it).
I found it interesting.
It doesn't solve the problem that I've long been obsessed about, which is
finding a way to estimate the total bandwidth cross that "l2" hop between
a home CPE and the ISP "CMTS" or "BNG"... such that we can auto-tune things.
IETF watchers might also care about the APN (really poorly named in the end)
BOF, where one use case they care about is where the "L2" hop is actually a
large metro-ethernet.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
reply other threads:[~2021-07-07 19:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4243.1625687851@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@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