[quicwg/base-drafts] Invert the connection ID logic during the handshake (#442)

[Martin Thomson <[e-mail]>]

The current design for server-chosen connection IDs doesn't allow the server to choose a connection ID on version negotiation and stateless reject.  Also, it doesn't allow a load balancer to distinguish between a server-chosen connection ID and one that the client chose.

The proposed resolution would be to have the following cleartext packet types:

1. initial client packet - in which connection ID is randomized by the client
2. server packet - in which the server picks a connection ID
3. version negotiation - in which the server picks a connection ID
4. client packet with server-chosen connection ID

Essentially, the only packet that contains a client-chosen connection ID is the first one from the client.

This only requires a change from "final server" to "initial client" packet type and a tweak to the semantics of the others.

Raised in conversation with @siyengar, @igorlord, and some others.

-- 
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/442