-
Notifications
You must be signed in to change notification settings - Fork 203
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
Transport parameters can be used before they are authentic #4463
Conversation
This is OK, but only in a limited fashion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the changes add clarity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the limitations could be a be clearer, but heading in a good direction.
draft-ietf-quic-tls.md
Outdated
and reliance on them should be minimized. However, any tampering with the | ||
parameters will cause the handshake to fail. | ||
Transport parameters become available prior to the completion of the handshake. | ||
Using these values earlier than handshake completion is necessary at the server |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure it's necessary to send 1-RTT packets prior to handshake completion, but it is necessary to send many things, such as data on streams in 0.5RTT packets.
Also, the way this is written, it could be read as sending 1-RTT packets from server to client requires using these values prior to handshake completion, which I realize isn't your intent.
Co-authored-by: Jana Iyengar <jri.ietf@gmail.com>
This is OK, but only in a limited fashion.