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

Jana Iyengar <> Fri, 17 May 2019 00:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3919312032B for <>; Thu, 16 May 2019 17:51:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.606
X-Spam-Status: No, score=-6.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, RCVD_IN_DNSWL_HI=-5, 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 9yrTWMDnFiH8 for <>; Thu, 16 May 2019 17:51:56 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7B2F112004C for <>; Thu, 16 May 2019 17:51:56 -0700 (PDT)
Date: Thu, 16 May 2019 17:51:55 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558054315; bh=CgTA5cYGnDxBv+708gewKmANx8sDDKJdr0m2kXJWdKo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=y5BuhTiDBB4fRYwxy5Qv6boMti6wcj47BA5rZnqt80axA8lTEk0Hezfelp3mx+RXh PJNhyOdJsIqVCr2JzocK0tnq5yGzfid1zgCP6YOt6rjcbCTQnN1fLGmD3kI9vNso0C 50XmwRqEzaATug2MLuKthbWs27N4nrPDF1rBHB3o=
From: Jana Iyengar <>
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_5cde05ab8dcf2_75623fc4310cd96c5023e"; 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
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 00:51:58 -0000

As I've pointed out, I don't think the mechanism you're asking for is adequately useful for the problem you're trying to solve. I'm not opposed to solving the problem, which is why I'm trying to understand the problem itself.

As I said, you would still want a mechanism to replace the existing CID, without which you are stuck draining open connections that aren't changing CID through the life of the connection. I expect this to be fairly common -- most clients are unlikely to change destination CIDs unless there's migration involved. Given this, I still don't see how simply replacing future CIDs is adequate.

@ianswett : Do you think the proposed mechanism _without_ replacing the current CID is still useful? Where do you think you might use it?

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