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

Is the loss_timer_updated event sufficient? #319

Open
LPardue opened this issue Jul 5, 2023 · 1 comment
Open

Is the loss_timer_updated event sufficient? #319

LPardue opened this issue Jul 5, 2023 · 1 comment

Comments

@LPardue
Copy link
Member

LPardue commented Jul 5, 2023

We've had the following todo's for loss_timer_updated in the quic schema for a while, pulling them out into this issue

  1. TODO: how about CC algo's that use multiple timers? How generic do these events
    need to be? Just support QUIC-style recovery from the spec or broader?

  2. TODO: read up on the loss detection logic in draft-27 onward and see if this suffices

@LPardue LPardue changed the title Is the loss_timer_updated event sufficient Is the loss_timer_updated event sufficient? Jul 5, 2023
LPardue added a commit that referenced this issue Jul 5, 2023
LPardue added a commit that referenced this issue Jul 7, 2023
@LPardue
Copy link
Member Author

LPardue commented Nov 4, 2024

I'm guessing we are looking for volunteers to help us here. We can ask. In the absence of someone offering it, we can use the WGLC as an indicator that there is consensus on what is already in the draft as sufficient.

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