Hi Martin, the problem is that with embedded implementations you need to be prepared to receive this amount of data when the specification says so.
On 10/07/2016 10:59 AM, Martin Thomson wrote: > On 7 October 2016 at 19:34, Ilari Liusvaara <[email protected]> wrote: >> If application supports any sort of multiplexing (e.g. HTTP/2), one >> presumably wants the context to be non-opaque and identify the stream >> that caused the request + some parameters about the request (to avoid >> duplicating those in application layer). > > > It's opaque to TLS. And 255 simply establishes the number of octets > in the length (1), if you don't need that much context (few will even > if they implement this), don't use the extra space. >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
