Re: [quicwg/base-drafts] Clarify CANCEL_PUSH server send conditions (#3387)

Martin Thomson <> Wed, 22 January 2020 22:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5CA5112004F for <>; Wed, 22 Jan 2020 14:35:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.682
X-Spam-Status: No, score=-3.682 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_MED=-2.3, 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 O3p2_vV3kwS3 for <>; Wed, 22 Jan 2020 14:35:14 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E913812001A for <>; Wed, 22 Jan 2020 14:35:13 -0800 (PST)
Date: Wed, 22 Jan 2020 14:35:13 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1579732513; bh=+W8v3IL+oSDczigSptbTHCmMSg9x9HuvkuvCJvhEfBs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WkBuxgVqugCLNGYlOPoobSVV035XfaD5pWjh7mKBnqdyD/M0FTo1Suehn47TW7iro 2ZZ/xwXSBCuIqoiu02aPxk7G1zSTdGma74CCN0nwimeBNekt41xFNIchRchihikb8k jus9Z/j/6pinYMRmJ6+Gv/aTOYAh9bfY/bsc51Ys=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3387/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Clarify CANCEL_PUSH server send conditions (#3387)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e28ce21125aa_21853fc8d72cd9601081a1"; 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: Wed, 22 Jan 2020 22:35:15 -0000

In some cases, creating a stream can result in a STREAM frame being sent.  It depends on the shape of the contract between the different components.  And it also might be difficult to determine whether anything has been sent.

I believe that the existing language is fine.

If you have created a stream object locally, and can be sure that the other side is unaware of this, and you have some means of taking it back or repurposing it, then it's fine to do that.  Note that this is only a "SHOULD" anyway.

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