Re: [quicwg/base-drafts] Add normative language for stateless reset (#2574)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.

> If I receive a packet for which I have no context, MUST I send a Stateless Reset or SHOULD I, assuming I might have sent the token?

It isn't the place of this specification to tell endpoints when a stateless reset is appropriate.  Describing the consequences should suffice.

> Furthermore, SHOULD I do some sort of rate control to avoid sending 1 SR per packet?

I thought we had that already.  But I think that we intentionally removed it.  I'm still looking for the PR that did that (tracking removed code is hard).


> @@ -2428,17 +2428,17 @@ This design relies on the peer always sending a connection ID in its packets so
 that the endpoint can use the connection ID from a packet to reset the
 connection.  An endpoint that uses this design MUST either use the same
 connection ID length for all connections or encode the length of the connection
-ID such that it can be recovered without state.  In addition, it cannot
-provide a zero-length connection ID.
+ID such that it can be recovered without state.  In addition, it cannot provide

I didn't want to repeat a requirement from elsewhere in that migration cannot be initiated if the connection ID is zero length.

-- 
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/2574#pullrequestreview-222222739