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

martinduke <> Wed, 01 April 2020 17:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0A6ED3A13C9 for <>; Wed, 1 Apr 2020 10:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Status: No, score=-3.099 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 LrIZp56-Gndq for <>; Wed, 1 Apr 2020 10:12:55 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CE9823A13B4 for <>; Wed, 1 Apr 2020 10:12:49 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A0DE62C0C06 for <>; Wed, 1 Apr 2020 10:12:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1585761168; bh=OtRrHwzeNepX+F5tnYAYX4ci/2D/ZO+3S5mOwr8Xnzc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=B+h09mN6eFBrunNRDd+5mUI0tHoGgDAMB0thdXOH3fEe4xWD/LHSIhzLXAHpLLpJ3 6EvUrFmaZ15hVDtbFKSyJ3EXsT+W9krGc7E9CgAuxbEHfvXqp/uZtvJ/xMz5hdyJvI UtKERTc7pvyVUdbN2x4kvVTlK7qwufyivU7mUDKA=
Date: Wed, 01 Apr 2020 10:12:48 -0700
From: martinduke <>
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_5e84cb9092c04_43ea3fdb77ccd96c99765"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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: Wed, 01 Apr 2020 17:12:58 -0000

@martinduke commented on this pull request.

> @@ -1069,6 +1069,15 @@ 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 SHOULD 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, the limit on the number of outstanding
+RETIRE_CONNECTION_IDs SHOULD be at least the active_connection_id_limit. An

@kazuho I believe my psuedocode indicates that the current version of the PR doesn't add more state for various values of "maximum RCIDs inflight" as long as it's small enough that you can fit it all in one QUIC packet. If the RCIDs are spread over multiple packets inflight then keeping track of RCIDs requires a scoreboard.

The exact threshold to throw an error is indeed not needed in the spec. However @ianswett, rightfully, requested a MAY around the error to set expectations for debugging.

I do think we should change the word "outstanding" to "in flight" just to make it a bit clearer.

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