Re: [quicwg/base-drafts] Push stream data and PUSH_PROMISE reordering clarification (#2527)

Martin Thomson <> Mon, 18 March 2019 22:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 260971311A8 for <>; Mon, 18 Mar 2019 15:22:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Status: No, score=-8.001 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, RCVD_IN_MSPIKE_H2=-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 J1glhObc8zjG for <>; Mon, 18 Mar 2019 15:22:38 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3CFCB12D861 for <>; Mon, 18 Mar 2019 15:22:38 -0700 (PDT)
Date: Mon, 18 Mar 2019 15:22:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1552947757; bh=g5k2SPuoCx7c2Q/L73s0ahu77RGcd6uBgTQS/QAx/0U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KjmrVzbZNp7js+8oG1TaYLXwaX3+r3qNinpcJdwZkyY0oSPfeU6i/d0TCr5iVRi+O PbdR/iYEAOa1dd3DKUmea8ID0mi/Cp+abaxcB4E7B/SUw36lGnbrB5xMu9rENqdjmp Gqg6EagD5rCpqv96cmyjOzJ7xMvv9sZ3iCh1VhmM=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2527/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Push stream data and PUSH_PROMISE reordering clarification (#2527)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c901a2d41593_32383f90ab8d45c0526552"; 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: Mon, 18 Mar 2019 22:22:48 -0000

martinthomson approved this pull request.

Seems like a good editorial improvement.

> @@ -1207,7 +1207,14 @@ the requests if the requested resource is already being pushed.
 When a server later fulfills a promise, the server push response is conveyed on
 a push stream (see {{push-streams}}). The push stream identifies the Push ID of
 the promise that it fulfills, then contains a response to the promised request
-using the same format described for responses in {{request-response}}.
+using the same format described for responses in {{request-response}}. Due to
+reordering, data on a push stream can arrive before the corresponding
+PUSH_PROMISE, in which case both the associated client request and the pushed
+request headers are unknown. Clients which receive a new push stream with an

CMOS change:
request headers are unknown. Clients that receive a new push stream with an

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