Re: [quicwg/base-drafts] Early CONNECTION_CLOSE fixes (#3440)

[ianswett <[e-mail]>]

ianswett commented on this pull request.



> @@ -415,12 +416,20 @@ A QUIC client starts TLS by requesting TLS handshake bytes from TLS.  The client
 acquires handshake bytes before sending its first packet.  A QUIC server starts
 the process by providing TLS with the client's handshake bytes.
 
-At any time, the TLS stack at an endpoint will have a current sending encryption
-level and receiving encryption level. Each encryption level is associated with a
-different flow of bytes, which is reliably transmitted to the peer in CRYPTO
-frames. When TLS provides handshake bytes 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.
+At any time, the TLS stack at an endpoint will have a current sending
+encryption level and receiving encryption level. Encryption levels determine
+the packet type and keys that are used for protecting data.
+
+Each encryption level is associated with a different flow of bytes, which is

Flow is a non-obvious word choice, maybe sequence of bytes?

```suggestion
Each encryption level is associated with a different sequence of bytes, which is
```

-- 
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/3440#pullrequestreview-372485718