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

MikkelFJ <> Sat, 09 February 2019 07:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3055B130F36 for <>; Fri, 8 Feb 2019 23:19:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Status: No, score=-8.001 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_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 ZarUAYcCaGh7 for <>; Fri, 8 Feb 2019 23:19:50 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 44447130F2F for <>; Fri, 8 Feb 2019 23:19:50 -0800 (PST)
Date: Fri, 08 Feb 2019 23:19:49 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1549696789; bh=V9noD4lhpWaY83krgal+LIgxy6ZeJWYvC90fMVFYmDU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BSskCEWkZT4QXdYp31Z3Mnor0wqL1Zvo95mhDZg9ghzEkS5J1MRkxI1BvH8Ai1KYX SDLp6GY2MqBQKOUJjOsZQlpjhKP/uFil4oQstArFpLgy3DGdYcmfQ4MZmcBKP2Fs5A QhhUgpxDKVKPsXXWG4ApdNXZ61njbxkQNOFk5pRk=
From: MikkelFJ <>
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_5c5e7f151aadb_44533ff5636d45b471438"; 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: Sat, 09 Feb 2019 07:19:52 -0000

> The proposal does not mandate such behavior. It's merely clarifying that such behavior is permissible.

I was concerned that you wanted to make it a requirement. Anyway, I'd also like that behaviour is reasonable predictable so app protocols don't have too many constraints on deployments. A stack used for HTTP might well be used for other things.

I'm still wondering if there are benefits to rotating CID's when not migrating, but I think there is since you might want to refresh routing tables. This is starting to be a separate, but related issue, but one thing is rate limiting, the other is convincing peer to rotate or not rotate within a given time frame, with no migration. I'd be best if transport could take the guesswork out of this.

Overall, I could see a requirement to rotate daily and requirement to supply a min count of CID's daily, just to ensure all entities, including middle boxes have something to work from.

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