Re: [quicwg/base-drafts] Don't Change Source CID After Retry (#1491)

[Kazuho Oku <[e-mail]>]

@MikeBishop 
> I thought there was text to the effect that changing the SCID during the handshake was effectively starting a fresh connection attempt, but I don't see it in the draft. 

FWIW, my understanding is that the existing text is (emphasis mine):
> During the handshake, an endpoint might receive multiple packets with the long header, and thus be given multiple opportunities to update the Destination Connection ID it sends. 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.
> [4.7 Connection ID Encoding](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#connection-id-encoding)

Anyways I agree that this is written from server's viewpoint, and I agree that we should have a "MUST NOT" for the client.

-- 
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/1491#issuecomment-400842078