-
Notifications
You must be signed in to change notification settings - Fork 204
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
Update Initial salt, Retry keys, and samples for -29 #3711
Conversation
Any chance we could also update the initial salt? |
I was saving that for the final version, by popular demand. If you have a reason to change, then I can do that (I'll also want to update the keys for Retry in that case). |
I agree with @martinthomson. Let's leave the salt update to the final version. |
With Google's QUIC deployment, we're already experiencing version ossification due to middleboxes inspecting initial packets - some of our traffic is stuck on older versions of GoogleQUIC because of this. Changing the salts every time we change the version number will help remind everyone that this is not an ossified aspect of the protocol. The cost to implementors is pretty much zero. @rpaulo out of curiosity, why the pushback? |
What @DavidSchinazi says makes sense to me, so I would be in favor of shipping draft-29 with new salts. |
I updated the salts and the test vectors in quic-go, and I can confirm that the values match. |
…ial_salt Update Initial salt, Retry keys, and samples (#3711) to changelog
No description provided.