[quicwg/base-drafts] Stateless Reset from clients, bis (#1505)

[Igor Lubashev <[e-mail]>]

In #466, we left it as the client cannot use Stateless Reset, until the server starts to use to a CID provided by the client's NEW_CONNECTION_ID.  (Something that is actually not stated explicitly in the draft.)

This is certainly not great, hence this issue.

To fix this, I can think of a few alternatives:
1. A new frame that provides the initial Stateless Reset Token from the client. It only applies to the initial CID (important to note, since you do not want it to override the token from a subsequent NEW_CONNECTION_ID in case of reordering).
2. If NEW_CONNECTION_ID frame is received from the client with Seq=0 and Length=0, it provides the initial Stateless Reset Token (and is considered to be Seq=-1, so the next NEW_CONNECTION_ID would actually be Seq=0).  I do not love this and would prefer just a new frame.

-- 
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/1505