Re: HTTP/2.0 #19: Clarify that max-streams is per-direction [WAS: Outstanding Action Items]

Mark Nottingham <mnot@mnot.net> Mon, 18 February 2013 08:42 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 13FBB21F86E6 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 18 Feb 2013 00:42:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.261
X-Spam-Level:
X-Spam-Status: No, score=-9.261 tagged_above=-999 required=5 tests=[AWL=1.038, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bc9fcm2NioDJ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 18 Feb 2013 00:41:57 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 91D9121F86BA for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 18 Feb 2013 00:41:57 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1U7MGp-0005er-Bt for ietf-http-wg-dist@listhub.w3.org; Mon, 18 Feb 2013 08:40:19 +0000
Resent-Date: Mon, 18 Feb 2013 08:40:19 +0000
Resent-Message-Id: <E1U7MGp-0005er-Bt@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1U7MGc-0005a6-5j for ietf-http-wg@listhub.w3.org; Mon, 18 Feb 2013 08:40:06 +0000
Received: from mxout-08.mxes.net ([216.86.168.183]) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1U7MGb-0004Tn-FI for ietf-http-wg@w3.org; Mon, 18 Feb 2013 08:40:06 +0000
Received: from [192.168.1.80] (unknown [118.209.197.138]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1DD9B509B5; Mon, 18 Feb 2013 03:39:42 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAA4WUYi+R1GrZS3wc89-5=gLLW+7J8PWv+BzCQf7xPfKJw32NQ@mail.gmail.com>
Date: Mon, 18 Feb 2013 19:39:38 +1100
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <56DC54C0-BBF9-4AB9-8604-3E815A542CED@mnot.net>
References: <CAA4WUYi+R1GrZS3wc89-5=gLLW+7J8PWv+BzCQf7xPfKJw32NQ@mail.gmail.com>
To: "William Chan (陈智昌)" <willchan@chromium.org>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass client-ip=216.86.168.183; envelope-from=mnot@mnot.net; helo=mxout-08.mxes.net
X-W3C-Hub-Spam-Status: No, score=-3.3
X-W3C-Hub-Spam-Report: AWL=-3.343, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1U7MGb-0004Tn-FI 37afd24741369fe435e2ae34c292f459
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP/2.0 #19: Clarify that max-streams is per-direction [WAS: Outstanding Action Items]
Archived-At: <http://www.w3.org/mid/56DC54C0-BBF9-4AB9-8604-3E815A542CED@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16662
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>

WFM. If others have suggestions, please say; otherwise I'll put that in the ticket and mark for incorporation.


On 18/02/2013, at 2:30 PM, William Chan (陈智昌) <willchan@chromium.org> wrote:

> I'm not one to be very particular about wording, but just to get the ball rolling...
> 
> Proposed new text to clarify directionality:
> """
> 4 - SETTINGS_MAX_CONCURRENT_STREAMS indicates the maximum number of concurrent streams which the sender of the SETTINGS frame is willing to allow the peer to open. Note that this limit is directional. By default there is no limit.  For implementors it is recommended that this value be no smaller than 100, so as not to unnecessarily limit parallelism.
> """
> 
> Not that it matters, but here's my github commit:
> https://github.com/willchan/http2-spec/commit/2fc3db01fd32bd8f20d1f01b3091c513eb40bde6 (ignore the html stuff above, I guess the the html generation tool hasn't been run since the last changes to the XML).
> 
> On Sun, Feb 17, 2013 at 5:57 PM, Mark Nottingham <mnot@mnot.net> wrote:
> Thanks. I've opened this to track:
>   https://github.com/http2/http2-spec/issues/19
> 
> On 06/02/2013, at 2:44 PM, William Chan (陈智昌) <willchan@chromium.org> wrote:
> 
> > <snip>
> >
> >> * Will: double check that spdy's change to directionality for max streams has made it into http/2, or raise issue.
> >
> > """
> >
> > 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.
> > """
> >
> > It's the same text as we've had in SPDY/2, and our SPDY/4 draft is the
> > same. This wording is technically correct, but it does not
> > particularly emphasize that the limit is directional. I can imagine
> > first time readers misinterpreting it.
> >
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 
> 
> 

--
Mark Nottingham   http://www.mnot.net/