On Tue, Jun 13, 2023, at 23:20, Marten Seemann wrote: > quic-go therefore neither sends nor acts upon ACK delays reported in > Initial packets. I thought we had text about that in the RFC, but I > can't find it. Same (modulo the below). Should we open an issue to track that? I think that our approach is different. We accept delays, but they will be bounded in their impact (minimum RTT bounds it on one end, and zero bounds it on the other) and we simply accept that.
- ack_delay_exponent, and acks received before transport p... Damien Neil
- Re: ack_delay_exponent, and acks received before tr... Marten Seemann
- Re: ack_delay_exponent, and acks received befor... Damien Neil
- Re: ack_delay_exponent, and acks received befor... Martin Thomson
- Re: ack_delay_exponent, and acks received befor... Damien Neil
- Re: ack_delay_exponent, and acks received before tr... Lars Eggert
- Re: ack_delay_exponent, and acks received befor... Damien Neil
- Re: ack_delay_exponent, and acks received b... Christian Huitema
- Re: ack_delay_exponent, and acks receiv... Kazuho Oku
- Re: ack_delay_exponent, and acks r... Damien Neil
- Re: ack_delay_exponent, and acks r... Martin Thomson
- Re: ack_delay_exponent, and acks received b... Lars Eggert
- Re: ack_delay_exponent, and acks receiv... Damien Neil
