Re: [quicwg/base-drafts] disable_active_migration with SPA (#3765)

Martin Thomson <> Mon, 06 July 2020 01:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4DF5D3A0D2A for <>; Sun, 5 Jul 2020 18:28:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Status: No, score=-2.009 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_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-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 xpSs1xrbEhdX for <>; Sun, 5 Jul 2020 18:28:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D5FEA3A0D29 for <>; Sun, 5 Jul 2020 18:28:25 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 0416A8C0E24 for <>; Sun, 5 Jul 2020 18:28:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1593998905; bh=QuyWvtEeyv+jfi7EM7d+cwx3adZ/XQO0ie3T4afwZSw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sPaukgJz0vmYWeTCPjv4b6Ll7AmsEN67vSLoZywNMewxT15j86FZBB81qbCFheZj1 IoWQmzRIUbCGmCpE+T6qKOFDi57YUQ77nwsUzmovXzfn7A3MqYH9Sxi73ZIYu2DWM8 Q5gH+kZI6LDMSbIR0EYUJG3EMSpLHuyd5gTCSgIg=
Date: Sun, 05 Jul 2020 18:28:24 -0700
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3765/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] disable_active_migration with SPA (#3765)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f027e38e8e61_2e8c3fcc330cd96c37636"; 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, 06 Jul 2020 01:28:27 -0000

I think that we were stuck on the meta-question, which is not about how to resolve the issue in a technical sense, but whether to resolve the issue in QUICv1 or an extension.  Given that we explicitly asked this question previously and resolved to defer to an extension, I think that the reason that this stalled is likely an unwillingness to say "no" again.  It's hard to look a use case in the eye and tell it that the bus is leaving without it.  But the bus is full.

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