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

Explain TLS/QUIC key update differences #4576

Merged
merged 2 commits into from Jan 11, 2021
Merged

Explain TLS/QUIC key update differences #4576

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8c56d8d
Explain TLS/QUIC key update differences
martinthomson Jan 6, 2021
9d42f06
plural/not
martinthomson Jan 7, 2021
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
3 changes: 3 additions & 0 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Expand Up @@ -1452,6 +1452,9 @@ without needing to receive the first packet that triggered the change. An
endpoint that notices a changed Key Phase bit updates keys and decrypts the
packet that contains the changed value.

Initiating a key update results in both endpoints updating keys. This differs
from TLS where endpoints can update keys independently.

This mechanism replaces the key update mechanism of TLS, which relies on
KeyUpdate messages sent using 1-RTT encryption keys. Endpoints MUST NOT send a
TLS KeyUpdate message. Endpoints MUST treat the receipt of a TLS KeyUpdate
Expand Down