[quicwg/base-drafts] Only received Stateless reset token should be checked (#2669)

Tatsuhiro Tsujikawa <notifications@github.com> Tue, 07 May 2019 12:08 UTC

Date: Tue, 07 May 2019 05:08:15 -0700
From: Tatsuhiro Tsujikawa <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2RAONO3KYQEQVQVFN232T27EVBNHHBUTBAQY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2669@github.com>
Subject: [quicwg/base-drafts] Only received Stateless reset token should be checked (#2669)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd1752fc66d_17783fafb62cd968135951"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/I9pHckId5BRnOKE8X8dwwv7vOz4>

The current text does not explicitly say that endpoint has to check the stateless reset token received in NEW_CONNECTION_ID (and server's TP if endpoint is a client).

> The endpoint MUST
   then compare the last 16 bytes of the packet with all Stateless Reset
   Tokens that are associated with connection IDs that are currently in
   use.  This includes Stateless Reset Tokens from NEW_CONNECTION_ID
   frames and the server's transport parameters.

With this wording, I was under the impression that server can use stateless reset token in its own TP, but it seems not.

I think it would be nice to state that only received stateless reset tokens are checked.


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

[quicwg/base-drafts] Only received Stateless rese… Tatsuhiro Tsujikawa
Re: [quicwg/base-drafts] Only received Stateless … Tatsuhiro Tsujikawa
Re: [quicwg/base-drafts] Only received Stateless … Martin Thomson
Re: [quicwg/base-drafts] Only received Stateless … Martin Thomson