On Sat, Jun 29, 2019 at 08:36:49AM -0400, Yishuai Li wrote:
> Thanks Ilari.
>
> Ilari Liusvaara 于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, the
Thanks Ilari.
Ilari Liusvaara 于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?
On Thu, Jun 27, 2019 at 05:40:19PM -0400, Yishuai Li wrote:
>
> RFC 8446 Section 4 Page 23 says:
>
> > Handshake messages are supplied to the TLS record layer, where they are
> > encapsulated within one or more TLSPlaintext or TLSCiphertext structures
> > which
> > are processed and transmitted
Dear TLS working group,
RFC 8446 Section 4 Page 23 says:
> Handshake messages are supplied to the TLS record layer, where they are
> encapsulated within one or more TLSPlaintext or TLSCiphertext structures which
> are processed and transmitted as specified by the current active connection
> state
