Re: [quicwg/base-drafts] rate-limiting of CID issuance needs to be allowed (#2436)

Kazuho Oku <> Fri, 08 February 2019 18:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7D107126D00 for <>; Fri, 8 Feb 2019 10:07:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 9isLF9GxzD0I for <>; Fri, 8 Feb 2019 10:07:26 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 63639124BF6 for <>; Fri, 8 Feb 2019 10:07:26 -0800 (PST)
Date: Fri, 08 Feb 2019 10:07:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1549649245; bh=Yqecxy9NbBajZk+DJcJ2yI1S4TcNd37cE/v7WpcN3pw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=buPxVFOCuamj0z1ZmLPYyGgFBhwjst2LTMHUm2EPYYN5XJl5NVGB1+3h8COfiBjwX hSl+FeIsqVz5VtDwZ1EjIc4hIhp1ZYZ0M4NNlByBjJJGibcWxtNaYuhVVp/mYtycyn IFuIAyhTjgjAvyInd6KJOcOWBccIHHiDHRnUThkM=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2436/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] rate-limiting of CID issuance needs to be allowed (#2436)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5dc55d1c751_5c343fee886d45b4108157"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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, 08 Feb 2019 18:07:28 -0000

@MikeBishop Partly yes. "always" indeed seemed strange to me.

What I want to see is something along the lines of "don't blame the server if a client runs out of CIDs when retiring them at high rate", as well as clarifying the reasons why a server developers might want to  limit the issuance of CIDs (as a guidance).

PS. Honestly speaking, I'm interested in simply capping the total number of CIDs issued for each connection rather than rate-limiting. That'd be fine for H3, because a server running out of CIDs can send GOAWAY.

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