Re: [quicwg/base-drafts] clarify what happens when consuming CIDs excessively (#2428)

Martin Thomson <> Wed, 06 February 2019 04:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BBC76126C7E for <>; Tue, 5 Feb 2019 20:14:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.552
X-Spam-Status: No, score=-7.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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_NONE=-0.0001, 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 CnPjxP5rB6u6 for <>; Tue, 5 Feb 2019 20:14:28 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 14A03123FFD for <>; Tue, 5 Feb 2019 20:14:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=vk9zbq0B5Kt3Ad73JejmupFDX5E=; b=KXCDpqaKVkMqjpHt 6ebUW8ydRtHyB9OW8YdFR3cCDilEoyamo6IXWatM5z/MQ36xiS0uxxrqrW4gWbtY 9HwQmD5OgG+94XKH00EmqWvhk3f/C2tO4RXb1BbUthMGd8ml6gm0SBvJYJAvGnmv 1bm8YsTS19+R1v1zGgf6LpWwJW4=
Received: by with SMTP id filter0580p1iad2-26101-5C5A5F22-11 2019-02-06 04:14:26.472814426 +0000 UTC m=+28451.782665947
Received: from (unknown []) by (SG) with ESMTP id nYcUBhZXTVm7DprwhO37Uw for <>; Wed, 06 Feb 2019 04:14:26.523 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 7E11BA80241 for <>; Tue, 5 Feb 2019 20:14:26 -0800 (PST)
Date: Wed, 06 Feb 2019 04:14:26 +0000
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2428/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] clarify what happens when consuming CIDs excessively (#2428)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5a5f227caaa_7cb53ff753cd45bc92335"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0ll7g/9PFr62qyuIXvbcKw07OGYEcy5rEzAe ej6blxQPCzN6QTEoc012xEzuCbb53oy9qDqaE0O6SFc1Xm7z22U58MKea2+FWPGKu/meTaPdYM7YM1 uf67tpadKk1vpi7bn2NOClpxumwtsIRbccdVJ2CVQrqC7YH2LC3s25D0g+Q0uS/eIuffUEltIYYe3Z M=
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: Wed, 06 Feb 2019 04:14:30 -0000

I don't want to put this in the draft.  It tells endpoints not to change connection IDs based on some unspecified (scary!) constraints that may or may not be present in a peer.

I realize that there might be a limited supply in some implementations, but artificial constraints on the rate of use is not the way I would address the problem.  Refusing or slowing issuance of new connection IDs if someone retires too many is a better approach.  In other words, implementations should deal with this on their own.

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