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

Separate key/secret availability from usage #1654

Merged
merged 3 commits into from Aug 14, 2018
Merged

Separate key/secret availability from usage #1654

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3dcfe95
Separate key/secret availability from usage
martinthomson Aug 13, 2018
ab5c19f
More text
martinthomson Aug 14, 2018
7632df3
Grammar!
martinthomson Aug 14, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 2 additions & 3 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Expand Up @@ -459,9 +459,8 @@ frame at the Handshake encryption level) an endpoint can send STREAM data (in
1-RTT encryption). If the Finished message is lost, the endpoint uses the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might actually be more instructive to talk about CRYPTO frames at different levels. Maybe the 1-RTT data could be a New Session Ticket in a CRYPTO frame?

Handshake encryption level to retransmit the lost message. Reordering or loss
of packets can mean that QUIC will need to handle packets at multiple encryption
levels. During the handshake, this means potentially handling of packets at
higher and lower encryption levels than the current encryption level used by
TLS.
levels. During the handshake, this means potentially handling packets at higher
and lower encryption levels than the current encryption level used by TLS.

In particular, server implementations need to be able to read packets at the
Handshake encryption level before the final TLS handshake message at the 0-RTT
Expand Down