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

Nick Banks <notifications@github.com> Wed, 15 May 2019 17:40 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EB6E12015A for <quic-issues@ietfa.amsl.com>; Wed, 15 May 2019 10:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.392
X-Spam-Level:
X-Spam-Status: No, score=-6.392 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_24=1.618, 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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TGmTQjDIQHCo for <quic-issues@ietfa.amsl.com>; Wed, 15 May 2019 10:40:36 -0700 (PDT)
Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D631120132 for <quic-issues@ietf.org>; Wed, 15 May 2019 10:40:36 -0700 (PDT)
Date: Wed, 15 May 2019 10:40:35 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557942035; bh=umIfXXhnYSKAZET4WUVveCtIbjVBoiYaggkJOPdW7D4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Z2J9GhHQbnct176Dc0GBMo62P4lNMum5xt5xUToN21SATaF4GqumOzUPIN8UPp0Mp D59LQUCmFv9WUH0VSyLiDJVGI+flUYaJZL5MlkvSlbAVsNNoLGBrTf+XZU+UMYa0BF FmpvPcQDY/4koRZCpxfbx+GaTVxVpHhiKgyeaj/Q=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYZ3AKNPMOMUEGRY2V25GAZHEVBNHHBUAUCHA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2645/492752485@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2645@github.com>
References: <quicwg/base-drafts/issues/2645@github.com>
Subject: Re: [quicwg/base-drafts] Retire My Own CID (#2645)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cdc4f1362f91_75dd3fb50dacd9687453aa"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/cbiCctCF2VpmfQx49axIPRgcxIs>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 17:40:39 -0000

Allowing for an endpoint to edit/replace existing CIDs can allow all sorts of dynamic rebalancing logic on the LB side of things. Perhaps server ID is changed for a back end server and it wants to update all CIDs to encode the new ID appropriately.

The current design of give something to the peer and you're stuck with it forever, until they decide to stop using it seems overly restrictive. Additionally, if we support inplace CID replacement, the actual implementation logic to support this should be extremely trivial; just memcpy over the old one with the new one for the most part. The complexity only comes from endpoints that want to actually replace their own CIDs. They would need to have synchronization logic for it and so on. Endpoints that never need to do this don't accrue any additional cost.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2645#issuecomment-492752485