Re: [quicwg/base-drafts] Retire My Own CID (#2645)

MikkelFJ <> Fri, 17 May 2019 07:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D912D120253 for <>; Fri, 17 May 2019 00:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.606
X-Spam-Status: No, score=-1.606 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 2pf9AAHvMAfp for <>; Fri, 17 May 2019 00:07:10 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F1A6D12012B for <>; Fri, 17 May 2019 00:07:09 -0700 (PDT)
Date: Fri, 17 May 2019 00:07:08 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558076828; bh=VqTe58G3FFKu001ggRwjLyx9Jf4Hsbs5ciL15II93c8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=d20UcmGbI7/z+TtOFjLrWVwNM1c+tyoC+kdP97fZEjd5qnAD6GyUS9imlzDIZ24R+ F2c9t9OB3DIrbcqewpiXBspKcK2OrD+DLrUtxv+m8wzDH+kGvDI0v5hov1wMWu3PSe a3RFvmoUOgm8lpViVxUstE0I5ebAgwQPSjaDyuuQ=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2645/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Retire My Own CID (#2645)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cde5d9cc1a80_5d563fb2dbecd95c124586"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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: Fri, 17 May 2019 07:07:12 -0000

There is also the concern of conflating migration with targeted load balancing. Even if you did replace the current CID, what happens if the client migrates frequently. All future CID's would be drawn from a pool of CID's that might point to the wrong endpoint process. This means you would have to split up the CID's into two parts: an address and a sequence number, both appearing random externally. You would then change the address part, but leave the sequence selection to the client. This appears to be rather overengineered. Alternatively the current CID could be replaced post migration which might just be few roundtrips of sub-optimal performance before hitting the proper destination, under the assumption that migration is is not that frequent. This also shows that having the server initiate a migration (which is not currently possibly) is insufficient unless the client future CID's are tied to a specific server path.

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