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

What does "compatible" VN mean #90

Closed
ekr opened this issue Mar 8, 2022 · 1 comment · Fixed by #104
Closed

What does "compatible" VN mean #90

ekr opened this issue Mar 8, 2022 · 1 comment · Fixed by #104
Assignees

Comments

@ekr
Copy link
Contributor

ekr commented Mar 8, 2022

Consider the case where the client and server both support v1 and v2 and prefer v2.

In the current draft, if the client puts v1 in the long header and the server responds with v2, that's called "compatible version negotiation". OTOH, if the client puts v2 in the long header and the server responds with v2, that's called, well, I'm not quite sure what. I guess not negotiation?

I think a better way to think about this is that the client is sending an Initial that is compatible with both versions and so both of these cases are compatible version negotiation.

@DavidSchinazi
Copy link
Contributor

In the scenario where the client starts with v2 and the server responds with v2, I think of that as just "creating a v2 connection" without compatible version negotiation involved. Let's discuss this with the WG at IETF 113.

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

Successfully merging a pull request may close this issue.

2 participants