Skip to content

Commit

Permalink
Remove extraneous "also".
Browse files Browse the repository at this point in the history
  • Loading branch information
huitema committed Sep 10, 2018
1 parent 6c018a6 commit 5dacf5f
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions draft-ietf-quic-transport.md
Expand Up @@ -2367,14 +2367,15 @@ congestion state (see {{migration-cc}}), so the port SHOULD only be changed
infrequently.

Endpoints that use connection IDs with length greater than zero
could also have their activity correlated if their peers keep using
could have their activity correlated if their peers keep using
the same destination connection ID after migration. If a node receives
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,
Nodes that initiate a migration and use connection IDs with length greater than zero
Nodes that initiate migration and
use connection IDs with length greater than zero
SHOULD provide their peers with new connection IDs before migration.

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

0 comments on commit 5dacf5f

Please sign in to comment.