From: T H Panton <tim@pi.pe>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: using up more ports in ipv6 for better congestion control
Date: Fri, 16 Jul 2021 16:46:41 +0200 [thread overview]
Message-ID: <0AA86EE7-3FFA-4764-A0B2-A6C18A6A231E@pi.pe> (raw)
In-Reply-To: <878s27aviv.wl-jch@irif.fr>
> On 16 Jul 2021, at 03:37, Juliusz Chroboczek <jch@irif.fr> wrote:
>
>>> Tim, I'd be very grateful if you could explain what advantages TWCC has
>>> over REMB. For now, I'm sticking with REMB.
>
>> I can’t speak from experience (I’ve only used REMB) - but my sense is
>> that the difference really kicks in when you have multiple video media
>> streams using the same path. So perhaps video, screen share and
>> audio. REMB treats each stream separately if I recall.
>
> Then REMB could be modified to perform per-connection congestion control,
> just like TWCC, without all of the chattiness of TWCC.
I don’t think it could. - isn't REMB based on watching the packet arrival interval which is
pretty consistent on a single stream. But imagine multiplexing some opus (50 fps)
a screenshare (10fps) a thumbnail (15fps) and a presenter view (60 fps), you now have
multiple valid packet intervals (in some sort of repeating pattern).
I imagine that would make the smoother in REMB go badly wrong.
TWCC is based on watching the time of flight - which doesn’t have that problem.
>
> I really feel that I'm missing something.
>
> -- Juliusz
next prev parent reply other threads:[~2021-07-16 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 15:15 [Galene] " Dave Taht
2021-07-10 15:19 ` [Galene] " Dave Taht
2021-07-10 16:36 ` T H Panton
2021-07-10 16:48 ` Dave Taht
2021-07-11 11:19 ` Juliusz Chroboczek
2021-07-15 14:17 ` Sean DuBois
2021-07-16 1:36 ` Juliusz Chroboczek
2021-07-16 14:25 ` Sean DuBois
2021-07-15 16:26 ` T H Panton
2021-07-16 1:37 ` Juliusz Chroboczek
2021-07-16 14:46 ` T H Panton [this message]
2021-07-16 17:48 ` Juliusz Chroboczek
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.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0AA86EE7-3FFA-4764-A0B2-A6C18A6A231E@pi.pe \
--to=tim@pi.pe \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
/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