Re: [quicwg/base-drafts] Servers should always send CANCEL_PUSH (#3700)

Mike Bishop <> Wed, 27 May 2020 13:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 632F33A0ADA for <>; Wed, 27 May 2020 06:49:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.482
X-Spam-Status: No, score=-1.482 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_24=1.618, 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 kfXw_pn6Kjf9 for <>; Wed, 27 May 2020 06:49:19 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 112BC3A0AD8 for <>; Wed, 27 May 2020 06:49:19 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 32D068C0F18 for <>; Wed, 27 May 2020 06:49:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1590587357; bh=we1/qYotpuPFkD2YYYu5P/Xqwis9tFhmZeVdmSX2Pco=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bTcaAnUmA5M0ia3z6M8P5hiYk54PDcXdYsJXneip7glBbC1Dk4fgGrmuHsLsTGP9v 22pQVK7Koi4LpIjZV+gZwLODaN0HwFUF+FC8qNvnJsCzppesMO/0gsba/u78JdHRCn JpHqkpQNynPbb7TdzlXjM1TMH0+gdGBESYLTG250=
Date: Wed, 27 May 2020 06:49:17 -0700
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3700/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Servers should always send CANCEL_PUSH (#3700)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ece6fdd238ca_4e193f83e44cd964125089"; 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: Wed, 27 May 2020 13:49:20 -0000

@MikeBishop commented on this pull request.

>  When a server sends CANCEL_PUSH, it is indicating that it will not be fulfilling
-a promise and has not created a push stream.  The client should not expect the
-corresponding promise to be fulfilled.
+a promise.  The client cannot expect the corresponding promise to be fulfilled.
+A server SHOULD send a CANCEL_PUSH even if it has opened the corresponding

Added text to this effect.  And that in fact could happen -- if we're suggesting a CANCEL_PUSH whenever the server abandons a stream (i.e. RESET_STREAM), it could be doing that to abort retransmissions even after writing the full payload.  The full payload might still have arrived if there's no loss.

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