IETF Logo Mail Archive

Re: [quicwg/base-drafts] Bundle new client connection ID and path challenge in migration probes (#1730)

ianswett <notifications@github.com> Mon, 10 September 2018 14:01 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 137AE130E04 for <quic-issues@ietfa.amsl.com>; Mon, 10 Sep 2018 07:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Level:
X-Spam-Status: No, score=-3.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 f94IoJ7eHRs6 for <quic-issues@ietfa.amsl.com>; Mon, 10 Sep 2018 07:01:12 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF873127333 for <quic-issues@ietf.org>; Mon, 10 Sep 2018 07:01:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=YcLE3fzGn52/22A4dif8aYUSbC4=; b=vE0DsqobhGy/DMb/ APD61M0n27wdTMUgq0YBzK2tfUdqC3rWw9GtFOXQFdn6QpbBe64cLv2peF1rjVGr Uyc6jBt0lawELtL7qhu6Nlaj+qgDLgph87uVJ5JvjlwVwR7zRZgwcbTubXyedrY/ evQ2bibwKsjETpYUcwxyR8wBp60=
Received: by filter1155p1las1.sendgrid.net with SMTP id filter1155p1las1-3908-5B96791B-35 2018-09-10 14:00:59.994566682 +0000 UTC m=+318043.617009979
Received: from github-lowworker-dcc078e.cp1-iad.github.net (unknown [192.30.252.44]) by ismtpd0023p1iad2.sendgrid.net (SG) with ESMTP id 5iSM_11QTvOYZbwFwPqGwQ for <quic-issues@ietf.org>; Mon, 10 Sep 2018 14:00:59.767 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-dcc078e.cp1-iad.github.net (Postfix) with ESMTP id D896E2C06B0 for <quic-issues@ietf.org>; Mon, 10 Sep 2018 07:00:59 -0700 (PDT)
Date: Mon, 10 Sep 2018 14:01:00 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abae204b779510f044f1ede59259b88233756490d292cf0000000117ae3b1b92a169ce155cc367@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1730/review/153787210@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1730@github.com>
References: <quicwg/base-drafts/pull/1730@github.com>
Subject: Re: [quicwg/base-drafts] Bundle new client connection ID and path challenge in migration probes (#1730)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b96791bd6b41_4ee73f954ced45c426040"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0hEUGYLwOQUVPsQRpEIO9oAUQntjjXYmjeky Hi5wxsknS7irUJmTMvumqizcOUR44VTf8WKWpPUT38jqnfsrfqNRByXztUF4IrB5Lan3xlWh5r34iy 1aWQcv6zjN19b6dFSA6sVSs3nZkvk6wJ5LYGzA1tOWa8E6XrPTlYN+CFyA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Eb3ODASmiPr-iNfplEOMalsTG4k>
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: Mon, 10 Sep 2018 14:01:14 -0000

ianswett commented on this pull request.



> @@ -2359,6 +2366,11 @@ genuine migrations.  Changing port number can cause a peer to reset its
 congestion state (see {{migration-cc}}), so the port SHOULD only be changed
 infrequently.
 
+Endpoints could also have their activity correlated if their peers keep using
+the same destination connection ID after migration. Nodes that initiate a
+migration need to provide their peers with new connection IDs. The goal is

need is non-normative, which feels odd to me, and there's no mention of zero-length connection IDs.

-- 
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/1730#pullrequestreview-153787210

v2.23.0 | Report a Bug | By Email