Re: [quicwg/base-drafts] Additional error cases for CANCEL_PUSH (#3083)

ianswett <> Mon, 14 October 2019 23:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5B52E120893 for <>; Mon, 14 Oct 2019 16:00:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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_32=0.001, 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 vDT3HiPpTwsm for <>; Mon, 14 Oct 2019 16:00: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 72466120894 for <>; Mon, 14 Oct 2019 16:00:26 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 7C156C6114C for <>; Mon, 14 Oct 2019 16:00:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571094025; bh=A0r8fn7QhWs7gazyjAZWiI1GadugS9pi7eQocrHHFuw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k6J+ayzs8riM26I4POG+YXVLLNgEjDfEA5scJ7sBleK6SYYllRFZlwfXrtcqyUgnj cvy+j3AwZrsNpfbO9MfBe7dRh4RauMc5qr+1UaI06HDciGzHfEfef3I3wmvb5HA7pM TGBhi33Kehum7LOTR0Cm/StW7eveowjs4bh2On7Q=
Date: Mon, 14 Oct 2019 16:00:25 -0700
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3083/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Additional error cases for CANCEL_PUSH (#3083)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5da4fe096da8c_70953f866d0cd9641085f1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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, 14 Oct 2019 23:00:29 -0000

ianswett commented on this pull request.

> -stream.  If the push stream has been opened by the server, the server SHOULD
-abruptly terminate that stream.
-A server can send the CANCEL_PUSH frame to indicate that it will not be
-fulfilling a promise prior to creation of a push stream.  Once the push stream
-has been created, sending CANCEL_PUSH has no effect on the state of the push
-stream.  The server SHOULD abruptly terminate the push stream instead.
+When a client sends this frame, it is indicating that it does not wish to
+receive the promised resource.  The server SHOULD abort sending the resource,
+but the mechanism to do so depends on the state of the corresponding push
+stream.  If the server has not yet created a push stream, it does not create
+one.  If the push stream is open, the server SHOULD abruptly terminate that
+stream.  If the push stream has already closed, the server MAY abruptly
+terminate the stream (cancelling any retransmissions) or MAY take no action.
+When a server sends this frame, it is indicating that it will not be fulfilling

When a server sends CANCEL_PUSH, it is indicating that it will not be fulfilling

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