Re: [quicwg/base-drafts] Issue when a server cancels a push stream (#3698)

Martin Thomson <> Tue, 26 May 2020 22:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D03353A0A74 for <>; Tue, 26 May 2020 15:04:19 -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 aNblMbJ0XQ2k for <>; Tue, 26 May 2020 15:04:18 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 57F6D3A0A6E for <>; Tue, 26 May 2020 15:04:18 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A77F0C60EA0 for <>; Tue, 26 May 2020 15:04:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1590530657; bh=velnPQflLUlrMMQOh1w7Ax+yKnQ1UM6VkP/ciM/0zAE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Kc9X0AI0Q1J/7RDNqr83FDprFy2mK0FopgKsVhvRTCoseN8WebkgGXHTjYdz9ruRA jI+J3Fw/x+53Ej49n6grwGpw4jqs9nKNQbmXWvMpXtGIfBFbEpf0b9Mecj71P5vQDD NwonVFc07vJa19ZY+RnoREyUs1DZCFOxBr8yi3Pw=
Date: Tue, 26 May 2020 15:04:17 -0700
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3698/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Issue when a server cancels a push stream (#3698)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ecd926198120_12513fb6d24cd95c2195cf"; 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: Tue, 26 May 2020 22:04:20 -0000

The server doesn't need to ensure that the push ID is read if CANCEL_PUSH is used, mostly.  If the stream type is read, but not the push ID (which is entirely possible), then the client will know that there was a push and that it didn't happen, but can't connect that with the promise or cancellation.  In that case, clients need to handle that.

In fact, this highlights the value of CANCEL_PUSH in the case where the stream is reset.

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