Re: [quicwg/base-drafts] HTTP SETTINGS: define setting content encoding (#1556)

[afrind <[e-mail]>]

> 4.2.6.1.  Integer encoding
>
>   Settings which are integers use the QUIC variable-length integer encoding.

So I don't think there's anything ambiguous in the current draft.  It is strange however that there is both a variable-length integer specifying the length of the integer setting AND the setting itself is a variable-length integer, so its length is self-describing and redundant.  

We could instead define settings that are integers use all of the `Contents` octets to specify the integer and take the length exclusively from the `Length` field of the parameter.  This would save a byte on the wire here and there (eg a parameter with value 100 currently requires 3 bytes to encode), and possibly make things a little less confusing, at the cost of having yet another way to encode integers.

-- 
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/1556#issuecomment-405377723