Re: [quicwg/base-drafts] Move requirements for packet number reset (#3811)

[Jana Iyengar <[e-mail]>]

@janaiyengar commented on this pull request.



> @@ -4549,13 +4549,9 @@ packets.
 
 After a client receives a Retry packet, 0-RTT packets are likely to have been
 lost or discarded by the server.  A client SHOULD attempt to resend data in
-0-RTT packets after it sends a new Initial packet.
-
-A client MUST NOT reset the packet number it uses for 0-RTT packets, since the
-keys used to protect 0-RTT packets will not change as a result of responding to
-a Retry packet.  Sending packets with the same packet number in that case is
-likely to compromise the packet protection for all 0-RTT packets because the
-same key and nonce could be used to protect different content.
+0-RTT packets after it sends a new Initial packet.  New packet numbers MUST be
+used for any new packets that are sent; as defined in {{retry-continue}},

```suggestion
used for any new packets that are sent; as described in {{retry-continue}},
```

> +processing a Retry packet. This applies to 0-RTT packets in particular as those
+contain confidential information that is most likely to need transmission.  The
+keys used to protect packets will not change as a result of responding to a
+Retry packet.  Sending packets with the same packet number is likely to
+compromise the packet protection for those packets because the same key and
+nonce could be used to protect different content.

```suggestion
processing a Retry packet. In particular, 0-RTT packets contain confidential
information that will most likely be retransmitted on receiving a Retry packet.
The keys used to protect these new 0-RTT packets will not change as a result of
responding to a Retry packet. However, the data sent in these packets could be
different than what was sent earlier. Sending these new packets with the same
packet number is likely to compromise the packet protection for those packets
because the same key and nonce could be used to protect different content.
```

-- 
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/3811#pullrequestreview-441311204