Return-Path: 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 05C8B1200F9 for ; Wed, 1 Jan 2020 17:17:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.999 X-Spam-Level: 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: 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 CYwc1WANvx1G for ; Wed, 1 Jan 2020 17:17:34 -0800 (PST) Received: from out-21.smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 804E21200DF for ; Wed, 1 Jan 2020 17:17:34 -0800 (PST) Date: Wed, 01 Jan 2020 17:17:32 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1577927852; bh=Jz638+TEHv8Dz77ic7yLH8bbcD/vLqJ+HAuPqj3Q7QI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NqzCv7nNK9cLHozLAGRddvSpyiwh0qzuv5CkTzWLFC6dGqYYnVdK49U4yYHgHaXZZ RoH6ohxyv7UWQvXUiC27B/0Dq43gER31Bwwh9f02nGuVTwon9RlxOdr8ghnHb7X01p I34BrfoBondYB0Xbxh6zIHek0VaTb2rLvF+EyTyw= From: Kazuho Oku Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Remove DUPLICATE_PUSH and allow duplicate PUSH_PROMISE (#3309) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5e0d44acc38fe_400f3f9a810cd96451136"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: kazuho X-GitHub-Recipient: quic-issues X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org Archived-At: X-BeenThere: quic-issues@ietf.org 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: Thu, 02 Jan 2020 01:17:36 -0000 ----==_mimepart_5e0d44acc38fe_400f3f9a810cd96451136 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit kazuho commented on this pull request. > -become available, or can initiate requests for discovered resources and cancel -the requests if the requested resource is already being pushed. When a client -receives a new push stream with an as-yet-unknown Push ID, both the associated -client request and the pushed request headers are unknown. The client can -buffer the stream data in expectation of the matching PUSH_PROMISE. The client -can use stream flow control (see section 4.1 of {{QUIC-TRANSPORT}}) to limit the -amount of data a server may commit to the pushed stream. +Due to reordering, push stream data can arrive before the corresponding +PUSH_PROMISE frame. When a client receives a new push stream with an +as-yet-unknown Push ID, both the associated client request and the pushed +request headers are unknown. The client can buffer the stream data in +expectation of the matching PUSH_PROMISE. The client can use stream flow control +(see section 4.1 of {{QUIC-TRANSPORT}}) to limit the amount of data a server may +commit to the pushed stream. + +If the same Push ID is promised on multiple request streams, the decompressed I think we can remove this sentence now that it is incorporated into the paragraph starting at line 605. Sorry for me not being explicit about the move when suggesting changes to that paragraph. -- 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/3309#discussion_r362354482 ----==_mimepart_5e0d44acc38fe_400f3f9a810cd96451136 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@kazuho commented on this pull request.

In draft-ietf-quic-http.md:

> -become available, or can initiate requests for discovered resources and cancel
-the requests if the requested resource is already being pushed. When a client
-receives a new push stream with an as-yet-unknown Push ID, both the associated
-client request and the pushed request headers are unknown.  The client can
-buffer the stream data in expectation of the matching PUSH_PROMISE. The client
-can use stream flow control (see section 4.1 of {{QUIC-TRANSPORT}}) to limit the
-amount of data a server may commit to the pushed stream.
+Due to reordering, push stream data can arrive before the corresponding
+PUSH_PROMISE frame.  When a client receives a new push stream with an
+as-yet-unknown Push ID, both the associated client request and the pushed
+request headers are unknown.  The client can buffer the stream data in
+expectation of the matching PUSH_PROMISE. The client can use stream flow control
+(see section 4.1 of {{QUIC-TRANSPORT}}) to limit the amount of data a server may
+commit to the pushed stream.
+
+If the same Push ID is promised on multiple request streams, the decompressed

I think we can remove this sentence now that it is incorporated into the paragraph starting at line 605.

Sorry for me not being explicit about the move when suggesting changes to that paragraph.

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

----==_mimepart_5e0d44acc38fe_400f3f9a810cd96451136--