Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits

William Chan (陈智昌) <willchan@chromium.org> Sat, 04 May 2013 02:05 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 2BBBE21F8F02 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 May 2013 19:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.906
X-Spam-Level:
X-Spam-Status: No, score=-8.906 tagged_above=-999 required=5 tests=[AWL=0.770, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 w79TpfiHhMe1 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 3 May 2013 19:05:17 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF7021F8FA5 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 3 May 2013 19:05:17 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UYRqC-0000ZL-Ei for ietf-http-wg-dist@listhub.w3.org; Sat, 04 May 2013 02:04:48 +0000
Resent-Date: Sat, 04 May 2013 02:04:48 +0000
Resent-Message-Id: <E1UYRqC-0000ZL-Ei@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <willchan@google.com>) id 1UYRq2-0000YW-CP for ietf-http-wg@listhub.w3.org; Sat, 04 May 2013 02:04:38 +0000
Received: from mail-qc0-f169.google.com ([209.85.216.169]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <willchan@google.com>) id 1UYRq1-0002au-Jd for ietf-http-wg@w3.org; Sat, 04 May 2013 02:04:38 +0000
Received: by mail-qc0-f169.google.com with SMTP id p9so1007907qca.28 for <ietf-http-wg@w3.org>; Fri, 03 May 2013 19:04:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=o8xQDRlRcdjmGJMdPhk9ujzc8XTevCp3gT8JPXwCjVM=; b=cJY9Ugd1uOyG09IgXYQ202oA37j72wxvldEuJZWl/Ato/WPx6f5oOFpqosf2HnY0yR IGwhtZ4CPXUpVwoscZkqFcwgl1rqxFKy2Muvukt+XtDxI7BcjoIiQKQ+f7X2/NhlSpTC QJHwCfXpj6vqQKgLIW+rZuXnA79QTwd2Le2WHuWgVlZcRQyc7YFjozHh0HXCEA/7rQbV niwF4hISX5/7kweWZHGzFaO/zR9actZAlutQAnD532loxDY8rOqQRraFVIunipYoy8y6 vpViI6aX66SkIy2/NtRRDgiSQqqPb+TY+guUzZhxJIgtn5Cl/paqIAliCDrtUQbPouqU lgOA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=o8xQDRlRcdjmGJMdPhk9ujzc8XTevCp3gT8JPXwCjVM=; b=FWNcoEh2GmOHP1gYMDNuOeJa/NUo8U2stQ04eIc06FbPdNB03HfhzKMUXQQsifpV1y Efk4Bxpi4HqQJB00h0vWjKjcE0x0ezZECDL/LArnCvAu+cG/YaFxe05FxYWjuuHN7a7t hz2xJYUMtrd23QlnTz+eEh0wsrUP0fBmfNQSU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=o8xQDRlRcdjmGJMdPhk9ujzc8XTevCp3gT8JPXwCjVM=; b=ktJjCygy1e5EKW5EOkoN3LGzfonJqMAXmw8WhgqMLjEXWN1g6sDUF4pOXRp4+qpR54 ZpWMeTHlkaKu3k83CFr/6YIDOHNNAvtqq4sNELhYLHX4IuBZzvCJSZy3sRPL9dsnXRTh rZG/TNNaeqcznpLo2zdv8wstStNnkROqamCm+lMrK00FhxRTV3lsHFmM8GZPBzmxgR0a O9PYeZ77CwvysULvAW+K0ili3XTI5uE144n/rAZd4ErFd2ujXTHiccoKlmLL5jjdPPlf F3w9GYhAuA7wl223o8E/OeWfmoyIWdP7rYKHSWyak4D7DZGrUio0vuLQMgKJjTpy6CJo 4+gg==
MIME-Version: 1.0
X-Received: by 10.224.79.138 with SMTP id p10mr10191282qak.13.1367633051473; Fri, 03 May 2013 19:04:11 -0700 (PDT)
Sender: willchan@google.com
Received: by 10.229.180.4 with HTTP; Fri, 3 May 2013 19:04:11 -0700 (PDT)
In-Reply-To: <CAP+FsNe8N33yJAthsHv_J8wU8WUESoGtcRkembCCJ8kQnNdRig@mail.gmail.com>
References: <CAA4WUYjnMupHPL8i13qzNTYr4dDjc_-ygZABaM1C6c8zUuMGJQ@mail.gmail.com> <CABP7RbfxGehBXw+114wyaKJaTQV1rLqCiZXq6KERWbO_HRRpBg@mail.gmail.com> <CAA4WUYg_zRcyU1Qju+MA_4YT3FJB4PVAWi+iVkqi=9uvAo84YA@mail.gmail.com> <CABP7RbdCWOQZRSmqTtc_X7qKnRi=vRBpQDH3PaZE42ZQbg--Jw@mail.gmail.com> <CAP+FsNesYysCpM60bEWBWk2_BzHpBtRUahck2K91TPX979GT1Q@mail.gmail.com> <CABkgnnW50TEaDoieOa3t3fSK7mCPECNzyZTSyQYD2ZqQKuznHA@mail.gmail.com> <CAP+FsNe8N33yJAthsHv_J8wU8WUESoGtcRkembCCJ8kQnNdRig@mail.gmail.com>
Date: Fri, 3 May 2013 23:04:11 -0300
X-Google-Sender-Auth: 2MvPV4zNnRh0BwoTuQ7FsIiAvu8
Message-ID: <CAA4WUYicCQJUduw4i0G8MVpado_-m6b=jxcT=3f50d0rsTLFQQ@mail.gmail.com>
From: =?UTF-8?B?V2lsbGlhbSBDaGFuICjpmYjmmbrmmIwp?= <willchan@chromium.org>
To: Roberto Peon <grmocg@gmail.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, James M Snell <jasnell@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary=047d7bf0de8837a97304dbdae234
X-Gm-Message-State: ALoCoQmCvaIpsdsaGIxA+A5neQ5RFlI/rpfYmWWoQa5z422mrkmLKXRGglxlnhLR7mR46Z8kX4UhnAx1kzH8cmJ5fDiLRr4e7i8uFpMGB5PJNVbtnecWglXj0KbGtkdIHRWDjw9bIgQfvjk03oFAv9zoqh0Zy3MNJMjc7H1TtdS9P2+6tS5l7V+HvljcCRLBCK/GZFAMPm/v
Received-SPF: pass client-ip=209.85.216.169; envelope-from=willchan@google.com; helo=mail-qc0-f169.google.com
X-W3C-Hub-Spam-Status: No, score=-4.8
X-W3C-Hub-Spam-Report: AWL=-1.376, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.581, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1UYRq1-0002au-Jd a74e685db3e04171f621119315e1fd07
X-Original-To: ietf-http-wg@w3.org
Subject: Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits
Archived-At: <http://www.w3.org/mid/CAA4WUYicCQJUduw4i0G8MVpado_-m6b=jxcT=3f50d0rsTLFQQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17832
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>

It sounds like I misremembered the spec. Sorry folks :) Sounds like any
change here is blocked on issue #40.


On Fri, May 3, 2013 at 10:55 PM, Roberto Peon <grmocg@gmail.com>; wrote:

> Yup, the language in the specs is the same as what is currently in the
> HTTP/2 spec, but people have been interpreting them differently (or at
> least I assume so).
>
>    - 4 - SETTINGS_MAX_CONCURRENT_STREAMS allows the sender to inform the
>    remote endpoint the maximum number of concurrent streams which it will
>    allow. By default there is no limit. For implementors it is recommended
>    that this value be no smaller than 100.
>
> is the thing in question, and most implementations that I know of default
> to 100, which makes sense given that "no limit" and "unlimited" are not
> always the same.
> -=R
>
>
> On Fri, May 3, 2013 at 3:46 PM, Martin Thomson <martin.thomson@gmail.com>wrote:
>
>> On 3 May 2013 14:22, Roberto Peon <grmocg@gmail.com>; wrote:
>> > This does differ from SPDY,
>>
>> This doesn't differ from the SPDY we were given.
>>
>> > but (still) seems reasonable given the number of
>> > streams created in the initial RTT shouldn't be unbounded anyway.
>> > Assuming we have persisted settings (which is in doubt, I guess), this
>> would
>> > only be a problem for the first RTT in a session where we didn't have
>> the
>> > persisted setting.
>>
>> I think that this default is under contention still:
>> https://github.com/http2/http2-spec/issues/40
>>
>> We may ultimately determine that some value between 0 (what #40
>> proposes) and infinity (status quo) is more appropriate.
>>
>
>