Subject: [quicwg/base-drafts] Stateless Reset Lacks Normative Text (#2471)

From: martinduke <[email-masked]>
Date: Fri, 15 Feb 2019 09:15:09 -0800

While there are some prohibitions, and an explicit MAY for responding to Long Headers, there is no normative statement for the usual use case for Stateless Reset.

I believe it's a SHOULD, but maybe someone thinks it's a MUST.

Relatedly, in 10.4.1, MUST we attempt to detect Stateless Reset, or MAY endpoints just drop after decrypt failure?

At the end of 10.4.2, MUST we not reuse connection IDs if there's a static key? (I think the answer is yes)

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