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

Fix verb ownership: a packet does not process packets #2799

Merged
merged 1 commit into from Jun 20, 2019
Merged

Fix verb ownership: a packet does not process packets #2799

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 6 additions & 5 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Expand Up @@ -1213,11 +1213,12 @@ key updates in a short time frame succession and significant packet reordering.
~~~
{: #ex-key-update title="Key Update"}

A packet that triggers a key update could arrive after successfully processing a
packet with a higher packet number. This is only possible if there is a key
compromise and an attack, or if the peer is incorrectly reverting to use of old
keys. Because the latter cannot be differentiated from an attack, an endpoint
MUST immediately terminate the connection if it detects this condition.
A packet that triggers a key update could arrive after the receiving endpoint
successfully processed a packet with a higher packet number. This is only
possible if there is a key compromise and an attack, or if the peer is
incorrectly reverting to use of old keys. Because the latter cannot be
differentiated from an attack, an endpoint MUST immediately terminate the
connection if it detects this condition.

In deciding when to update keys, endpoints MUST NOT exceed the limits for use of
specific keys, as described in Section 5.5 of {{!TLS13}}.
Expand Down