Re: Permissible states for extension frames #591

Ilari Liusvaara <ilari.liusvaara@elisanet.fi> Tue, 12 August 2014 17:03 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3981A03CF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 12 Aug 2014 10:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.57
X-Spam-Level:
X-Spam-Status: No, score=-7.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 7PBu1LrotyNc for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 12 Aug 2014 10:03:39 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08C271A039A for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 12 Aug 2014 10:03:36 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1XHFQh-0005vf-ML for ietf-http-wg-dist@listhub.w3.org; Tue, 12 Aug 2014 17:00:11 +0000
Resent-Date: Tue, 12 Aug 2014 17:00:11 +0000
Resent-Message-Id: <E1XHFQh-0005vf-ML@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <ilari.liusvaara@elisanet.fi>) id 1XHFQD-000321-Jl for ietf-http-wg@listhub.w3.org; Tue, 12 Aug 2014 16:59:41 +0000
Received: from emh01.mail.saunalahti.fi ([62.142.5.107]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <ilari.liusvaara@elisanet.fi>) id 1XHFQC-000092-KA for ietf-http-wg@w3.org; Tue, 12 Aug 2014 16:59:41 +0000
Received: from LK-Perkele-VII (a88-112-44-140.elisa-laajakaista.fi [88.112.44.140]) by emh01.mail.saunalahti.fi (Postfix) with ESMTP id 66F999007A; Tue, 12 Aug 2014 19:59:13 +0300 (EEST)
Date: Tue, 12 Aug 2014 19:59:13 +0300
From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20140812165912.GA21666@LK-Perkele-VII>
References: <CABkgnnVgnJSmJW2B4nJ8Vb-Nwi3EF2pra7D_m8uqZfQ8H1a2eA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <CABkgnnVgnJSmJW2B4nJ8Vb-Nwi3EF2pra7D_m8uqZfQ8H1a2eA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Received-SPF: pass client-ip=62.142.5.107; envelope-from=ilari.liusvaara@elisanet.fi; helo=emh01.mail.saunalahti.fi
X-W3C-Hub-Spam-Status: No, score=-3.2
X-W3C-Hub-Spam-Report: AWL=-3.214, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1XHFQC-000092-KA bc497c66384e246d5deb0b93cf58c7a6
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Permissible states for extension frames #591
Archived-At: <http://www.w3.org/mid/20140812165912.GA21666@LK-Perkele-VII>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/26593
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 Mon, Aug 11, 2014 at 03:03:24PM -0700, Martin Thomson wrote:
> We don't really say this, but the implication is that an extension
> frame can appear anywhere, for any stream. Worst case, you can have
> frames appearing with any stream number at any time.
> 
> Are we OK with this?
> 
> Or... do we want to limit the sending of extension frames on streams
> somehow. Note that the most permissibly constrained frame type is
> PRIORITY, which can appear in any state other than "idle". A similar
> constraint would be relatively easy to enact.

Just as IMO:

I don't think "out-of-the-blue" extension frames have any use in idle
state (since state must be idle afterwards as well). And letting those
frames modify the sub-state in some manner would likely be a DOS attack
waiting to happen.

But negotated extensions are different matter, since those might define
new stream-opening frame types (or something even more radical).


-Ilari