Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created??

Martin Thomson <martin.thomson@gmail.com> Fri, 26 April 2013 20:50 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 3FD6921F97EF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 26 Apr 2013 13:50:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 dC-fasetSt9R for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 26 Apr 2013 13:50:34 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 9F83D21F96AC for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 26 Apr 2013 13:50:34 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UVpal-0001iB-46 for ietf-http-wg-dist@listhub.w3.org; Fri, 26 Apr 2013 20:50:03 +0000
Resent-Date: Fri, 26 Apr 2013 20:50:03 +0000
Resent-Message-Id: <E1UVpal-0001iB-46@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <martin.thomson@gmail.com>) id 1UVpag-0001Ea-Pq for ietf-http-wg@listhub.w3.org; Fri, 26 Apr 2013 20:49:58 +0000
Received: from mail-wi0-f182.google.com ([209.85.212.182]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <martin.thomson@gmail.com>) id 1UVpag-0002b0-8Z for ietf-http-wg@w3.org; Fri, 26 Apr 2013 20:49:58 +0000
Received: by mail-wi0-f182.google.com with SMTP id m6so1057858wiv.9 for <ietf-http-wg@w3.org>; Fri, 26 Apr 2013 13:49:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=6M+qltCCgXck/zqyxJhKciZeJFaai2HMf3XtGn9rf0Q=; b=mVc/AUxyL2UB4JRSOAYF7p9J3pB0zKU5doAG2F0NRmQt9m+KQXqrZK0V1IRvI8s/6M sTCPAUQtUxPLDggOXEppiEaQc3vUhEe0yMkh8cwejOnuG8ga/G+h8hSJ6xHgNByYpXpg YON1/G9T6laUz0wIKOK/V1oqJHcyO/vkLgDfs0WFGuEnrinxshgsffQnWHiJbnmDn4H4 2rhH67FDdNq4xp/1lrjM+2PHj/918qMKlHWa3nfdbCCtewMKTy/bsQYIwxT47tUXd+UK JkkoIP0dsWjRPc8bq+qh0uT4vKPyqqHeYdndSB1g3PEI/dLUNj5MCioUPvnPL2l63DS4 e9Hg==
MIME-Version: 1.0
X-Received: by 10.180.183.133 with SMTP id em5mr6319549wic.26.1367009372163; Fri, 26 Apr 2013 13:49:32 -0700 (PDT)
Received: by 10.194.33.102 with HTTP; Fri, 26 Apr 2013 13:49:32 -0700 (PDT)
In-Reply-To: <CABP7RbeAb71vTmnGbR65wVepyT=WykdRcRNFYDuWoprWD7+2gg@mail.gmail.com>
References: <CABP7Rbe808o_rqxnvVvH6OJxqFSvOnoLgnaQT5goFabBF_zi0A@mail.gmail.com> <CABkgnnUBnr8+_bbFRGMhnWSkGK5N+DoX75m8bHuLfa0Zbq4=CA@mail.gmail.com> <CABP7RbeAb71vTmnGbR65wVepyT=WykdRcRNFYDuWoprWD7+2gg@mail.gmail.com>
Date: Fri, 26 Apr 2013 13:49:32 -0700
Message-ID: <CABkgnnW5tDqVwRJE99Fkd5YFeAcRZYPV40QjuBrdrZxbKj6+9w@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: James M Snell <jasnell@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.212.182; envelope-from=martin.thomson@gmail.com; helo=mail-wi0-f182.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.671, 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 1UVpag-0002b0-8Z acfe7dad0e66d5997b17e327c4eb60a5
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created??
Archived-At: <http://www.w3.org/mid/CABkgnnW5tDqVwRJE99Fkd5YFeAcRZYPV40QjuBrdrZxbKj6+9w@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17623
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>

On 26 April 2013 13:43, James M Snell <jasnell@gmail.com>; wrote:
> I think I disagree on that point and say that I think it's much safer
> if we require that streams be initiated with only headers-bearing
> frames.
>
> Imagine, for instance, that a sender sends along a DATA frame with a
> new, previously unused stream identifier. Without an associated
> headers frame I have absolutely no context with which to determine
> what I need to do with that DATA frame. Likewise if I receive an
> RST_STREAM that references a previously unused stream identifier. If
> there's absolutely nothing that I can reliably do with it, or not
> reliable way that I can interpret it without additional context, then
> we should not allow it.

I believe that this is exactly the scenario that the websockets
binding will take advantage of.  (Maybe there is some need to expose
some header information there, but that's a case that needs to be made
for that specific use of the framing layer.)