Re: http/2 flow control

Mike Belshe <mike@belshe.com> Mon, 28 January 2013 05:44 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 A341E21F8445 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 27 Jan 2013 21:44:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.676
X-Spam-Level:
X-Spam-Status: No, score=-9.676 tagged_above=-999 required=5 tests=[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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sA0Dgmoh4shv for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 27 Jan 2013 21:44:21 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id F1A7021F8830 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 27 Jan 2013 21:44:20 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1TzhUD-0006fR-LY for ietf-http-wg-dist@listhub.w3.org; Mon, 28 Jan 2013 05:42:29 +0000
Resent-Date: Mon, 28 Jan 2013 05:42:29 +0000
Resent-Message-Id: <E1TzhUD-0006fR-LY@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <mike@belshe.com>) id 1TzhU6-0006eP-De for ietf-http-wg@listhub.w3.org; Mon, 28 Jan 2013 05:42:22 +0000
Received: from mail-bk0-f47.google.com ([209.85.214.47]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <mike@belshe.com>) id 1TzhU3-0006yX-Le for ietf-http-wg@w3.org; Mon, 28 Jan 2013 05:42:22 +0000
Received: by mail-bk0-f47.google.com with SMTP id jc3so1100857bkc.34 for <ietf-http-wg@w3.org>; Sun, 27 Jan 2013 21:41:53 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=HXiVyFyfNIXA1Mb7XgPaI8WGsYVdMC1bD1B4JqChLmE=; b=YGdMC9w9m1YtDx1aOefLgLST8WyZtNdSZj5UkSAyLRO0FWWk3xcxzhaDf/71ug8xSB oen8pFSQLu7rEzbIOAyUBWlM9c8tBEFsDl5hTwiyJjqcCaFipcA/DfsrCBsPqs3w9N5d Tz0D7mHJr/fSLfQQI5FAO5i3td2/DGFXRpRu6oD1lB3d4E75hp2+cS9VWqBQRyYtWJHJ I5PP/C0dBbi/Y18kZn6+9jPVOqzyYeJzyUz6U461ULKSSelWgfjnqjw68ap1rzTB1mVL 8ajrEwVFtN9SRGFMW5sW5WtG1UnV4b4xO6QzHPKB3i0qWobmSac1ZFehZJiBVaYB+h+6 TZRQ==
MIME-Version: 1.0
X-Received: by 10.205.124.146 with SMTP id go18mr3661979bkc.68.1359351712513; Sun, 27 Jan 2013 21:41:52 -0800 (PST)
Received: by 10.205.75.133 with HTTP; Sun, 27 Jan 2013 21:41:52 -0800 (PST)
In-Reply-To: <CAA4WUYgk-NPZ0bdYV3KysVED=OqFQ6Z0eE-7ePmmFdS2GMfjLA@mail.gmail.com>
References: <CAA4WUYgk-NPZ0bdYV3KysVED=OqFQ6Z0eE-7ePmmFdS2GMfjLA@mail.gmail.com>
Date: Mon, 28 Jan 2013 14:41:52 +0900
Message-ID: <CABaLYCv-K4A8AbtyjCc35H77pSjvTOVACcR6g9fpt0W3c3MAUA@mail.gmail.com>
From: Mike Belshe <mike@belshe.com>
To: "William Chan (陈智昌)" <willchan@chromium.org>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="000e0cdfc886f3006904d452bb9d"
X-Gm-Message-State: ALoCoQkSeiuBQXFdye7VHH+b5KTfr4YFy2lOtLcwflaQ9gFnnkZ0dKHFfPsEfLgdqSahUMmHPpBS
Received-SPF: none client-ip=209.85.214.47; envelope-from=mike@belshe.com; helo=mail-bk0-f47.google.com
X-W3C-Hub-Spam-Status: No, score=-2.6
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7
X-W3C-Scan-Sig: maggie.w3.org 1TzhU3-0006yX-Le aea695f6e024ecb9bf44569930d3b916
X-Original-To: ietf-http-wg@w3.org
Subject: Re: http/2 flow control
Archived-At: <http://www.w3.org/mid/CABaLYCv-K4A8AbtyjCc35H77pSjvTOVACcR6g9fpt0W3c3MAUA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16227
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>

Nice writeup, will.

I guess if you wanted to note one more thing, the (max streams * default
per stream window) is potentially a type of flow control too, depending on
values chosen.

Mike



On Fri, Jan 25, 2013 at 7:22 AM, William Chan (陈智昌)
<willchan@chromium.org>wrote:

> Given the long previous debates in flow control discussions on the
> spdy-dev@ mailing list
> (https://groups.google.com/d/topic/spdy-dev/JB_aQPNI7rw/discussion), I
> thought it would be useful to write up a summary of lots (but not all)
> of the discussions before we engage in the f2f interim meeting
> discussions. Here's my summary:
>
> https://docs.google.com/document/d/15LMnvVWSY-kF-ME4RZIFHN0FukViapjiefQMmQCnr14/pub
> .
>
> It discusses the reasoning behind per-stream flow control windows, as
> included in SPDY3 and in the current http2 draft. It discusses some
> problems with it, and also tradeoffs between relying on transport
> level flow control windows (TCP) and session level flow control
> windows.
>
> This document left out some other proposals to hopefully keep it simpler:
> * Receiver sending a xon/xoff frame to instruct the sender to
> resume/stop sending.
> * Stream group flow control windows.
>
> The latter is fairly advanced, and I think it is only pertinent if we
> agree there is a need for session level flow control windows, since
> stream group flow control windows subsume session level flow control
> windows (session == a single stream group containing all streams).
>
> One last thing on flow control. It's definitely possible, as Patrick
> demonstrates in
> http://bitsup.blogspot.com/2012/12/managing-bandwidth-priorities-in.html,
> to use flow control facilities to control prioritization. It's my hope
> that HTTP/2's prioritization facilities will suffice for that end, and
> thus we won't try to use receive windows to control prioritization.
>
> Cheers.
>
>