Ben Kaduk's Transport Comment 32

[LPardue]

@kaduk said:

Section 17.2.5.2

Token field to the token provided in the Retry. The client MUST NOT
change the Source Connection ID because the server could include the
connection ID as part of its token validation logic; see
Section 8.1.4.

It looks like Section 8.1.4 doesn't actually talk specifically about
connection IDs being bound to the token, just "additional information
about clients". Perhaps it should?

[martinthomson]

It isn't necessary that the value be stable for any property we rely on, but keeping it stable allows some implementation shortcuts for servers (and avoids problems that might arise from the Initial growing by more than the server expects, for instance).

[MikeBishop]

For concreteness, the proposal is no action. The client MUST NOT change, because it doesn't know whether the server might have bound it into the token state; the server is not under any obligation to do so. Both are correct.