Re: [quicwg/base-drafts] Renumber packet types and invert Connection ID Flag (#956)

[ianswett <[e-mail]>]

Our server always requires connection id to be present on packets it receives, so the ambiguity you mention in your original post is not a problem.

With the previous numbering scheme, on the server side, we can just look at the first two bits.  If either is 1, then it's IETF QUIC, and if both are 0, it's GQUIC.

In the new scheme, I can still check the first bit for the long header, and then I can check the nonce bit, and if it's that's 1, it must be IETF QUIC because the client never sends a diversification nonce.  

But I believe the nonce bit is the bit that would end up being the spin bit, which could start making things pretty tricky.  It's probably worth thinking through what happens if two bits are reserved for measurement.

-- 
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/pull/956#issuecomment-347883901