Re: [quicwg/base-drafts] Allow endpoints to generate traffic keys asynchronously (#3874)

[Kazuho Oku <[e-mail]>]

@kazuho commented on this pull request.



> @@ -501,9 +501,11 @@ handshake, new data is requested from TLS after providing received data.
 As keys for new encryption levels become available, TLS provides QUIC with those
 keys.  Separately, as keys at a given encryption level become available to TLS,
 TLS indicates to QUIC that reading or writing keys at that encryption level are
-available.  These events are not asynchronous; they always occur immediately
-after TLS is provided with new handshake bytes, or after TLS produces handshake
-bytes.
+available.  While waiting for TLS to provide these keys, an endpoint SHOULD
+buffer the received packets marked as protected by the keys yet to be provided,
+and process them once those keys become available.  If the keys are generated
+asynchronously, an endpoint MAY continue responding to the received packets that
+are processable while waiting for TLS to provide these keys.

Thanks, I agree that that's better. Applied in 16038c1.

-- 
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/3874#discussion_r451945094