Re: [quicwg/base-drafts] Clarify that unlinkability is required for NEW_TOKEN tokens. Changes … (#2647)

Kazuho Oku <notifications@github.com> Wed, 22 May 2019 08:56 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 155E71201B5 for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 01:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WrPa5RTHLKLY for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 01:55:58 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F10E31201D1 for <quic-issues@ietf.org>; Wed, 22 May 2019 01:55:56 -0700 (PDT)
Date: Wed, 22 May 2019 01:55:55 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558515356; bh=5cRAbc7o5QpIascXkcj24S1qVDObBZ46iLdnzQWwqB0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SAaL8rkuVFwlj7Dob7/zjwJknCOwd1F3LPi3kirbnclfh7na4qlz/Ns/IS+KHeBma siE8Huwk9Yvk6m455+jHs6CJwK2mrHmWe27wwSZQK+r2FO435EqWdViMLGaZyz3ykA T+13NsdMyC48BHKmYObJHWHlxfeWHoXKF4BT96ko=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZNGJMCZGJHNEJD6QN26JARXEVBNHHBUBA3UE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2647/review/240493929@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2647@github.com>
References: <quicwg/base-drafts/pull/2647@github.com>
Subject: Re: [quicwg/base-drafts] Clarify that unlinkability is required for NEW_TOKEN tokens. Changes … (#2647)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce50e9bd777a_47b63fdb32ecd9649023b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/p7rnxZN2kw6ldxnxdHMYLcw-5Oc>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2019 08:56:06 -0000

kazuho commented on this pull request.



>  A token SHOULD be constructed for the server to easily distinguish it from
 tokens that are sent in Retry packets as they are carried in the same field.
+The token SHOULD NOT expose linkability; i.e., information that lets observers
+correlate the connection that is using the token and the one that issued the
+token.
+
+Unlike the token that is created for a Retry packet, there might be some time
+between when the token is created and when the token is subsequently used.
+Thus, a token SHOULD have an expiration time, which could be either an explicit
+expiration time or an issued timestamp that can be used to dynamically calculate
+the expiration time.  A server can retain the expiration time in the server-side

Applied in 1a0be70.

-- 
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/pull/2647#discussion_r286381671