Re: [quicwg/base-drafts] Section 4.2.6 PUSH_PROMISE does not indicate on which stream type this frame is allowed (#1920)
Lucas Pardue <notifications@github.com> Mon, 29 October 2018 12:54 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 A10DE130F18 for <quic-issues@ietfa.amsl.com>; Mon, 29 Oct 2018 05:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 N0kMvhrVE0kA for <quic-issues@ietfa.amsl.com>; Mon, 29 Oct 2018 05:54:08 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D47E2130F17 for <quic-issues@ietf.org>; Mon, 29 Oct 2018 05:54:07 -0700 (PDT)
Date: Mon, 29 Oct 2018 05:54:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1540817646; bh=TPlvoTQ16CxwsoSpxEO/7E1Mxl+4H6Voa9JVKiWcWao=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pVe5HsjfnzVoLroG8lvd/KnVaIgPoDptR62oPlPK7mM30+xXSdpnB8NJUMQI1Vgx6 WgI1q/zg0umBMGha4ftY36Katj7Y3voAiINVqwo58WuI56gJoEZDeICAA1riEv832W U3XJN35/dfYP0/c3x1BUTKx1EvqeXg0paPjRXl1g=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4f50ee3742379917573d6d66bc150940654942c992cf0000000117eec4ee92a169ce164d1592@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1920/433898812@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1920@github.com>
References: <quicwg/base-drafts/issues/1920@github.com>
Subject: Re: [quicwg/base-drafts] Section 4.2.6 PUSH_PROMISE does not indicate on which stream type this frame is allowed (#1920)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bd702ee715ea_772d3ff8708d45c02469297"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/hhqF3gsneZ3ETO5p4nJMz6KkTPI>
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: Mon, 29 Oct 2018 12:54:09 -0000
FWIW this is explained in section 5. > The header of the request message is carried by a PUSH_PROMISE frame (see Section 4.2.6) on the request stream which generated the push. But I agree that conistency in the frame descriptions could help. -- 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/issues/1920#issuecomment-433898812