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.

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

Change CID after inactivity #1214

Merged
merged 2 commits into from Apr 3, 2018
Merged
Changes from all commits
Commits
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
6 changes: 6 additions & 0 deletions draft-ietf-quic-transport.md
Expand Up @@ -1762,6 +1762,12 @@ recovers the packet number by adding the cumulative packet number gap to its
expected packet number. An endpoint MUST discard packets that contain a smaller
gap than it advertised.

Clients MAY change connection ID at any time based on implementation-specific
concerns. For example, after a period of network inactivity NAT rebinding might
occur when the client begins sending data again. A client might wish to reduce
linkability by employing a new connection ID when sending traffic after a period
of inactivity.

An endpoint that receives a successfully authenticated packet with a previously
unused connection ID MUST use the next available connection ID for any packets
it sends to that address. To avoid changing connection IDs multiple times when
Expand Down