Re: HTTP/2.0 SETTINGS frame values

William Chan (陈智昌) <willchan@chromium.org> Mon, 03 June 2013 22:41 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 71FA521F909A for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 3 Jun 2013 15:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.176
X-Spam-Level:
X-Spam-Status: No, score=-6.176 tagged_above=-999 required=5 tests=[AWL=3.500, 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 Fp39usKFxHAX for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 3 Jun 2013 15:41:04 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 328CE11E8102 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 3 Jun 2013 15:37:03 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UjdL4-0008A5-Il for ietf-http-wg-dist@listhub.w3.org; Mon, 03 Jun 2013 22:34:54 +0000
Resent-Date: Mon, 03 Jun 2013 22:34:54 +0000
Resent-Message-Id: <E1UjdL4-0008A5-Il@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 1UjdKm-00088v-4x for ietf-http-wg@listhub.w3.org; Mon, 03 Jun 2013 22:34:36 +0000
Received: from mail-qe0-f51.google.com ([209.85.128.51]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <willchan@google.com>) id 1UjdKh-0001wb-Ds for ietf-http-wg@w3.org; Mon, 03 Jun 2013 22:34:36 +0000
Received: by mail-qe0-f51.google.com with SMTP id nd7so2795111qeb.10 for <ietf-http-wg@w3.org>; Mon, 03 Jun 2013 15:34:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=B/vw/ow0SDB3aQPZ+Lf2i6TcWJ/eWkv+0YK+eUAnIOA=; b=dfT4dNAT04xe0ZZ60hWqEYWbog/78v2K54QxXlcXvI97QDpkxWwjhm/VmIuohx2pij 2C7eX8n3lshHgw/WcWjaxROnMoGQ9gfi6nG/GMjf4VYRZhbyL7w4vGnq/z7JvC7MY8tF xgf5/abEbbit/9KiLWXgPw1VDnsF7Znf2Tkjz5W14PPmYQkbmdYEkoa9x0QnK/gYbDsV G7a8j2gNHwcF5x9O2b+ZwJ2Komn1YCnoU1PcpLbS2qi2XOPM3U18KQYefdmBXn7gkn9k 3f6ysX/k2n517/ruDa7OlA5c6s21OVxeO4yXaofJTBMxj7w5yn7B3SGzaFnjNpwrz87e uN8A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=B/vw/ow0SDB3aQPZ+Lf2i6TcWJ/eWkv+0YK+eUAnIOA=; b=eStwm/IxNyanbrG8hpoZKeKBQtg/KlqL4M8Z9RNJa7qVhXieVL4Kz3bzBoXBdzni4x MlTFk91ZQP12wrBLgx57eQlgUT/chKOZqobgrqnp1T6jayjmoLoCOczfj7lHkz6H0Jhl AzRn9yJ7Mx8DhCD+ZTxB8hR1oWICIRWO4u6/k=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=B/vw/ow0SDB3aQPZ+Lf2i6TcWJ/eWkv+0YK+eUAnIOA=; b=c1TLrrvwhVbsdCNXc4ZIpSXMMkYuZo0oYUyvc4/Sro4W7kde1ywiWuvLXuAJ73FOu8 bZGkGGfAR1JobPHPR++r2Yir04AS+Lmpwy78Gs6Ag3Z7vFFSBDwJnTz9HlHinT0IvQom crofqoXKgtcDoTEnbpgiEquTapsLj8FiFuPV2RjjMIzpxqRRrWvXBDiD4EkyFdhdbR9t vo50g9vLzyAvK82SmkCTgrMI7108Y3MoE7bI3d6TSJZgnIBZeAZJox3JpT2qCUBJrjBh RkFrf3LYeLr0c0IDUy/43IxsorGqsQ0GiHnD1AVndADh/m5EhB1ZMGkmVF1gk653ktN+ Px4g==
MIME-Version: 1.0
X-Received: by 10.49.71.203 with SMTP id x11mr24366088qeu.19.1370298845676; Mon, 03 Jun 2013 15:34:05 -0700 (PDT)
Sender: willchan@google.com
Received: by 10.229.62.133 with HTTP; Mon, 3 Jun 2013 15:34:05 -0700 (PDT)
In-Reply-To: <0F5D3725-8C49-41B8-B581-8F6AAD940DC6@mnot.net>
References: <A372C012-0840-4B0F-8F49-D735F6B1D342@ifi.uio.no> <B910C3C4-3566-430C-A82D-756E2DE7A855@ifi.uio.no> <0F5D3725-8C49-41B8-B581-8F6AAD940DC6@mnot.net>
Date: Mon, 03 Jun 2013 15:34:05 -0700
X-Google-Sender-Auth: 36_bUOR72x3AtPwFsqLWDDwBWTo
Message-ID: <CAA4WUYgkUwFbkLh+z1bH-YNag16txVLfMWn1Hyq1ftCZDQYg4Q@mail.gmail.com>
From: "William Chan (陈智昌)" <willchan@chromium.org>
To: Mark Nottingham <mnot@mnot.net>
Cc: Michael Welzl <michawe@ifi.uio.no>, HTTP Working Group <ietf-http-wg@w3.org>, iccrg@irtf.org
Content-Type: multipart/alternative; boundary="047d7b6dc474eefe9304de478f04"
X-Gm-Message-State: ALoCoQkjHdh1wHgMVurgGtb6+v6pY49EkFydZO2ieMYZMQaJ2hpSOcawZ8i138fyIMr23OipWkwjGVMP4gD5riaZyZXaxoN5/lyfgPSEUtToVilnMGgzF9m5VowUAUnZ+IyLAf97NHxiBquxjseOJI3hNklQd7FWNTIFQc+n9zHI/a/M0eRe2LzcAqt88TkdiHhL+aq3o4cZ
Received-SPF: pass client-ip=209.85.128.51; envelope-from=willchan@google.com; helo=mail-qe0-f51.google.com
X-W3C-Hub-Spam-Status: No, score=-4.7
X-W3C-Hub-Spam-Report: AWL=-1.530, BAYES_00=-1.9, 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=-0.511, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1UjdKh-0001wb-Ds 5e9fd47e2cb8ee1d037172ba0adf1503
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP/2.0 SETTINGS frame values
Archived-At: <http://www.w3.org/mid/CAA4WUYgkUwFbkLh+z1bH-YNag16txVLfMWn1Hyq1ftCZDQYg4Q@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18157
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>

Brian just filed a bunch of issues for these here. It's true, other than
the TCP_CWND setting, we are not using any of the rest in SPDY. I am
inclined to agree that we should remove all of them (mod the TCP_CWND
setting since we're actively experimenting here).

The main idea was to provide more information to the peer to allow it to
better decide how to optimize. For example, if you can calculate BDP for
the connection, then it may be possible to do better write scheduling so as
not to unnecessarily fill bloated buffers and cause HoL blocking. This is
fairly advanced and obviously has lots of weaknesses, but as with many
things, we stuck it into the SPDY spec so we could experiment. But we never
really pursued it, so I think unless anyone is actively interested in
pursuing experimentation here, it's fine to remove. If people decide later
to experiment, we can always bring it back or it can live in a separate
experimental spec.


On Tue, May 28, 2013 at 3:41 AM, Mark Nottingham <mnot@mnot.net> wrote:

> :)
>
> We're planning a joint session with Transport area folks in Berlin, to
> discuss things just like this; ICCRG folks are of course welcome to come
> along.
>
> Cheers,
>
>
> On 28/05/2013, at 7:31 PM, Michael Welzl <michawe@ifi.uio.no> wrote:
>
> > I can't believe that this keeps happening to me (being one of the chairs
> of ICCRG) - very sorry, everyone! Here's a fix, using the correct address
> for ICCRG!
> >
> > Cheers,
> > Michael
> >
> >
> > On 28. mai 2013, at 11:25, Michael Welzl wrote:
> >
> >> (including ICCRG because folks there might be interested)
> >>
> >> Hi,
> >>
> >> I just joined the list. While I did look at some old presentations from
> minutes and the list archive, I might have missed an answer to the question
> I'm asking - my apologies in this case!
> >>
> >> Here it goes: here,
> http://tools.ietf.org/html/draft-ietf-httpbis-http2-02#section-3.7.4
> >> various values are defined, like an estimate of the upload bandwidth,
> download bandwidth, the RTT, the initial window and so forth.
> >>
> >> I wonder, has it been discussed whether these things are useful and/or
> appropriate?
> >> I have only seen a thread related to SETTINGS_CURRENT_CWND, but what
> about all the other stuff (values 1, 2, 3, 4, 6, 7)? This smells like a
> feedback channel for app-layer congestion control, is this the plan  (of,
> ahem, the whole HTTPBIS group) ?    :-)
> >>
> >> Thanks, cheers,
> >> Michael
> >>
> >
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>
>