From: Michael Richardson <mcr@sandelman.ca>
To: Juliusz Chroboczek <jch@irif.fr>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] impressed with my starlink today
Date: Mon, 18 Sep 2023 14:40:36 -0400 [thread overview]
Message-ID: <8658.1695062436@localhost> (raw)
In-Reply-To: <87msxjqwhj.wl-jch@irif.fr>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
Juliusz Chroboczek via Starlink <starlink@lists.bufferbloat.net> wrote:
> We're currently using receiver-driven congestion control, which is
> deprecated in WebRTC. The plan is to switch to sender-driven congestion
> control at some point (I'm no big fan, but that's what everyone is
> implementing, and we better be compatible with the rest of the universe).
...
> (I could in principle use receiver-driven for the downstream and
> sender-driven for the upstream, thus using libwebrtc's excellent
> controllers in both directions, but it really feels like a hack. I'd
> much rather not negociate receiver-driven at all.)
If I understand correctly, galene would support p2p media streams?
The web page seems to focus on lecture style.
It seems to me that if you have multiple outgoing streams, that if there are
problems with any of them, a sender-driven system allows for better use of
what is typically a smaller uplink.
--
] 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 [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2023-09-18 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 22:44 Dave Taht
2023-09-18 13:18 ` Livingood, Jason
2023-09-18 14:13 ` Dave Taht
2023-09-18 16:25 ` Juliusz Chroboczek
2023-09-18 18:40 ` Michael Richardson [this message]
2023-09-18 19:44 ` Frantisek Borsik
2023-09-18 19:57 ` Juliusz Chroboczek
2023-09-18 20:18 ` Frantisek Borsik
2023-09-18 19:48 ` Juliusz Chroboczek
2023-09-18 19:37 ` David Lang
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8658.1695062436@localhost \
--to=mcr@sandelman.ca \
--cc=jch@irif.fr \
--cc=starlink@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