[hybi] frame length encoding

[Brian <[e-mail]>]

Then that one bit isn't reserved, it's defined as a bit that adds an
optional "flags" field that contains 7 undefined bits and another "add
another flags field" bit.

Seems simpler to just throw in the one-byte "reserved" field that can be
used for whatever down the line.  If we later need more fields in the
header, then one of those bits could be designated to indicate such at that
time.

I guess we need to decide how many reserved bits we care to keep in the
initial header and let that drive the solution we come up with.  I'm happy
to punt on the issue and keep plenty by adding an extra byte.

Brian



On Sun, Aug 22, 2010 at 2:53 AM, Shelby Moore <[e-mail]> wrote:

> >> As for the concern about keeping a sufficient number of reserved bits...
> >> throw in a whole reserved byte and put a bow on it. :-)
> >
> > That might not be a bad idea.  But I think we will know that more as we
> > move forward on designed the extensions?
> >
> > 1 byte is not that ridiculous, because we already have 3 bytes minimum
> > including a 1 byte payload.
>
> I forgot that I had already mentioned in this thread that we only need to
> keep 1 reserved bit free, so that we can always add another bit as needed,
> by allocating that 1 bit to signal there is an extra byte.  Repeat in next
> byte, and so on...
>
> So we don't need the extra byte now, unless we see an extension now that
> needs that many bits.
>
> Any one disagree?
>