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 identification of version 1 ossification? #342

Closed
martinthomson opened this issue May 6, 2021 · 0 comments
Closed

Is identification of version 1 ossification? #342

martinthomson opened this issue May 6, 2021 · 0 comments

Comments

@martinthomson
Copy link
Member

@martinthomson martinthomson commented May 6, 2021

Is this a promise?

An in-network observer assuming that a set of packets belongs to a QUIC flow can infer the version number in use by observing the handshake: for QUIC version 1, if the version number in the Initial packet from a client is the same as the version number in the Initial packet of the server response, that version has been accepted by both endpoints to be used for the rest of the connection.

Because there are a number of designs floating around that would allow a client and server to agree - out of band or by prior arrangement - that version 1 means something else entirely.

If the above were a promise, that's perhaps reasonable. It is an interpretation that seems consistent with the invariants. However, the invariants don't make this particular (that was deliberate), so this is technically stretching it.

This might be better phrased with a "might infer the version number in use" to admit the possibility of error.

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

Successfully merging a pull request may close this issue.

3 participants