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

Martin Thomson <> Mon, 30 March 2020 03:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 015423A09C3 for <>; Sun, 29 Mar 2020 20:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Status: No, score=-1.2 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_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 TYVZlNQFE4C4 for <>; Sun, 29 Mar 2020 20:48:28 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D96243A09BE for <>; Sun, 29 Mar 2020 20:48:27 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id C2716E004E for <>; Sun, 29 Mar 2020 20:48:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1585540106; bh=JGxebw0TPapO0fPS8qQM970XTF5cp1xH9WAFovLXpXE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ShLx8F3MLpLgM4VdY481wx1QwumCtaztwIcXkFMWIjJfv2Jyz4WXKUq3tMiHsHNn0 NyqZobNq+zFCpE7ehcZtR+elYddfDNUfheBHVk9WV77THzPPuLCzSJI+4O/MB+nOyw CtLJb2V96ZZuwiSboN6RbygE1OwIibYiJbLi4k8c=
Date: Sun, 29 Mar 2020 20:48:26 -0700
From: Martin Thomson <>
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_5e816c0ab2671_37dd3fa2d22cd968734618"; 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 03:48:30 -0000

I know that you have characterized this as "leaky", but I'm not sure that I understand exactly what is being leaked.  Nothing is lost in #3547, except that the endpoint requesting retirement has to tolerate a potentially extended period without old connection IDs being retired.

In case this helps, I have no big preference between #3547 and #3550.  There is a certain elegance to #3550 that might tip me toward that, but it is slightly more disruptive.

I prefer either of those to the more disruptive change in #3553, which also has the downside of strongly encouraging connection ID changes in order to preserve a clean separation between active and retired.  #3553 doesn't force you to drop old connection IDs.  However, the encoding of the frame is just too complicated for me to accept.  I would prefer forcing a clean separation than having a complex encoding like this.

#3548 is a non-starter for me for the reasons stated.

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