Re: [quicwg/base-drafts] Limit RCID state (#3547)

Martin Thomson <> Mon, 30 March 2020 01:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 09F493A0415 for <>; Sun, 29 Mar 2020 18:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.082
X-Spam-Status: No, score=0.082 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.282, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, 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 OtABCwBgNb-l for <>; Sun, 29 Mar 2020 18:07:35 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9953E3A0410 for <>; Sun, 29 Mar 2020 18:07:35 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 4F936660186 for <>; Sun, 29 Mar 2020 18:07:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1585530454; bh=qw3kGwc8YgTEQ5AbKth9tCHIOHN0Wf8hlVpDeOj2Jw0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JXRZv4AR/r51HP5yrpOVK9ufQSdIA0ygjhPh0fdWX6wgi/zkkuTAToHSOl1dS41aD xNljsuFDpNOKHmqobAV/MBXkRCqGTnLpTRQ/p0eHS809jJ5G5m1bPxmiTmjTn7xIm2 Qew7yWS9fZJ69m5gMGF1sfsNtfJ/EgCfT6yS1XWs=
Date: Sun, 29 Mar 2020 18:07:34 -0700
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3547/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Limit RCID state (#3547)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e8146563fb72_31ed3fe1c6ecd96076849"; 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
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: Mon, 30 Mar 2020 01:07:37 -0000

@martinthomson commented on this pull request.

I'm still unconvinced that we need to be as precise as @kazuho, but the other suggestions he makes are spot on.

> @@ -1069,6 +1069,17 @@ to cease using the connection IDs when requested can result in connection
 failures, as the issuing endpoint might be unable to continue using the
 connection IDs with the active connection.
+An endpoint MAY elect to limit the number of outstanding RETIRE_CONNECTION_ID
+frames to bound the necessary state. In order to allow a peer to retire all
+previously issued connection IDs, this limit SHOULD be at least the

"this limit" here seems a bit non-specific

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