Yes - that’s the length prefixing I was talking about. I should prevent any disambiguities. But even without that peers should be able to distinguish between t

Yes - that’s the length prefixing I was talking about. I should prevent any disambiguities. But even without that peers should be able to distinguish between truncated and full messages: HTTP2 allows to finish streams either cleanly or reset them. I’m case of a clean close (FIN) no truncation should be expected. I’m case of a HTTP/2 Reset or a tcp connection breakdown the stream must be treated as potentially truncated.