Thanks Ilari. Ilari Liusvaara <ilariliusva...@welho.com> 于2019年6月28日周五 上午4:01写道： > 1) 0x16 byte is appended to plaintext to yield TLSInnerPlaintext > (since this is encrypted handshake message), together with 0 > trailing zeroes (for padding, there could be more).
1. Is it worth adding this explanation to RFC 8448? Neither "TLSInnerPlaintext" or "0x16" was mentioned in the context, making this "Informational" RFC not so informative. 2. Is there a specific reason to structure TLSInnerPlaintext this way? Does it make parsing counterintuitive that the parser must know ContentType before locating ContentType? -Yishuai _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
