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

Martin Thomson <notifications@github.com> Wed, 15 April 2020 00:45 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 40DB53A13A6 for <quic-issues@ietfa.amsl.com>; Tue, 14 Apr 2020 17:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.721
X-Spam-Level:
X-Spam-Status: No, score=-1.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.168, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, 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 OO4Qjou3OYRe for <quic-issues@ietfa.amsl.com>; Tue, 14 Apr 2020 17:45:25 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7C243A13A3 for <quic-issues@ietf.org>; Tue, 14 Apr 2020 17:45:25 -0700 (PDT)
Received: from github-lowworker-3a0df0f.ac4-iad.github.net (github-lowworker-3a0df0f.ac4-iad.github.net [10.52.25.92]) by smtp.github.com (Postfix) with ESMTP id 8FBC01C0C4B for <quic-issues@ietf.org>; Tue, 14 Apr 2020 17:45:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1586911524; bh=EO9SIht08YInxy3aVDkmSv3eetk81PoaRfhpi0HBET8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qf9NQpbHfFdkDyrFKSgD4ELhYVHoKM+7UgyiN8BdRaVCE3/Qy/qFbvg/RhfaF12h2 l3HrKE5BZWGiqpOmWEjeWgBE+dE1x+4sBYP2NyhxOJcC8xBRlLOai9LXp9EWg/i3Qf uEKlT+Lf021bMgwfoCLkSVAbkOcM5f7mmzQwEum4=
Date: Tue, 14 Apr 2020 17:45:24 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY7H6QRKVE3QRDBD4V4UI5CJEVBNHHCGQM7OQ@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/393386930@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_5e96592480847_495d3fb87dacd9681897c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/JgahAz2BAJolZShMwl7ms_GddNk>
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, 15 Apr 2020 00:45:27 -0000

@martinthomson commented on this pull request.



> @@ -2246,6 +2246,14 @@ 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 with a peer that uses a zero-length
+connection ID, for two reasons. First, if the peer routes incoming packets using

This is specifying the client reaction to the situation when disable_active_migration is not set, that's all.  Mostly the second reason applies here, as you are right that the server is responsible for that, but it doesn't mean that it is untrue.

-- 
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#discussion_r408516738