Re: [quicwg/base-drafts] New connection IDs are mandatory for intentional migration (#2414)

ianswett <> Mon, 11 February 2019 21:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 91C311311DC for <>; Mon, 11 Feb 2019 13:18:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
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_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oRU1roz86pch for <>; Mon, 11 Feb 2019 13:18:19 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9F43B1311C1 for <>; Mon, 11 Feb 2019 13:18:19 -0800 (PST)
Date: Mon, 11 Feb 2019 13:18:18 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1549919898; bh=qUgUfKn4Tq/mliiqnZo0Dnpi8CXVu9hBu52QNkXwuIU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iX1w+YfLV3SqqbT9NrrqjzJ4Ayd2hk3f4XHThT6wT3BV8lDtRWjem91yxfHLzYpWG X4ncqvYwUhUujfI5Iko7nw93IaMiJF4PVnI8fc4Lxn/so/q2jaasykOKtjQmWKjOwq PlhuBLiorUqlW9PnZKj3I5KbRBQk5qZxsGOqvvuU=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2414/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] New connection IDs are mandatory for intentional migration (#2414)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c61e69a87b28_3a123ff6f10d45bc334261"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 11 Feb 2019 21:18:25 -0000

ianswett approved this pull request.

One small suggestion, but I think this LG.

> @@ -2089,15 +2091,18 @@ different local addresses, as discussed in {{connection-id}}.  For this to be
 effective endpoints need to ensure that connections IDs they provide cannot be
 linked by any other entity.
-This 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
+Endpoints MAY move to a new connection ID at any time.

Nit: move to may not be clear.  How about "Endpoints MAY change the Destination Connection ID they send in short header packets at any time." assuming that statement is correct.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: