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

The "quic " label is used for key update #1899

Merged
merged 7 commits into from Oct 23, 2018
Merged

The "quic " label is used for key update #1899

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
7ad0b15
The "quic " label is used for key update
martinthomson Oct 23, 2018
6489433
Use 'it' less
martinthomson Oct 23, 2018
e5eee0b
Use unexpected_message for KeyUpdate
martinthomson Oct 23, 2018
76b70fd
does not
janaiyengar Oct 23, 2018
24ac0f0
glom together
janaiyengar Oct 23, 2018
fa1d40c
does not
janaiyengar Oct 23, 2018
a5c5af3
comma
janaiyengar Oct 23, 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
4 changes: 2 additions & 2 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Expand Up @@ -994,8 +994,8 @@ defined in {{protection-keys}}; that is, the prefix "quic " is used in place of
"tls13 ".

If the packet can be decrypted and authenticated using the updated key and IV,
then the keys it uses for packet protection are also updated. The next packet
sent by the endpoint will then use the new keys.
then the keys the endpoint uses for packet protection are also updated. The
next packet sent by the endpoint will then use the new keys.

An endpoint doesn't always need to send packets when it detects that its peer
martinthomson marked this conversation as resolved.
Show resolved Hide resolved
has updated keys. The next packet that it sends will simply use the new keys.
Expand Down