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

Mike Bishop <> Mon, 19 August 2019 14:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D018C12013A for <>; Mon, 19 Aug 2019 07:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 Q46ZyLQFGd8W for <>; Mon, 19 Aug 2019 07:39:04 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 75898120815 for <>; Mon, 19 Aug 2019 07:39:04 -0700 (PDT)
Date: Mon, 19 Aug 2019 07:39:03 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1566225543; bh=z25vTsFMPsSIdk8jp8nWxfuZtEnjkviwD9Rv7+Nyq/o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k1Tl3DqaIUp5L0oeIdKs0G9bUf+vu/MUrxitWbFDKJdO7rOljRreNeqiOYMt2lMik iU6FY2E18NBumwtZ8kP8Ro/ypD3IDN9YPV3wta5ii69b8cN6lBMOEkURmDxKSkm3YU FW9YFUzL11b3zVRJbU9L4SLfYZ67+cSurQndY3VU=
From: Mike Bishop <>
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_5d5ab48782991_6b433ff8178cd9683246d2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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, 19 Aug 2019 14:39:06 -0000

I thought where we landed (in concept, not necessarily text) was that you MUST change CID any time you're using a different local or remote IP:port.  That means the client MUST change if it knows it's migrating (new source address); the server will change in response because it's going to a new destination.  The client SHOULD change if it has been quiescent and anticipates a NAT-rebind (i.e. uncertain about source address); if it actually got rebound, the server would change as well (new destination address).  If it turns out the client didn't get rebound, then IP:port already correlate it; perhaps slightly better if the server rotates, but it's not required to.

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