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

Jana Iyengar <notifications@github.com> Thu, 16 May 2019 01:57 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 32B351200B8 for <quic-issues@ietfa.amsl.com>; Wed, 15 May 2019 18:57:36 -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 ccr9xeDanxyA for <quic-issues@ietfa.amsl.com>; Wed, 15 May 2019 18:57:34 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 313651200A2 for <quic-issues@ietf.org>; Wed, 15 May 2019 18:57:34 -0700 (PDT)
Date: Wed, 15 May 2019 18:57:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557971852; bh=MhWVRwYJdPnCyBzmTZ10+erbQg7IVl1VWukFW7gmUCw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BNfd6MNvsbP9RMYn9sIdW96n+75BbbG+6i/2ZbMTjBVxe36USYaDrlx9+xA0AdrYY Yb5K2UWqPhl3srRsYgHe0GX6NvP4kldh3y1QbYIZ7cHQoFpWLzCISPs/s/D3CX0UOw 8HJuMSIVi6CfFF9Bl2c7e2wI4tg2RviC8nmq+UgQ=
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK45OYVNYODEZNXWO6N25H3AZEVBNHHBUAUCHA@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/492886642@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_5cdcc38c8b24d_137a3fb9cc4cd964392483"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/nq3Oy2VP9_EByQxz8y_LXlYiHbQ>
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: Thu, 16 May 2019 01:57:36 -0000

Even if you do a REPLACE for future IDs, you can't currently require that the client stop using the current CID. So given that you have to wait an arbitrary amount of time for connections to "drain" anyways, I'll go back to my earlier comment: why not send GOAWAYs for connections you want to shed to the new partition?

If you really want to have dynamic balancing, it seems to me that there'd be more to gain by forcing the client to stop using the existing CID and using a new one. You would want to REPLACE IDs as well, but without forcing the client to move off the current CID, most connections won't move since most connections are unlikely to use a new CID unless the client is migrating (an uncommon event).

-- 
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-492886642