Re: [quicwg/base-drafts] Multiple connections on the same port (#714)

[Mike Bishop <[e-mail]>]

Basically, the reasoning in the meeting was this:  If you want multiple handshakes sharing the same 5-tuple in parallel, then you have to be able to identify which handshake a given packet belongs to.  That means the first packet from the server that gives you the server-chosen ID _also_ has to have the client-chosen ID so it can be correlated.  The client can start using the server-chosen ID after that, as currently defined.

If the server's choice of connection ID has to be carried in its first packet and that packet has to have the client-chosen connection ID, then it makes sense to just carry the new connection ID in the transport parameters, which are in that packet anyway for the normal case.  (Of course, we also need a way to carry it in a HelloRetryRequest, but that's #713.)

-- 
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/714#issuecomment-321317131