Re: [quicwg/base-drafts] The "quic " label is used for key update (#1899)

[janaiyengar <[e-mail]>]

janaiyengar commented on this pull request.



> -
-An endpoint doesn't need to send packets immediately when it detects that its
-peer has updated keys.  The next packet that it sends will simply use the new
-keys.  If an endpoint detects a second update before it has sent any packets
-with updated keys it indicates that its peer has updated keys twice without
-awaiting a reciprocal update.  An endpoint MUST treat consecutive key updates as
-a fatal error and abort the connection.
+the corresponding read key and IV.  This uses the same variation on HKDF as
+defined in {{protection-keys}}; that is, the prefix "quic " is used in place of
+"tls13 ".
+
+If the packet can be decrypted and authenticated using the updated key and IV,
+then the keys the endpoint uses for packet protection are also updated.  The
+next packet sent by the endpoint will then use the new keys.
+
+An endpoint doesn't always need to send packets when it detects that its peer

```suggestion
An endpoint does not always need to send packets when it detects that its peer
```

-- 
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/1899#pullrequestreview-167681460