Re: [quicwg/base-drafts] If you want a Stateless Reset you need to send a much larger packet than before (#2770)

[David Schinazi <[e-mail]>]

>From an offline conversation with @RyanAtGoogle , when client connection IDs are in use, Stateless Resets are inherently distinguishable from regular traffic because they do not carry the previously-used client connection ID. One might say that they could be confused for a change in connection ID, which is true. But let's assume we just changed from an 18 byte client connection ID to a 4-byte connection ID (which is specifically allowed by the spec), then that new packet is indistinguishable from a stateless reset.

So I propose that instead of having a minimum required size for stateless resets of 21 and a recommended minimum of 39, we can just say the minimum required size is 25. The important value here is the minimum non-zero connection ID length, not the maximum connection ID length.

This also means that the conversation about changing the maximum connection ID length is now orthogonal to stateless resets.

-- 
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/issues/2770#issuecomment-502763574