Re: [quicwg/base-drafts] Required state for retaining unacked RETIRE_CONNECTION_ID frames is unbound (#3509)

martinduke <> Fri, 27 March 2020 02:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 344273A07CF for <>; Thu, 26 Mar 2020 19:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.553
X-Spam-Status: No, score=-1.553 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, 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 OmwrJeOJLij7 for <>; Thu, 26 Mar 2020 19:03:22 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CCB663A07CC for <>; Thu, 26 Mar 2020 19:03:22 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id CD7AD6A08A9 for <>; Thu, 26 Mar 2020 19:03:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1585274601; bh=lDee5pEjzu1MDUDsUACLILOQsWA0PfWxG2HKg1OVLRs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tVjwbgmPGKvBxLiN5SkaZZT3dw+KmT5Qf8kgbLAoV9aH5lVxF7XZWgyah0dfPS4ZO cjJM0boVWi9NAyAQQfqX6PWDRyVGN9V5BLwDlHBHeYyxTdREAKt94/PhYeFlSIc6sA HQo/fYeIpLIB3KjfsGtw/LbTHdI9Tp7dD/NML8ss=
Date: Thu, 26 Mar 2020 19:03:21 -0700
From: martinduke <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3509/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Required state for retaining unacked RETIRE_CONNECTION_ID frames is unbound (#3509)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e7d5ee9bd57c_43423f8db2ccd95c40883"; 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: Fri, 27 Mar 2020 02:03:25 -0000

@ianswett unfortunately we are cornered by the spec.

Consider two well behaving endpoints. I'm fully stocked with CIDs and then retire one with a frame. The peer gets the RCID and issues an NCID, but the ack of RCID is lost. If I don't count the CID as retired, then I MUST close the connection. That's bad, so I have to treat the CID as retired if I sent RCID.

If you drop acks at scale, this becomes an attack.

I'm really coming around to your cumulative retire idea, but will have another go at this tomorrow.

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