[quicwg/base-drafts] Duplicate NEW_TOKEN should only be on same connection (#3179)

MikkelFJ <notifications@github.com> Thu, 31 October 2019 07:53 UTC

Date: Thu, 31 Oct 2019 00:52:59 -0700
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3IOYVF3CSFBSC25NV3Y7CVXEVBNHHB5NOWSE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3179@github.com>
Subject: [quicwg/base-drafts] Duplicate NEW_TOKEN should only be on same connection (#3179)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dba92db4e4cf_68e3ffcfc8cd96070952b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/gaM6VmgtpgEHcdwJ7ywi4JmqM04>

> An endpoint might receive multiple NEW_TOKEN frames that contain the same token value. Endpoints are responsible for discarding duplicate values, which might be used to link connection attempts; see Section 8.1.2.

This text does not forbid the server from sending the same token on multiple connections. Consequently the client has a hard, or impossible, task of excluding duplicates. At least if you only read that section.

Later the text says:

>The token MUST NOT include information that would allow it to be linked by an on-path observer to the connection on which it was issued.

This suggests that the token MUST indeed be unique, but in a roundabout manner.

It would be helpful to make the initial paragraph clearer by stating the that the duplicate token can only happen on the same connection and that the server MUST ensure different connections use different tokens.

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

[quicwg/base-drafts] Duplicate NEW_TOKEN should o… MikkelFJ
Re: [quicwg/base-drafts] Duplicate NEW_TOKEN shou… Jana Iyengar