allow endpoints to generate traffic keys asynchronously, write down t…

…he expectations in relation

draft-ietf-quic-tls.md

@@ -499,9 +499,13 @@ handshake, new data is requested from TLS after providing received data.
 ### Encryption Level Changes
 
 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.
+QUIC that reading or writing keys at that encryption level are available.  While
+generating these keys, an endpoint SHOULD buffer received packets marked as
+protected by the keys being generated, and process them once those keys become
+available.  If the keys are generated asynchronously, an endpoint MAY continue
+responding to the received packets that were processable while waiting for TLS
+to provide these keys.  >>>>>>> allow endpoints to generate traffic keys
+asynchronously, write down the expectations in relation
 
 TLS provides QUIC with three items as a new encryption level becomes available: