Re: [quicwg/base-drafts] What can change in a different version (#55)

[ianswett <[e-mail]>]

Yes, clearly the version bit must not change.  And I think it's fine to always have the client use a 64 bit connection id until negotiated, but I think there were a few folks interested in suggesting 128 bit connection ids for future connections.  If that becomes a requirement, then putting the version before the connection id may be the way to go?

The benefit of the current approach where the connection ID directly follows the flags is it's easy for load balancers to deal with.  That being said, if they're going to have to deal with an extended flags bit, the extra complexity of dealing with a connection id that comes after the version may not matter.

And I do think the MORE_FLAGS bit should be defined.  The alternative would be to not use more than one flag byte until after version negotiation is complete, but that may be sub-optimal.



-- 
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/55#issuecomment-267054655