Re: [quicwg/base-drafts] Clarify section on negotiating connection IDs (#3349)

[Nick Banks <[e-mail]>]

nibanks commented on this pull request.



> -Initial packet from the server. Once a client has received an Initial packet
-from the server, it MUST discard any packet it receives with a different Source
-Connection ID.
-
-A client MUST only change the value it sends in the Destination Connection ID in
-response to the first packet of each type it receives from the server (Retry or
-Initial); a server MUST set its value based on the Initial packet.  Any
-additional changes are not permitted; if subsequent packets of those types
-include a different Source Connection ID, they MUST be discarded.  This avoids
-problems that might arise from stateless processing of multiple Initial packets
-producing different connection IDs.
-
-The connection ID can change over the lifetime of a connection, especially in
-response to connection migration ({{migration}}); see {{issue-cid}} for details.
+the SCID supplied by the server as the DCID for subsequent packets, including
+all subsequent Handshake and 0-RTT packets. This means that a client might

Why require that all subsequent Handshake packets use the same CID? It's definitely requires for Initial and 0-RTT to have consistent routing through the LB, but I haven't heard any reason to require it for handshake (taking into account possible new CIDs being received, i.e. #3348). IMO, adding extra restrictions here just complicates NEW_CONNECTION_ID handling.

-- 
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/3349#pullrequestreview-343453704