Re: [quicwg/base-drafts] Make HTTP frames a TLV format. This has several advantages: (#2235)

[Kazuho Oku <[e-mail]>]

I'm fine with moving frame type in front of the length.

OTOH, I am not sure if I prefer using varints for frame types.

IIRC, using varints for frame types of the transport, with the requirement that the minimal-sized encoding MUST be used, was based on the fact that it reserves more code points to future extensions, at the same time not making existing implementations complex. The reason the change did not make existing implementations complex was because new frame types cannot be used without negotiation.

The situation is different in H3.

H3 allows frames to be used without negotiation. In fact, we allow endpoints to grease the codepoints.

That means that every implementation would be required to support frame types using varints, even though in practice only the single-octet versions would be used.

To me that sounds like an unnecessary complexity.

I am also skeptical if we would ever run out of H3 frame types even if they are kept 8 bits, considering how few we have used in H2.

-- 
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/2235#issuecomment-449610469