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

[martinduke <[e-mail]>]

So as I see it there are two extremes in the approach to this problem:

1) Minimum field consistency across versions. There must be exactly one
flags byte, in which the VERSION bit's meaning and location cannot change.
All other bits could, in theory, change. This byte must be followed by a
64-bit connection ID and the 32-bit version.

If there are additional flag bytes, or additional bytes for the connection
ID, they must appear after the version bytes.

2) More intuitively organized header fields. The VERSION and MORE_FLAGS
bits must have their meaning and position unchanged, and all flags bytes
are consecutive.

If we want to preserve the ability to one day have conn ids > 64 bits, I
believe it is necessary (in this approach) to move the version field ahead
of the connection ID.

****

Both of these approaches have their advantages, and it's possible to mix
and match. But I believe these are the limits.

On Sat, Dec 17, 2016 at 9:32 AM, Lars Eggert <[e-mail]>
wrote:

> Do you guys have that email reply stuff working for httpwg?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/55#issuecomment-267775403>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AXRMEYirpi9EXb7npboTXWtErJjdF0KZks5rJByUgaJpZM4LCAfq>
> .
>


-- 
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/55#issuecomment-268642523