Re: [quicwg/base-drafts] Consider making h3 frame types varint (#2253)

[Kazuho Oku <[e-mail]>]

> I agree with @kazuho that exchanging H3 settings in transport parameters has appealing benefits, there is however the downside that client transport parameters are not encrypted, and this could therefore be used for fingerprinting.

I am not sure if we need to care about the downside, considering the fact that we are sending other parameters (including the transport-level transport parameters) in clear. If we do care, we should try protecting all of them.

> That said we may be somewhat off topic, as this issue is about 8-bit vs varint for h3 frame types. Without going into the details discussed in this thread, there seems to be interest in allowing uncoordinated extensions, and varints allow those at a very small implementation cost.

Yeah my point was that people interested in doing private experiments can always negotiate the use of the extensions for all the cases the WG decided to care about, and therefore that there is not a benefit in having varint frame types, especially assuming that sending private experimental extensions to the wild without coordination is likely to be just waste of bandwidth.

-- 
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/issues/2253#issuecomment-451373046