Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)

Martin Thomson <> Tue, 31 July 2018 04:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7B83E130DF0 for <>; Mon, 30 Jul 2018 21:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Status: No, score=-8.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_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 X32lmuAdO99R for <>; Mon, 30 Jul 2018 21:15:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2B8A9130DE0 for <>; Mon, 30 Jul 2018 21:15:26 -0700 (PDT)
Date: Mon, 30 Jul 2018 21:15:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1533010525; bh=neYKC3AQ9r7Gu6BMviZNAf9lKudk6fzupanQ8MtyWac=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l29iei5blPDF/EfvKpQiKCaJ35m6OQX/OnCANLC9IF6KfgVTgGww0AXOIpoz3ngBE Uufks3o6x8OQhc/O3cKj6YDCHMU8mM9JwV0CvIT0CxIhvR3WlOUwL9Y55KcMl0lAZB kDngAQbQu0NEg+LWRrCv2C3lqECBG96VkN4IZ4fM=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/203/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b5fe25d8de64_55403fb699cd45bc599473"; 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.27
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: Tue, 31 Jul 2018 04:15:27 -0000

This is in the really hard bucket right now.  Other than genuinely doing a handshake (maybe with a PSK), this is easily detectable, if not trivially so.  Given the late stage of the process, unless a serious proposal emerges, this is not likely to change.

It's also questionable as to whether this is something we want to do.  The QUIC handshake tends to leak information in ways that a connection migration currently does not.

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