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.

Sign up for GitHub

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

Jump to bottom

What to do if a skipped packet is acknowledged #546

Closed
martinthomson opened this issue May 22, 2017 · 3 comments
Closed

What to do if a skipped packet is acknowledged #546

martinthomson opened this issue May 22, 2017 · 3 comments
Labels
-recovery -transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.

Comments

@martinthomson
Copy link
Member

#415 was submitted, but I think that that was in error.
@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. -recovery -transport labels May 22, 2017
@martinthomson
Copy link
Member Author

To be clear, I think that the transport document is where this sort of requirement belongs.

@mnot mnot added this to Reliability in QUIC May 22, 2017
@ianswett
Copy link
Contributor

I tend to agree, now that you mention it. The reference to a connection close error makes it clearer to me that it should be in transport.

@ianswett
Copy link
Contributor

Closed with PR #555

@martinthomson martinthomson removed this from Reliability in QUIC Jun 6, 2017
@mnot mnot added the has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. label Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-recovery -transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@martinthomson @mnot @ianswett