Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include note about loss detection update #306

Open
michael-eriksson opened this issue Sep 26, 2024 · 0 comments
Open

Include note about loss detection update #306

michael-eriksson opened this issue Sep 26, 2024 · 0 comments

Comments

@michael-eriksson
Copy link

The example loss detection algorithm in Appendix A of RFC 9002 assumes that packets that arrives out of order are always acknowledged immediately. Because of this, it does not include max_ack_delay when the loss delay threshold is computed.

Setting the Ack-Eliciting Threshold field in the ACK_FREQUENCY frame to something else than 1 implies that some packets that arrive out of order will have delayed acknowledgments. Hence, the max_ack_delay should be added to the loss_delay variable in the algorithm above in those cases.

It would probably be valuable for implementers if this information was included in the document.

See also the quicdev Slack thread: https://quicdev.slack.com/archives/CTDAH4H71/p1725960809852329

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant