quicwg/ops-drafts

Are client-requested Connection IDs atypical?

Closed this issue · 2 comments

Client and server negotiate connection IDs during the handshake; typically, however, only the server will request a connection ID for the lifetime of the connection.

From a discussion on this assertion with @nibanks, he observed that while client-side CIDs are uncommon on "actual" clients, they're likely to be very common on proxies (e.g. Masque). Anyone monitoring traffic at the server network might well see lots of client-side CIDs.

That suggests this statement about what "typically" happens might be overly specific to one deployment or viewpoint.

Agreed. I think the strongest statement I could agree with are that they're more likely to be present in the client to server direction than server to client, but I'm not sure that's very useful in practice?

How about:

Client and server each choose a connection ID during the handshake; for example, a server might request that a client use a connection ID, whereas the client might choose a zero-length value.