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

require peers to check if RETIRE_CONNECTION_ID sequence number is valid #3036

Merged

Conversation

marten-seemann
Copy link
Contributor

@marten-seemann marten-seemann commented Sep 16, 2019

When it comes to error checks for protocol violations, our principle is that easy to implement error checks are REQUIRED. Only error checks that might require a lot of state to perform are optional.

The check that the sequence number retired in a RETIRE_CONNECTION_ID frame is smaller than the highest issued connection ID is a single trivial uint64 comparison. Furthermore, every implementation needs to track the highest issued sequence number anyway, since connection IDs are issued in order.

Fixes #3037

@ianswett
Copy link
Contributor

This is small and I support it, but I think it needs to be marked design and run through the process because it changes normative language.

@martinthomson martinthomson added the design An issue that affects the design of the protocol; resolution requires consensus. label Oct 31, 2019
@martinthomson martinthomson merged commit ba07711 into quicwg:master Nov 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Require peers to check if RETIRE_CONNECTION_ID sequence number is valid
4 participants