Re: [quicwg/base-drafts] CID change still required in response to migration? (#2778)

Eric Kinnear <> Tue, 11 June 2019 00:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2771D12008D for <>; Mon, 10 Jun 2019 17:54:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Status: No, score=-6.463 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 RvcB-iLDYYBX for <>; Mon, 10 Jun 2019 17:54:09 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 41ABC120048 for <>; Mon, 10 Jun 2019 17:54:09 -0700 (PDT)
Date: Mon, 10 Jun 2019 17:54:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560214448; bh=YEW0hY4sR9Ysy8x1zKhoZk/KcUf7ouwmHnoNe8w7TIQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=p2TJ1uk2Jwb/GmZR3c6e7MxWr3KdVQaz8BGdabRQ0y9tCqjHZeZEvQTg3Y746HHyv vumGfRcNjsQNGTMEgHOa2o84QtSXx9pkNPt2X/wvcpjR1Cx4TWm0gVfnDCm5S0Zta2 Oq/TxHuLyQE+T0sTLOFqzrCe1R50Yu8arTYK168U=
From: Eric Kinnear <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2778/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] CID change still required in response to migration? (#2778)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cfefbafebeda_4ac33fc8d3acd95c139785"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: erickinnear
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: Tue, 11 Jun 2019 00:54:11 -0000

I think at one point we said "SHOULD change if the peer changes, but be careful not to loop". Otherwise it's pretty trivial to establish linkability, so everything is structured about trying to make sure you can do it, but not falling over too hard in the edge cases where you may not be able to.

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