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

Connection migration spec is hard to understand #1364

Closed
huitema opened this issue May 21, 2018 · 0 comments
Closed

Connection migration spec is hard to understand #1364

huitema opened this issue May 21, 2018 · 0 comments
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@huitema
Copy link
Contributor

huitema commented May 21, 2018

In section 6.8.5. Privacy Implications of Connection Migration, the base transport spec says:

An endpoint that to break linkability upon changing networks MUST use a previously unused connection ID provided by its peer. Protection of packet numbers ensures that packet numbers cannot be used to correlate connections. Other properties of packets, such as timing and size, might be used to correlate activity, but no explicit correlation can be used to link activity across paths.

"That to break" is a bit awkward. Something must have been left out in the editing process...

martinthomson added a commit that referenced this issue May 22, 2018
@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels May 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

No branches or pull requests

2 participants