Re: [quicwg/base-drafts] Migration with zero-length CID is inadvisable (#3563)

ianswett <notifications@github.com> Tue, 31 March 2020 23:49 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 01C413A0D84 for <quic-issues@ietfa.amsl.com>; Tue, 31 Mar 2020 16:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.082
X-Spam-Level:
X-Spam-Status: No, score=0.082 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.282, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 P0BY6P4UbHEU for <quic-issues@ietfa.amsl.com>; Tue, 31 Mar 2020 16:48:58 -0700 (PDT)
Received: from out-27.smtp.github.com (out-27.smtp.github.com [192.30.252.210]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 763F93A0C35 for <quic-issues@ietf.org>; Tue, 31 Mar 2020 16:48:58 -0700 (PDT)
Received: from github-lowworker-6b40fdd.va3-iad.github.net (github-lowworker-6b40fdd.va3-iad.github.net [10.48.16.64]) by smtp.github.com (Postfix) with ESMTP id 9C714E045E for <quic-issues@ietf.org>; Tue, 31 Mar 2020 16:48:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1585698537; bh=4VV80iUCrNB2ZeQ9YD5kK5FBicDMym/0GtCsUz+W6tM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=AYxdgCkQltV0dq6ZeuIu9XSXJ+b9kmCZHZ4dMk7Hzi8k0Hg696Gttuvr0pG2LXCyR LV+GQI7G5O9e4IlMbN2HN6UH1kGIsDySOAtLfenap5YkE12ZAi+bfI9KR2OT7lLnGj jb/MjTCNWGiXQ4xKvf6oh9A6ons1yjHaPlWvoayg=
Date: Tue, 31 Mar 2020 16:48:57 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5BOGFGHZQQICRTCZ54R636TEVBNHHCGQM7OQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3563/review/385179447@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3563@github.com>
References: <quicwg/base-drafts/pull/3563@github.com>
Subject: Re: [quicwg/base-drafts] Migration with zero-length CID is inadvisable (#3563)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e83d6e98cbb0_53f83fed538cd96481280"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/PJDBV1qXu2TuHLO8Y5Ss-WlTdaQ>
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: Tue, 31 Mar 2020 23:49:01 -0000

@ianswett commented on this pull request.



> @@ -2246,6 +2246,13 @@ 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
 correlate activity.
 
+An endpoint SHOULD NOT initiate migration when a peer that requests the use of
+a zero-length connection ID. If the peer routes incoming packets using the
+source address, migration might not be successful. If the peer routes incoming
+packets by assigning a unique destination address to the connection, which
+might be achieved using using the preferred_address transport parameter (see
+{{preferred-address}}), packets sent on different paths will be linkable.

```suggestion
{{preferred-address}}), packets sent on different paths are likely to be linkable.
```

-- 
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/3563#pullrequestreview-385179447