From: "Holland, Jake" <jholland@akamai.com>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Congestion control with FQ-Codel/Cake with Multicast?
Date: Thu, 23 May 2024 23:15:26 +0000 [thread overview]
Message-ID: <B174EB9E-0964-437F-86E2-87BCB58A97DA@akamai.com> (raw)
In-Reply-To: <A7CFFD21-1EF5-48A0-92AC-A62D9C589489@akamai.com>
Hi Linus,
One correction on that last message:
After sending and re-reading I belatedly realized it's completely viable to
snoop SDP over SAP if you wanted to. So I guess it's not a non-starter if
you don't care about solving other kinds of multicast traffic in addition to
the ones in that can announce SDP to the SAP channels you can watch.
I'm not sure why it wouldn't be better to make a separate service that
coordinates the channels in use since the SAP channels will probably have
to do that anyway, but on reflection I think snooping SDP is probably
more viable than I gave it credit for. My caution there would be that in
a network where multicast can get delivered and people are using it, I
would think someone might start doing SDP outside the SAP channels at
the app level, or maybe doing other kinds of multicast traffic. So I'd
imagine it only can lead to a partial solution, but it could be useful.
Apologies for my confusion.
Best regards,
Jake
next prev parent reply other threads:[~2024-05-23 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 14:56 Linus Lüssing
2024-05-21 15:25 ` Linus Lüssing
2024-05-23 21:43 ` Holland, Jake
2024-05-23 23:15 ` Holland, Jake [this message]
2024-05-25 11:15 ` Jonathan Morton
2024-05-24 13:58 ` Toke Høiland-Jørgensen
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=B174EB9E-0964-437F-86E2-87BCB58A97DA@akamai.com \
--to=jholland@akamai.com \
--cc=bloat@lists.bufferbloat.net \
--cc=linus.luessing@c0d3.blue \
/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