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

reserved versions don't need to be generated deterministically #831

Closed
marten-seemann opened this issue Oct 3, 2017 · 0 comments
Closed

reserved versions don't need to be generated deterministically #831

marten-seemann opened this issue Oct 3, 2017 · 0 comments
Labels
-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

@marten-seemann
Copy link
Contributor

marten-seemann commented Oct 3, 2017 •
edited
Loading

The client doesn't check that the version numbers sent in the Version Negotiation Packet exactly match those sent in the Transport Parameters, it just checks that

  1. a change of the version number was necessary and
  2. it would have selected the current version.

Therefore, a server might as well send different reserved version numbers in VNP and Transport Parameters, which will simplify implementations (they don't need to do any derivation based on client address and initial version).
@marten-seemann marten-seemann mentioned this issue Oct 5, 2017
Closed
@martinthomson martinthomson added -transport design An issue that affects the design of the protocol; resolution requires consensus. labels Nov 14, 2017
@marten-seemann marten-seemann mentioned this issue Nov 15, 2017
Merged
@mnot mnot added has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. and removed has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. labels 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
-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 @marten-seemann