IETF Logo Mail Archive

Re: [quicwg/base-drafts] Rework flow of Push ID (#3925)

Mike Bishop <notifications@github.com> Wed, 22 July 2020 20:23 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C07173A0900 for <quic-issues@ietfa.amsl.com>; Wed, 22 Jul 2020 13:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JPGbTK9SLl-b for <quic-issues@ietfa.amsl.com>; Wed, 22 Jul 2020 13:23:27 -0700 (PDT)
Received: from out-18.smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 891A93A08F9 for <quic-issues@ietf.org>; Wed, 22 Jul 2020 13:23:27 -0700 (PDT)
Received: from github-lowworker-39ac79b.ac4-iad.github.net (github-lowworker-39ac79b.ac4-iad.github.net [10.52.18.15]) by smtp.github.com (Postfix) with ESMTP id 832D2340BF5 for <quic-issues@ietf.org>; Wed, 22 Jul 2020 13:23:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1595449406; bh=NYJbvxFdLTCphBG55WDCEZ5jDbW04e8jmBL7xQJwrZY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=svmphWrnIMvz7YDxjayb+CMqNJvHWkxDwwxFDxe/4bu3rVZDFnqjq76usPxnrdvaX 0HTecFY/730fViyt8pPi2815e4VFxPBra9WSkh5VXxjXlcGQ5Qa/MTExHZ7AV/pRG3 NJm+ysAadYSSLcqMeTTSJhaihZtzqsykulZEm0xo=
Date: Wed, 22 Jul 2020 13:23:26 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZI3WJFLBN6EDYQHXF5ESAT5EVBNHHCPBRDMY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3925/review/453656257@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3925@github.com>
References: <quicwg/base-drafts/pull/3925@github.com>
Subject: Re: [quicwg/base-drafts] Rework flow of Push ID (#3925)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f18a03e72da7_16203fc0700cd96873277"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/L2leugBKrQNR2kKOUvQ5mV920R8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2020 20:23:29 -0000

@MikeBishop commented on this pull request.



> +Push stream data can also arrive after a client has canceled a push. In this
+case, the client can abort reading the stream with an error code of

Actually, it turns out the same SHOULD is present in the CANCEL_PUSH section anyway:

> When a server sends CANCEL_PUSH, it is indicating that it will not be fulfilling
> a promise.  The client cannot expect the corresponding promise to be fulfilled,
> unless it has already received and processed the promised response. A server
> SHOULD send a CANCEL_PUSH even if it has opened the corresponding stream.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3925#discussion_r459060561

v2.23.0 | Report a Bug | By Email