Re: [quicwg/base-drafts] Prevent linkability from responding to migration (#2969)

Kazuho Oku <notifications@github.com> Thu, 15 August 2019 04:38 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 4D7AF120122 for <quic-issues@ietfa.amsl.com>; Wed, 14 Aug 2019 21:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 iVW-AcpUAK03 for <quic-issues@ietfa.amsl.com>; Wed, 14 Aug 2019 21:38:46 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6822C120041 for <quic-issues@ietf.org>; Wed, 14 Aug 2019 21:38:46 -0700 (PDT)
Date: Wed, 14 Aug 2019 21:38:45 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1565843925; bh=mnPJ23T7qppXiT/Y5LSedA0ugvX5biSRUN0zHgXPtsk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gyad07XWdTUBmcDnegbzAH12kvxurCVHlGdRJiz4oGX7C+d7GaXJqm/ITG97ukk79 vkdytE84fNxP90ygYnezrHVUtN7Upu0BilDdqRg9vL7YdWOYfh5xAR3WXX20FgsPqm 6ZO+429VP0TA7/YYYwrziAFOe5xbMqklyxUjrDQ4=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYOMBBGSUXO6YTGXB53MIKFLEVBNHHBZKYFBA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2969/review/275257914@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2969@github.com>
References: <quicwg/base-drafts/pull/2969@github.com>
Subject: Re: [quicwg/base-drafts] Prevent linkability from responding to migration (#2969)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d54e1d5889af_2e733fae77acd964638349"; 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/lj5tLXxgPGWDM1F95LuUH4s9ldQ>
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: Thu, 15 Aug 2019 04:38:48 -0000

kazuho commented on this pull request.



> @@ -2057,11 +2057,17 @@ linked by any other entity.
 At any time, endpoints MAY change the Destination Connection ID they send to a
 value that has not been used on another path.
 
-An endpoint MUST use a new connection ID if it initiates connection migration.
-Using a new connection ID eliminates the use of the connection ID for linking
-activity from the same connection on different networks.  Header protection
-ensures that packet numbers cannot be used to correlate activity.  This does not
-prevent other properties of packets, such as timing and size, from being used to
+An endpoint MUST use a new connection ID if it initiates connection migration as
+described in {{initiating-migration}}.  An endpoint MUST use a new
+connection ID in response to a connection migration if the packet that initiates
+migration uses a different connection ID to packets received on any previous
+path.

I wonder if using the term "initiate a connection migration" is correct, as to me it seems to imply what [section 9.2](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#rfc.section.9.2) talks, but not [path probing (section 9.1)](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#rfc.section.9.1)

Shouldn't we better state that, an endpoint MUST use a new connection ID when responding to a packet on a new path, using a new connection ID?

-- 
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/2969#pullrequestreview-275257914