Re: Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't?
James M Snell <jasnell@gmail.com> Sat, 27 April 2013 20:32 UTC
Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59C8221F98DB for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 27 Apr 2013 13:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.393
X-Spam-Level:
X-Spam-Status: No, score=-10.393 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lc-rfGKNoQ5W for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 27 Apr 2013 13:32:51 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id DA1A221F98D4 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 27 Apr 2013 13:32:48 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UWBnS-0003Kn-Go for ietf-http-wg-dist@listhub.w3.org; Sat, 27 Apr 2013 20:32:38 +0000
Resent-Date: Sat, 27 Apr 2013 20:32:38 +0000
Resent-Message-Id: <E1UWBnS-0003Kn-Go@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UWBnO-0003K3-3l for ietf-http-wg@listhub.w3.org; Sat, 27 Apr 2013 20:32:34 +0000
Received: from mail-oa0-f50.google.com ([209.85.219.50]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UWBnN-0001E8-IH for ietf-http-wg@w3.org; Sat, 27 Apr 2013 20:32:34 +0000
Received: by mail-oa0-f50.google.com with SMTP id j6so4912516oag.23 for <ietf-http-wg@w3.org>; Sat, 27 Apr 2013 13:32:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=NFPEjbsaf7+zQUjCHI6tvWNFRiOCSLGgcnhv0uZ5RAs=; b=YLcn479jLQlMoGo/f5BxdNZjYDLqQvlazmB2RTtM1Kbha/ieRV8STLoQkfzS/CNaVY fqmJK77gNn6/Yla+uCdeNEG3b29mwH14ocSf9SRo/rRuoSIj0tzAHwNsaYi7ugxWZjJo CBDe+m++BMJLAQUQDHDqIj0lGxIhs3z3eNp9uGArW5ktXqsZd7kb6/EZ3tlUYqSyVSh9 qKfC2G/GmYn0E7OIwX7GNBRTshRRiDuFCN0C5IrOO/W47KqlScfTUy68D8UanzAI+dmf 7rNYibuwlaA8R0Oy+heNLFYE64DKIO7KIF40IYkgpy/WH6MmlDRLJefi72nOmCp7lGeu uMKA==
X-Received: by 10.60.76.234 with SMTP id n10mr25974992oew.63.1367094727717; Sat, 27 Apr 2013 13:32:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.60.3.137 with HTTP; Sat, 27 Apr 2013 13:31:47 -0700 (PDT)
In-Reply-To: <CABkgnnUpwM8aOzwt=Yb7_TsvNheotMYb+BD17eE7P4QaZSCdeA@mail.gmail.com>
References: <CABP7RbeOM_-fYHTt2UFcxTkXb8bU03_shQkq1p-99VWA+hCnXg@mail.gmail.com> <CABkgnnUpwM8aOzwt=Yb7_TsvNheotMYb+BD17eE7P4QaZSCdeA@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Sat, 27 Apr 2013 13:31:47 -0700
Message-ID: <CABP7RbeJAwkS03YsmhC1VB1b3Ln+BqA50wnfmAmxMCPqF2nbLg@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.219.50; envelope-from=jasnell@gmail.com; helo=mail-oa0-f50.google.com
X-W3C-Hub-Spam-Status: No, score=-4.5
X-W3C-Hub-Spam-Report: AWL=-1.750, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1UWBnN-0001E8-IH 694aea490a8f8a16fdd5ab130a076f12
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't?
Archived-At: <http://www.w3.org/mid/CABP7RbeJAwkS03YsmhC1VB1b3Ln+BqA50wnfmAmxMCPqF2nbLg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17635
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Ok, I have a pending push request that addresses these items. On Fri, Apr 26, 2013 at 11:38 AM, Martin Thomson <martin.thomson@gmail.com> wrote: > On 26 April 2013 11:28, James M Snell <jasnell@gmail.com> wrote: >> One can look at the various frame types and determine which are >> obviously intended for use with streams and which are for the session >> but we need to be clear on exactly what happens when various types of >> frames reference Stream ID #0. >> >> For instance, if a DATA frame reference Stream ID #0, I would say that >> the result MUST be a protocol error. (Likewise with HEADERS frames) > > DATA on stream 0 is an error, we need to make that clear. > >> Likewise, what exactly does it mean for a PING Frame to specify a >> Stream Identifier? Or are all PING Frames required to use Stream ID >> #0? > > PING on non-stream 0 is an error. The problem there is that PING > demands a PONG and you cannot know whether it is possible for the peer > to do that.
- Design Issue: Which frames are allowed to referen… James M Snell
- Re: Design Issue: Which frames are allowed to ref… Martin Thomson
- Re: Design Issue: Which frames are allowed to ref… James M Snell