Re: [quicwg/base-drafts] handle reordered NEW_CONNECTION_ID frames (#3202)

Mike Bishop <> Fri, 08 November 2019 15:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F12DF120133 for <>; Fri, 8 Nov 2019 07:04:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 LDlxZ7jkAPkV for <>; Fri, 8 Nov 2019 07:04:02 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 25C3612006F for <>; Fri, 8 Nov 2019 07:04:02 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 58082C602DE for <>; Fri, 8 Nov 2019 07:04:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1573225441; bh=enEiS1s3hAX3hxrHKrTaq2VdoohebesVSPNePbwfWXQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fr3lrVCDDDXBLb0/K0c4nQCrzZqaPf0IMb54PnweEtm69cdVsrt+j4vK/So1igJnm U01mZC4IXWpsojsV0t+WmZL5XV4M8SGozOqOluW7ZwFC3b4rtiKGkqgIf7161qOL8Y fxX83ygh7FVGSYxB4566InNkcn8N412hGpptHIKY=
Date: Fri, 08 Nov 2019 07:04:01 -0800
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3202/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] handle reordered NEW_CONNECTION_ID frames (#3202)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc583e14799b_50943f91104cd96c8886c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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, 08 Nov 2019 15:04:04 -0000

We had that at one point, didn't we?  It is a feature until you start doing probes on other paths.  If you use a CID on a different path, then want to retire it, that also retires a CID you might still be using on the main path.  And it's no problem if you have another CID to roll forward to, but it forces you to burn more CIDs than you otherwise would.  I believe there was also an objection to that model that the gratuitous CID rolls leaked signals about use of other paths.

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