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

Martin Duke TLS Comment 1 #4465

Closed
LPardue opened this issue Dec 29, 2020 · 1 comment · Fixed by #4463
Closed

Martin Duke TLS Comment 1 #4465

LPardue opened this issue Dec 29, 2020 · 1 comment · Fixed by #4463
Labels
-tls iesg An issue raised during IESG review.
Milestone

Comments

@LPardue
Copy link
Member

LPardue commented Dec 29, 2020

@martinduke said:

The third-to-last paragraph of Sec 4.1.3 implies that the transport
parameters are not delivered until the handshake is complete. In 8.2 it says
that the TPs are "available" but "not fully trusted" before completion. The
latter is certainly true; but the server can't send 0.5-RTT packets (e.g. a
SETTINGS frame) without any indication of the client transport parameters. I
would suggest a clarification in 4.1.3 and letting the language in 8.2 stand.

@LPardue LPardue added -tls iesg An issue raised during IESG review. labels Dec 29, 2020
@LPardue LPardue added this to the tls-iesg milestone Dec 29, 2020
@LPardue LPardue linked a pull request Dec 29, 2020 that will close this issue
@LPardue
Copy link
Member Author

LPardue commented Dec 29, 2020

Proposed resolution is #4463

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-tls iesg An issue raised during IESG review.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant