QUIC: position of RTT and congestion
Maxim Konovalov
maxim at nginx.com
Sun Dec 4 04:53:53 UTC 2022
Hi,
Your patches are more than welcome.
Maxim
On 01.12.2022 02:57, 朱宇(黎叔) via nginx-devel wrote:
> Thank you for the reply. And one question follows:
>
> Will the patches from community of such features be accepted , or should
> wait for official updates?
>
>
>
> ------------------原始邮件 ------------------
> *发件人:*Vladimir Homutov via nginx-devel <nginx-devel at nginx.org>
> *发送时间:*Wed Nov 30 20:33:18 2022
> *收件人:*Vladimir Homutov via nginx-devel <nginx-devel at nginx.org>
> *抄送:*Vladimir Homutov <vl at inspert.ru>
> *主题:*Re: QUIC: position of RTT and congestion
>
> On Wed, Nov 30, 2022 at 08:10:29PM +0800, Yu Zhu wrote:
> >
> > Hi,
> >
> > As described in "rfc 9002 6. Loss Detection", "RTT and congestion
> > control are properties of the path", so moves first_rtt,
> > latest_rtt, avg_rtt, min_rtt, rttvar and congestion from
> > ngx_quic_connection_t to struct ngx_quic_path_t looks more
> > reasonable?
>
> yes, you are right.
>
> Currently per-path calculations are not implemented, as well as path mtu
> discovery and some other things.
>
> _______________________________________________
> nginx-devel mailing list -- nginx-devel at nginx.org
> To unsubscribe send an email to nginx-devel-leave at nginx.org
>
>
> _______________________________________________
> nginx-devel mailing list -- nginx-devel at nginx.org
> To unsubscribe send an email to nginx-devel-leave at nginx.org
--
Maxim Konovalov
More information about the nginx-devel
mailing list