Re: [quicwg/base-drafts] Push stream data and PUSH_PROMISE reordering clarification (#2527)
Mike Bishop <notifications@github.com> Sun, 24 March 2019 08:52 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 43464127979 for <quic-issues@ietfa.amsl.com>; Sun, 24 Mar 2019 01:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 Rm5SgnbsyWcI for <quic-issues@ietfa.amsl.com>; Sun, 24 Mar 2019 01:52:14 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C196A127971 for <quic-issues@ietf.org>; Sun, 24 Mar 2019 01:52:13 -0700 (PDT)
Date: Sun, 24 Mar 2019 01:52:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1553417532; bh=nHd6AVdNyinrx+fmmbV2pVhVwe82bj5todFIVWXVclM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mftpOY7x4RrTVB8KB8/sKn+5wMzVwQSDOYwg4OJiBrryfhY9vsSdQox5CmLFfmqZT rDS7qMatr+FBGDXJvvSmGJj03FWb5I6tF+y73dgFBRtI8VfXGlyuP9b2AI002Wp2EO RDDUPFUTmr5WwDNht1UcmyvXnUKp+TGsn2ZFSKuI=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab689d345e8df3fdeb516474a3dc38c9537ee363df92cf0000000118af073c92a169ce19290f08@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2527/review/218071525@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2527@github.com>
References: <quicwg/base-drafts/pull/2527@github.com>
Subject: Re: [quicwg/base-drafts] Push stream data and PUSH_PROMISE reordering clarification (#2527)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c97453c16e50_74b53fa63bed45c4149789"; 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/3a52rk783kd9QF8ONopBYcIX8XU>
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: Sun, 24 Mar 2019 08:52:16 -0000
MikeBishop commented on this pull request. > @@ -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 You haven't changed it _here_, though. -- 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/2527#discussion_r268423736
- [quicwg/base-drafts] Push stream data and PUSH_PR… Robin Marx
- Re: [quicwg/base-drafts] Push stream data and PUS… Lucas Pardue
- Re: [quicwg/base-drafts] Push stream data and PUS… Martin Thomson
- Re: [quicwg/base-drafts] Push stream data and PUS… Robin Marx
- Re: [quicwg/base-drafts] Push stream data and PUS… Robin Marx
- Re: [quicwg/base-drafts] Push stream data and PUS… Mike Bishop
- Re: [quicwg/base-drafts] Push stream data and PUS… Robin Marx
- Re: [quicwg/base-drafts] Push stream data and PUS… Robin Marx
- Re: [quicwg/base-drafts] Push stream data and PUS… Mike Bishop