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

Bundle new client connection ID and path challenge in migration probes #1730

Merged
merged 10 commits into from Sep 12, 2018
Merged

Bundle new client connection ID and path challenge in migration probes #1730

Changes from 1 commit
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
b0396b0
Merge pull request #5 from quicwg/master
huitema Sep 9, 2018
bc74468
Specifying use of new connection ID to avoid correlation
huitema Sep 9, 2018
efeb5fc
Attempt to incorporate Martin's suggestions
huitema Sep 10, 2018
34f056e
ensures
martinthomson Sep 10, 2018
a1ecc65
Adding more specific requirements per Ian's review
huitema Sep 10, 2018
cac497f
Merge branch 'probe-cid' of https://github.com/huitema/base-drafts in…
huitema Sep 10, 2018
6c018a6
Remove trailing white space.
huitema Sep 10, 2018
5dacf5f
Remove extraneous "also".
huitema Sep 10, 2018
86ecbec
Tweak probing text
martinthomson Sep 12, 2018
17ccc69
reword, note the possibility of infinite regress
martinthomson Sep 12, 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 @@ -2373,9 +2373,9 @@ packets through a newly used connection ID, it SHOULD select an
available new connection ID provided by the peer and use it as
destination address for its responses. The goal is
to ensure absence of correlation between the pairs of client and server
connection ID used on different paths. To fulfill this privacy requirement,
connection ID used on different paths. To fulfill this privacy requirement,
Nodes that initiate a migration and use connection IDs with length greater than zero
SHOULD provide their peers with new connection IDs before migration.
SHOULD provide their peers with new connection IDs before migration.

## Server's Preferred Address {#preferred-address}

Expand Down