Re: Stream0 Proposal: CRYPTO_HS frame encoding (Re: Stream0 Design Team Proposal)

[Christian Huitema <[e-mail]>]

On 5/23/2018 5:41 PM, Martin Thomson wrote:

> On Thu, May 24, 2018 at 10:06 AM Kazuho Oku <[e-mail]> wrote:
>> 0x10 - 0x17: STREAM frame
>> 0x18: CRYPTO_HS frame
> ....
>> I think that is workable, although it makes me sad because we will
>> have more conditional branches.
> Yeah.  We have an extremely limited space here.  And while Jana is right
> that we haven't used much yet, we're only just starting.  As for
> conditionals.  Maybe.  One way to implement this is a switch statement, and
> those might not suffer as badly when you consider that you also have to
> dispatch to other frame handlers in the same piece of code.
>

I am with Martin on this one. Just one code point for crypto frames,
please. At best the optimization saves 2 bytes in the entire duration of
the connection -- one byte for the CH, one byte for the first frame of
the SH. And for the CH, you don't care because you are going to pas to
min length anyhow.

You can still do common code with the "stream" data even without that,
you just need two small branches of code to parse the stream id, stream
offset, and stream fin. Just default to "stream=Crypto, stream offset=
always present, stream fin= false" in the crypto branch.

-- Christian Huitema