Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't?

James M Snell <jasnell@gmail.com> Fri, 26 April 2013 18:29 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 AB3FD21F9878 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 26 Apr 2013 11:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.218
X-Spam-Level:
X-Spam-Status: No, score=-10.218 tagged_above=-999 required=5 tests=[AWL=0.381, 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 A6r0YynCvUvZ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 26 Apr 2013 11:29:51 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 34F1121F984C for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 26 Apr 2013 11:29:51 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UVnOi-0000bj-OL for ietf-http-wg-dist@listhub.w3.org; Fri, 26 Apr 2013 18:29:28 +0000
Resent-Date: Fri, 26 Apr 2013 18:29:28 +0000
Resent-Message-Id: <E1UVnOi-0000bj-OL@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 1UVnOW-0000aT-IV for ietf-http-wg@listhub.w3.org; Fri, 26 Apr 2013 18:29:16 +0000
Received: from mail-ob0-f172.google.com ([209.85.214.172]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UVnOV-0003mm-KC for ietf-http-wg@w3.org; Fri, 26 Apr 2013 18:29:16 +0000
Received: by mail-ob0-f172.google.com with SMTP id v19so3825321obq.17 for <ietf-http-wg@w3.org>; Fri, 26 Apr 2013 11:28:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=FCDQE3scKE5xJ9n4cWEO2axgPxi6RW05WwNZwA9//+k=; b=jesFupS8So8ntoXHeuZlfPQoN6ploXCN6Hpk1PvsLq/PXk34gk1eIbas9YcDrMggDG 3Q4983mrSG1R3Beuy2AO/mAEXqMayeamKTOdDMY8C/exGur+LyBZWa2MCavE+GZr4TRi I/M4Q0UqydnWO/xMG7pqw/QiyVxLANnHlLLJky91DBrWPpWh2wDHgKs47yhqP36jFfCF QwKhkeRfufm97DQ+STzcx9yClhyKysr9J0+upT4w3RbtHxd0FlNzpIpo+Vf5JmvCpSbu wvugwt/GpwVhjpnryYhnzvkjnmNM/5nQqbl40tHF9ZtdEH3OJbml15IJcBjaJgogD1b/ qfMg==
X-Received: by 10.182.22.133 with SMTP id d5mr9018680obf.43.1367000929765; Fri, 26 Apr 2013 11:28:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.60.3.137 with HTTP; Fri, 26 Apr 2013 11:28:29 -0700 (PDT)
From: James M Snell <jasnell@gmail.com>
Date: Fri, 26 Apr 2013 11:28:29 -0700
Message-ID: <CABP7RbeOM_-fYHTt2UFcxTkXb8bU03_shQkq1p-99VWA+hCnXg@mail.gmail.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset=UTF-8
Received-SPF: pass client-ip=209.85.214.172; envelope-from=jasnell@gmail.com; helo=mail-ob0-f172.google.com
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-2.632, 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 1UVnOV-0003mm-KC 95e37246674af42af5247541bb37bdba
X-Original-To: ietf-http-wg@w3.org
Subject: Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't?
Archived-At: <http://www.w3.org/mid/CABP7RbeOM_-fYHTt2UFcxTkXb8bU03_shQkq1p-99VWA+hCnXg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17613
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>

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)

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?

- James