On 7 October 2016 at 19:34, Ilari Liusvaara <ilariliusva...@welho.com> 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. _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
