Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't bother reserving bits #58

Merged
merged 1 commit into from Oct 21, 2018
Merged

Don't bother reserving bits #58

merged 1 commit into from Oct 21, 2018

Conversation

@martinthomson
Copy link
Contributor

martinthomson commented Aug 31, 2018

This is a bikeshed colour, but I think a good one. In the 5 bits that
we have, we can pack two epoch bits (we only need one in practice, but
let's leave that aside for the moment), and a bit each to signal
presence of connection ID and length. That leaves one spare bit. I'm
suggesting that we spend this on signaling the difference between an
8-bit and 16-bit sequence number. 16 bits is far more comfortable than
14, and 8 is probably enough for many use cases (saving a byte).

That is, unless you were saving this for a spin bit and VEC.

This doesn't do anything about #56, but I think that we can save a bit
from the epoch. More on that later.

This is a bikeshed colour, but I think a good one.  In the 5 bits that
we have, we can pack two epoch bits (we only need one in practice, but
let's leave that aside for the moment), and a bit each to signal
presence of connection ID and length.  That leaves one spare bit.  I'm
suggesting that we spend this on signaling the difference between an
8-bit and 16-bit sequence number.  16 bits is far more comfortable than
14, and 8 is probably enough for many use cases (saving a byte).

That is, unless you were saving this for a spin bit and VEC.
@thomas-fossati
Copy link
Contributor

thomas-fossati commented Sep 6, 2018

If epoch can be one bit - the rationale you provided is quite convincing - then this proposal could coexist with #56.

@ekr ekr merged commit 411ab29 into tlswg:master Oct 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.