-
Notifications
You must be signed in to change notification settings - Fork 7
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
Explain compatibility for future QUIC versions #83
Comments
That's a good point, but I don't think we should make any change.
Would you agree? |
I agree with your summary. Should this document specify that the extension only works with QUIC versions that satisfy (1) - (3), but not (4)? |
Yes, I think it would be good to add a line to explain that if the behavior of stateless reset changes or other requirements are added, we need new capsules. |
A few things that can be done here:
|
The Register Target Connection ID capsule and the Virtual Connection ID capsule allow connection IDs of up to 255 bytes. This is because RFC 8999 allows up to 255 bytes, while RFC 9000 restricts them to 20 bytes.
The capsules also contain stateless reset tokens. However, stateless resets are not a concept defined in RFC 8999, they’re only defined in RFC 9000.
It seems like the hope when defining this extension is that once a new QUIC version that allows longer CIDs ships, it will still contain the concept of stateless reset tokens, with unchanged semantics and wire format. This might or might not hold true.
The text was updated successfully, but these errors were encountered: