Re: [quicwg/base-drafts] Minor nits (#1800)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> @@ -387,6 +392,10 @@ peer in CRYPTO frames. When TLS provides handshake octets to be sent, they are
 appended to the current flow and any packet that includes the CRYPTO frame is
 protected using keys from the corresponding encryption level.
 
+Unlike its operations with TCP, the TLS bytestream is never separately
+encrypted and decrypted. This operation only occurs on the QUIC packet as a
+whole.

I know what you are saying, but it's equally confusing because it's not clear what the TLS bytestream is.  For QUIC, it's the sequence of TLS handshake messages, but TLS has other concepts that could be considered to be a bytestream: the sequence of TLS records (unencrypted), or the sequence of protected TLS records could very much be considered to be a bytestream.

Maybe the right thing to say here is that "QUIC takes the unprotected content of TLS handshake records as the content of CRYPTO frames.  Encapsulation of these messages in protected TLS records does not happen.  QUIC assembles CRYPTO frames into QUIC packets, which are protected using QUIC packet protection."

But isn't that written down elsewhere?

> @@ -320,14 +322,17 @@ Each encryption level has a specific list of frames which may appear in it. The
 rules here generalize those of TLS, in that frames associated with establishing
 the connection can usually appear at any encryption level, whereas those
 associated with transferring data can only appear in the 0-RTT and 1-RTT
-encryption levels
+encryption levels.

I think you want a colon:

> @@ -161,6 +161,9 @@ series of typed TLS records. Records are individually cryptographically
 protected and then transmitted over a reliable transport (typically TCP) which
 provides sequencing and guaranteed delivery.
 
+Note that Change Cipher Spec records, optional in TLS over TCP, have no
+encoding for TLS over QUIC.

I would say simply "Change Cipher Spec records cannot be sent in QUIC."

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/1800#pullrequestreview-159063733