Re: [quicwg/base-drafts] Unknown transport parameters cannot be ignored if no length is provided (#1661)

[Mike Bishop <[e-mail]>]

What you missed is that the TLS presentation language makes length prefixes implicit.  The generic definition for a TransportParameter is:

```
   struct {
      TransportParameterId parameter;
      opaque value<0..2^16-1>;
   } TransportParameter;
```

That means that `value` is a sequence of bytes with a two-byte length prefix.  Everything else defines the content of `value` for particular values of `parameter`.

Separately, while I agree that there's a dependency on the TLS *document* for the definition of the presentation language, there's actually no dependency on TLS *libraries* for generating this sequence of blobs.  It's a convenient notation for a binary structure, just as ABNF is a convenient notation for a text structure.  I'm with you that I wish it were a separate RFC rather than being a section in a TLS draft, but that's not the province of this WG.

-- 
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/1661#issuecomment-412941132