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

Permit 0-RTT after Retry and VN #1514

Merged
merged 9 commits into from Jul 31, 2018
Merged

Permit 0-RTT after Retry and VN #1514

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
fe48863
Permit 0-RTT after Retry and VN
martinthomson Jul 3, 2018
88fc560
0-RTT, 1-RTT, same thing
martinthomson Jul 3, 2018
620c583
Clarify key changes
martinthomson Jul 3, 2018
b6c48be
Redo fixes I already committed somewhere else, I swear
martinthomson Jul 4, 2018
e2b9137
Refinements
martinthomson Jul 6, 2018
1011f5e
Have been
martinthomson Jul 8, 2018
2e13f0d
Add text to the TLS spec too
martinthomson Jul 9, 2018
25598fd
Extra 'on'
martinthomson Jul 9, 2018
22deb75
Remove especially if text
martinthomson Jul 9, 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
2 changes: 1 addition & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -744,7 +744,7 @@ where it is used. Clients that want to break continuity of identity with a
server MAY discard tokens provided using the NEW_TOKEN frame. Tokens obtained
in Retry packets MUST NOT be discarded.

A client SHOULD NOT reuse a token. Reusing a token on allows connections to be
A client SHOULD NOT reuse a token. Reusing a token allows connections to be
linked by entities on the network path (see {{migration-linkability}}). A
client MUST NOT reuse a token if it believes that its point of network
attachment has changed since the token was last used; that is, if there is a
Expand Down