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

Lucas Pardue <> Wed, 27 May 2020 01:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C24BA3A0C9B for <>; Tue, 26 May 2020 18:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Status: No, score=-1.555 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_20=1.546, 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 q5BN5ds4N24h for <>; Tue, 26 May 2020 18:06:34 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 61D0D3A0C99 for <>; Tue, 26 May 2020 18:06:34 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D24A3960CFF for <>; Tue, 26 May 2020 18:06:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1590541592; bh=kPTUCuFiqIym9s3EEgrgNHjla+BWmOchy9ubUYEjn/E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=M/K1fTxA0s8jeWhVGBkNZaJMNtg1WCz0zZx8Zc6jjtv5SUx1BWs5ujGRjlSD6XhEP Hjx7Ucu2gZ0tK5QAu4gI+SowZuXiPGEZt4eswxGgI5jgK/O3xv6Kkiam0dvCGOBqnX y9Go6LZaNDEQNwNHKlJtfy+vTJV5L7bUn55dzGek=
Date: Tue, 26 May 2020 18:06:32 -0700
From: Lucas Pardue <>
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_5ecdbd18c2d68_74383fc5586cd95c145333"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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 01:06:36 -0000

@LPardue 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

Maybe not a direct result of this change but now I'm confused what happens if the server sends a CANCEL_PUSH that references a Push ID of a valid completed push stream. Do nothing seems like the right call.

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