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

Martin Thomson <> Mon, 11 February 2019 01:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 47BFA130E57 for <>; Sun, 10 Feb 2019 17:18:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Status: No, score=-6.597 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_28=1.404, 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 v9-icmW1Mlo5 for <>; Sun, 10 Feb 2019 17:18:47 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 764CB12F18C for <>; Sun, 10 Feb 2019 17:18:47 -0800 (PST)
Date: Sun, 10 Feb 2019 17:18:46 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1549847926; bh=N5YckE99i4jq/FFfIRBODtfDWEnheIrWUbVUGDEkzY0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WKcsPxrHsHQhnKfzYhpBkRMOFBNEpD7JvuefhRXYimPqrZIxBtdtEhUqOVrH6zzZd vffxnYnrtM9fUZaEtDiKQTPwJVIoz4ucVjmmnq4ZeijKF6LXucKCh6nRLQZ0xDAEy2 rABQDpDHx9knW3jDIf1CpxcjLBN1jCPTTn/7IVu0=
From: Martin Thomson <>
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_5c60cd765f558_6c643fbfcfed45bc7678a"; 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
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 01:18:49 -0000

martinthomson commented on this pull request.

> @@ -2089,15 +2091,19 @@ 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
+Endpoints MAY move to a new connection ID at any time.
+An endpoint MUST use a new connection ID if it initiates connection migration,
+unless the peer has selected a zero-length connection ID.  Using a new

Yep, trimmed it down.

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