Re: Design Issue: Frame Size Items

James M Snell <jasnell@gmail.com> Wed, 08 May 2013 04:34 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 C9EFB21F8E77 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 7 May 2013 21:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level:
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 jPBY1tYQ4LYj for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 7 May 2013 21:34:02 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 737BD21F8E7B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 7 May 2013 21:34:02 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UZw3q-00073X-K1 for ietf-http-wg-dist@listhub.w3.org; Wed, 08 May 2013 04:33:02 +0000
Resent-Date: Wed, 08 May 2013 04:33:02 +0000
Resent-Message-Id: <E1UZw3q-00073X-K1@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UZw3a-000715-9o for ietf-http-wg@listhub.w3.org; Wed, 08 May 2013 04:32:46 +0000
Received: from mail-oa0-f43.google.com ([209.85.219.43]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UZw3Z-0001WL-6r for ietf-http-wg@w3.org; Wed, 08 May 2013 04:32:46 +0000
Received: by mail-oa0-f43.google.com with SMTP id o6so1569647oag.2 for <ietf-http-wg@w3.org>; Tue, 07 May 2013 21:32:19 -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:content-transfer-encoding; bh=PSt0XYZmewVITppZTrvxo7EW332h4LdgW3BYJLYee60=; b=z9hvcs5iOEW9vzfKkCar1uAQ8kEMsafjSr47xJN77GXU7e5hBq9pHUXzI3xxOi9frl F9GIysk+hGFYhxoawfNGAwkdEnHqRJVebUWD2zSoNmNTxwr43L+roceDIiW8jJ2m3ZYH ZzzFB7esFTWmu89DhdR4Ihwz16TuBySERblJk+vZEJzH6elne5fGu1k+d1kw8kgQRlp9 yGc54KORxai5s6VO+J5U7fMedt7t2yqixOQslTkxIE12w0RY0fTwfc6GHC2BqDyaGcG9 Ol1hfFDLKDUlnkjr2Vlr1VhVBruTrc9AJZwEu2aLg8dPF9cuu+M9qmvqnTPX/uNEUSQp H0bw==
X-Received: by 10.60.92.41 with SMTP id cj9mr1480396oeb.31.1367987539311; Tue, 07 May 2013 21:32:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.60.3.137 with HTTP; Tue, 7 May 2013 21:31:59 -0700 (PDT)
In-Reply-To: <CAA4WUYgKnYhgvArS7FSWqRSf4MfhRbymCiGOC3E21E6R32KWCQ@mail.gmail.com>
References: <CABP7RbcUDvmYjUjE703UTgOcYTSLBohR7EFw2Rb9u-EDkB7htg@mail.gmail.com> <CAA4WUYgwggq4FNweDCEfbsp-fN3yJ8p35jx=fK8Xc5adk+fUVg@mail.gmail.com> <CABkgnnVvhxw_h1QEM3U=pRwKFdZ5GudEiz+UwNf99M5vjMvVLQ@mail.gmail.com> <CAA4WUYgKnYhgvArS7FSWqRSf4MfhRbymCiGOC3E21E6R32KWCQ@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Tue, 07 May 2013 21:31:59 -0700
Message-ID: <CABP7Rbe+N+JEesvsV4EeQnc-7YSyiUmp2_46cD7znAA9OcNTZQ@mail.gmail.com>
To: "William Chan (陈智昌)" <willchan@chromium.org>
Cc: Martin Thomson <martin.thomson@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=209.85.219.43; envelope-from=jasnell@gmail.com; helo=mail-oa0-f43.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.667, 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: maggie.w3.org 1UZw3Z-0001WL-6r bdf79fb73d33ff95d0d7c937153f92ae
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Design Issue: Frame Size Items
Archived-At: <http://www.w3.org/mid/CABP7Rbe+N+JEesvsV4EeQnc-7YSyiUmp2_46cD7znAA9OcNTZQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17887
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>

Reading back over that thread, it seems to me that the overall
majority opinion was in favor of a smaller default max thread size
(let's just say 8192 + 8 byte header).

Proposal: Let's define that 8192+8 is the default MAX_FRAME size. If
an endpoint wishes to allow for frames larger or smaller than that, up
to ((s^16)-1)+8 total, then they can specify a SETTINGS_MAX_FRAME_SIZE
in the SETTINGS frame.

Yes, I know this proposal won't please everyone, but at some point we
need to put a stake in the ground on it. 8192+8 seems like a
reasonable enough of a default.

On Tue, May 7, 2013 at 2:17 PM, William Chan (陈智昌)
<willchan@chromium.org> wrote:
> On Tue, May 7, 2013 at 5:58 PM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>>
>> On 7 May 2013 12:41, William Chan (陈智昌) <willchan@chromium.org> wrote:
>> > I need to re-read the framing continuation thread
>> > (http://lists.w3.org/Archives/Public/ietf-http-wg/2013JanMar/0600.html),
>> > but
>> > I thought all this was addressed by that (8192 max frames, with frame
>> > continuation bit). I see that the spec does not mention frame
>> > continuations,
>> > so maybe we just have to write the text, or perhaps the thread reached a
>> > different conclusion than I remember.
>>
>> That discussion never really concluded.
>
>
> OK, I think we should conclude that thread :) I believe that resolving that
> thread will resolve this issue.
>
>>
>>
>> What we have is MUST support 8192, but no upper limit (other than the
>> hard 65535 byte limit imposed by the frame length field size).
>>
>> You might infer from this that 8192 is the only safe upper limit,
>> especially for frames containing headers.  Other frames might trigger
>> RST_STREAM, but at least you don't lose the session.
>
>
> Yep, I indeed did infer that, since we don't (at least, that I know of) have
> a safe mechanism for not processing frames that affect session state.