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

Include a token on all Initial packets #1794

Merged
merged 5 commits into from Oct 2, 2018
Merged

Include a token on all Initial packets #1794

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5084586
Only include a token in the "first" Initial
martinthomson Sep 25, 2018
2f216b2
Use the token always
martinthomson Sep 25, 2018
c921b42
Not clear which 'same' this meant.
martinthomson Sep 26, 2018
83356f6
Update draft-ietf-quic-transport.md
ianswett Oct 2, 2018
5c054d4
Update draft-ietf-quic-transport.md
ianswett Oct 2, 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-transport.md
View file
Open in desktop
Expand Up @@ -622,8 +622,8 @@ client MUST NOT change the Source Connection ID because the server could include
the connection ID as part of its token validation logic (see {{tokens}}).

All subsequent Initial packets from the client MUST use the connection ID and
token values from the Retry packet. All subsequent Initial packets from
the client MUST use the connection ID and token values from the Retry packet.
token values from the Retry packet. Aside from this, the Initial packet sent
by the client is subject to the same restrictions as the first Initial packet.
A client can either reuse the cryptographic handshake message or construct a
new one at its discretion.

Expand Down