Re: [tsvwg] QUIC with L4S

[Vidhi Goel <[e-mail]>]

>>> Is there a new Prague draft? I could only find an obsolete draft from 2019. Maybe I did not look in the right places.
>> This is the latest - https://datatracker.ietf.org/doc/html/draft-briscoe-iccrg-prague-congestion-control-00
> 
> Yes, that's the one I used. But it expired in September 2021. Please someone starts a new version, then get it to be discussed and progress!

We are working on this. Will post on the ML when the new version is out.

Thanks,
Vidhi

> On Jul 5, 2022, at 4:45 PM, Christian Huitema <[e-mail]> wrote:
> 
> 
> On 7/5/2022 4:24 PM, Vidhi Goel wrote:
>> Thank you Christian for resuming the work on scalable CC. I have been using picoQUIC as a receiver for my testing and once you merge it to main, I would use it as a sender too.
>> 
>>> Is there a new Prague draft? I could only find an obsolete draft from 2019. Maybe I did not look in the right places.
>> This is the latest - https://datatracker.ietf.org/doc/html/draft-briscoe-iccrg-prague-congestion-control-00
> 
> Yes, that's the one I used. But it expired in September 2021. Please someone starts a new version, then get it to be discussed and progress!
> 
>> 
>> All your points are valid and I have noted them.
>> 
>>> I also had to try a couple of different settings for the threshold value used in the simulation. Too low, and the throughput drops. Too high, and the amount of losses increases too much. In the tests, the router has a queue size of 1 BDP, and setting the threshold to BDP/4 appears to work well.
>> Which AQM are you using on your router? For me setting fixed threshold = 2ms when testing over Ethernet and threshold = 4ms when testing over Wi-Fi worked well.
> 
> This was tested on a simulation. I was first testing a 10 Mbps link with 20ms RTT. Threshold was set to 5 ms -- 1/4th of RTT.
> 
> -- Christian Huitema
>