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

Reword linkability on migration text #1369

Merged
merged 2 commits into from May 23, 2018
Merged

Reword linkability on migration text #1369

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bdd9392
Reword linkability on migration text
martinthomson May 22, 2018
99b73d9
Update draft-ietf-quic-transport.md
martinthomson May 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
6 changes: 3 additions & 3 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1809,9 +1809,9 @@ in the order in which they are numbered.
Upon changing networks an endpoint MUST use a previously unused connection ID
provided by its peer. This eliminates the use of the connection ID for linking
activity from the same connection on different networks. Protection of packet
numbers ensures that packet numbers cannot be used to correlate activity. Other
properties of packets, such as timing and size, might be used to correlate
activity, but these changes ensure that the packet header cannot be used.
numbers ensures that packet numbers cannot be used to correlate activity.
This does not prevent other properties of packets, such as timing and size,
from being used to correlate activity.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"but these changes" is a bit vague - how about "but using a path unique connection ID enures ..."

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, but I agree with @mikkelfj, "but these changes" is loose text and wont stand well after another change or three.

Clients MAY change connection ID at any time based on implementation-specific
concerns. For example, after a period of network inactivity NAT rebinding might
Expand Down