Re: [quicwg/base-drafts] Coalescing different CIDs for same connection (#3800)

[Kazuho Oku <[e-mail]>]

@hardie 
> I think "high probability" is probably app-dependent, because there may be cases where there are significant numbers of parallel connections.  In the case of proxied queries, for example, the use of the same 4-tuple but a different CID could turn out to be common, because the proxy may prefer to keep traffic from its different clients separate even if they could be served by the same upstream server.

I might be missing something, but if an endpoint wants to cut linkability between the packets used during the handshake and the packets used in 1-RTT, that endpoint has to switch to a new CID *after* the peer has dropped its Initial and Handshake keys, regardless of the outcome of this issue. That is because if the endpoint switches to a new CID while the peer is still sending Initial or Handshake packets, we allow the peer to use that new CID in the long header packets sent in response.

Therefore, I do not think that requiring endpoints to use one DCID in all the coalesced QUIC packets help us in practice.

-- 
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/issues/3800#issuecomment-658462267