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

ianswett <> Fri, 27 March 2020 11:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 52BE83A0C01 for <>; Fri, 27 Mar 2020 04:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Status: No, score=-1.696 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_28=1.404, 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 rLJfERrztwmy for <>; Fri, 27 Mar 2020 04:54:16 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CD3D23A0A52 for <>; Fri, 27 Mar 2020 04:54:16 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E0A0E8C0086 for <>; Fri, 27 Mar 2020 04:54:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1585310055; bh=CiidOHBZuU7k63+GwO0z++Hf3lj3IpBfoBlElfCT07A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lTwRGf4pdkYJDJgyH77LpeIP96O1tL5hPrQEHXx2oTA9ulNRXy1JiVB5DvYzdQJlw Q93BNJkqpKjZX1cX05Kb0pZNjn2vHtu0H+Gfl+i1uvQGPlIjERLdtJZVH57krwNocK uamOwriPxrIeoM98eGf2Rcy3SaqXJmub23giZxTU=
Date: Fri, 27 Mar 2020 04:54:15 -0700
From: ianswett <>
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_5e7de967d25d3_746c3fc3e86cd964104971"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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, 27 Mar 2020 11:54:28 -0000

@ianswett commented on this pull request.

> @@ -1069,6 +1069,18 @@ 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 only send or retransmit RETIRE_CONNECTION_ID frames
+with sequence numbers greater than or equal to the highest Retire Prior To field
+received minus its advertised active_connection_id_limit. This bounds the

You can only retire as many as you store, so the only way you could have more than max_connection_id_limit RETIRE_CONNECTION_ID frames outstanding is if you need to retransmit all of them due to loss and subsequently you've both received a new connection ID AND need to retire it.  Retiring it because you decided to use it typically takes at least a round trip, so it's most likely the subsequent retiring is due to the peer's Retire Prior To increasing again.

Given the above situation starts looking increasingly like an attack(or a bug) and sending RETIRE_CONNECTION_ID quickly for the Retire Prior To case isn't critical, I'd suggest max_connecion_id_limit is a better recommendation.

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