Re: [quicwg/base-drafts] Prevent linkability from responding to migration (#2969)

[Eric Kinnear <[e-mail]>]

erickinnear approved this pull request.

Thanks for writing this up! Content looks great, just two minor wording questions and this looks ready to go.

> @@ -2077,9 +2084,13 @@ genuine migrations.  Changing port number can cause a peer to reset its
 congestion state (see {{migration-cc}}), so the port SHOULD only be changed
 infrequently.
 
-An endpoint that exhausts available connection IDs cannot migrate.  To ensure
-that migration is possible and packets sent on different paths cannot be
-correlated, endpoints SHOULD provide new connection IDs before peers migrate.
+An endpoint that exhausts available connection IDs cannot migrate.  Similarly,
+an endpoint is unable to respond to probes or an attempt by its peer to migrate

This sentence parses oddly for me, I assume it's in the context of the previous sentence, but maybe something like
```
An endpoint that exhausts available connection IDs cannot probe new paths or initiate 
migration, nor can it respond to probes or attempts by its peer to migrate.
```
and replace both sentences.
(Not providing that as a suggested change since it'll mess up the wrapping, sorry!)

> @@ -2077,9 +2084,13 @@ genuine migrations.  Changing port number can cause a peer to reset its
 congestion state (see {{migration-cc}}), so the port SHOULD only be changed
 infrequently.
 
-An endpoint that exhausts available connection IDs cannot migrate.  To ensure
-that migration is possible and packets sent on different paths cannot be
-correlated, endpoints SHOULD provide new connection IDs before peers migrate.
+An endpoint that exhausts available connection IDs cannot migrate.  Similarly,
+an endpoint is unable to respond to probes or an attempt by its peer to migrate
+or probe.  To ensure that migration is possible and packets sent on different
+paths cannot be correlated, endpoints SHOULD provide new connection IDs before
+peers migrate.  If a peer might have exhausted available connection IDs, a

Do we want to reference the other section that talks about SHOULD provide a new CID for every one that gets retired, etc.? I think that's `{{issue-cid}}`.

Specifically the below paragraph: 
```
An endpoint SHOULD supply a new connection ID when it receives a packet with a
previously unused connection ID or when the peer retires one, unless providing
the new connection ID would exceed the peer's limit.  An endpoint MAY limit the
frequency or the total number of connection IDs issued for each connection to
avoid the risk of running out of connection IDs; see {{reset-token}}.
```

```suggestion
peers migrate ({{issue-cid}}).  If a peer might have exhausted available connection IDs, a
```

If that doesn't mess up the spacing.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2969#pullrequestreview-276821582