Re: [quicwg/base-drafts] More words on the minimum packet size requirement (#3986)

[Jana Iyengar <[e-mail]>]

@janaiyengar commented on this pull request.



> +endpoint might request that a peer include in the Destination Connection ID
+field.  This ensures that any stateless reset sent by the peer is
+indistinguishable from a valid packet sent to the endpoint.  An endpoint that
+sends a stateless reset in response to a packet that is 43 bytes or less in
+length SHOULD send a stateless reset that is one byte shorter than the packet it
+responds to.

This is difficult to parse. Suggested rephrase of the paragraph.

```
The resulting minimum size of 21 bytes does not guarantee that a stateless reset is
difficult to distinguish from other packets if the recipient requires the use of
a connection ID. To achieve that end, the endpoint SHOULD pad all packets it sends 
to at least 22 bytes longer than the minimum connection ID that the
endpoint might request a peer to include in packets that the peer sends. 
This ensures that any stateless reset sent by the peer is
indistinguishable from a valid packet sent to the endpoint.  An endpoint that
sends a stateless reset in response to a packet that is 43 bytes or shorter
SHOULD send a stateless reset that is one byte shorter than the packet it
responds to.
```

-- 
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/3986#pullrequestreview-462906971