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

Don't Change Source CID After Retry #1491

Merged
merged 3 commits into from Jun 27, 2018
Merged

Don't Change Source CID After Retry #1491

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
93b705e
Don't Change Source CID After Retry
nibanks Jun 27, 2018
6d48169
should -> must
nibanks Jun 27, 2018
6a68e07
Removing extra text
martinthomson Jun 27, 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
5 changes: 2 additions & 3 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -634,10 +634,9 @@ packet in response, then it sets the Destination Connection ID to the value from
the Source Connection ID in the Retry packet. Changing Destination Connection ID
also results in a change to the keys used to protect the Initial packet. It also
sets the Token field to the token provided in the Retry. Additionally, the
client SHOULD NOT change the Source Connection ID because the server may include
client MUST NOT change the Source Connection ID because the server may include
the connection ID as part of its token validation logic. If the client changes
the Source Connection ID in this case, it would likely trigger a new Retry to be
sent.
the Source Connection ID in this case it could trigger a new Retry to be sent.

When a server receives an Initial packet with an address validation token, it
SHOULD attempt to validate it. If the token is invalid then the server SHOULD
Expand Down