Dear Stephen:
Google gcc is a hybrid delay/loss webrtc protocol that is part of most
browsers today, and quite a few SFUs. It has been around since 2012 or
so. An RFC for it was started, here:
https://datatracker.ietf.org/doc/html/draft-ietf-rmcat-gcc-02
But as it grew to dominate the market,
On Sat, 5 Aug 2023 13:35:40 -0400
Sean DuBois via Bloat wrote:
> I am working on improving Pion's Google Congestion Control algorithm
> https://github.com/pion/interceptor/tree/master/pkg/gcc. As I start to use
> it in more real world networks I find flaws.
>
> How are people testing software
GREAT to hear from you sean! (I added you as "accept" to the bloat
list, but did not subscribe you. You can subscribe if you want to stay
on) I am delighted to see all the places pion is popping up now, most
recently I hear it is in matrix´s stacked SFU implementation? That is
a very interesting
I am working on improving Pion's Google Congestion Control algorithm
https://github.com/pion/interceptor/tree/master/pkg/gcc. As I start to use
it in more real world networks I find flaws.
How are people testing software today? Is 'Traffic Control' the best option?
> On Sat, Jul 1, 2023 at 12:23?AM Rodney W. Grimes
> wrote:
> >
> > > This paper does a really good job of measuring the impacts of tcp
> > > cross traffic, including BBRv2, against the videoconferencing
> > > subsystems in signal, telegram, and whatsapp.
> >
> > Did I miss something? The paper
> This paper does a really good job of measuring the impacts of tcp
> cross traffic, including BBRv2, against the videoconferencing
> subsystems in signal, telegram, and whatsapp.
Did I miss something? The paper only shows a dumb bell topology with
instream traffic, I did not see any cross flow
