ENABLE ⇒ PROVIDE | Re: SETTINGS_PRIORITY_SCHEME | Re: Setting to disable HTTP/2 Priorities

Kari Hurtta <hurtta-ietf@elmme-mailer.org> Wed, 31 July 2019 18:04 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@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 3C421120225 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 31 Jul 2019 11:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.652
X-Spam-Level:
X-Spam-Status: No, score=-2.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lfQjllxichsK for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 31 Jul 2019 11:04:50 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2864E12017C for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 31 Jul 2019 11:04:49 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hssvI-0007EL-5z for ietf-http-wg-dist@listhub.w3.org; Wed, 31 Jul 2019 18:02:00 +0000
Resent-Date: Wed, 31 Jul 2019 18:02:00 +0000
Resent-Message-Id: <E1hssvI-0007EL-5z@frink.w3.org>
Received: from mimas.w3.org ([2603:400a:ffff:804:801e:34:0:4f]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <khurtta@welho.com>) id 1hssvE-0007DU-8U for ietf-http-wg@listhub.w3.org; Wed, 31 Jul 2019 18:01:56 +0000
Received: from welho-filter2.welho.com ([83.102.41.24]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <khurtta@welho.com>) id 1hssvC-0000m6-EX for ietf-http-wg@w3.org; Wed, 31 Jul 2019 18:01:56 +0000
Received: from localhost (localhost [127.0.0.1]) by welho-filter2.welho.com (Postfix) with ESMTP id D385BC3F0A; Wed, 31 Jul 2019 21:01:08 +0300 (EEST)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp2.welho.com ([IPv6:::ffff:83.102.41.85]) by localhost (welho-filter2.welho.com [::ffff:83.102.41.24]) (amavisd-new, port 10024) with ESMTP id Xljkv84AoZnx; Wed, 31 Jul 2019 21:01:08 +0300 (EEST)
Received: from kasvihuone.keh.iki.fi (89-27-39-95.bb.dnainternet.fi [89.27.39.95]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by welho-smtp2.welho.com (Postfix) with ESMTPS id 1662A72; Wed, 31 Jul 2019 21:00:56 +0300 (EEST)
In-Reply-To: <CACweHNDChKtVBTzQGctxAFdgZydrOKt8a9oAKrYbbq1JKLFPNg@mail.gmail.com>
References: <20190725191746.GB12596@ubuntu-dmitri> <20190730154809.BBE3412178@welho-filter1.welho.com> <CALGR9oZnKo1JXnxLiKp+04kJeT5Uek3BiCPq=XSq4dG4B3AUBA@mail.gmail.com> <CACweHNDChKtVBTzQGctxAFdgZydrOKt8a9oAKrYbbq1JKLFPNg@mail.gmail.com>
To: Matthew Kerwin <matthew@kerwin.net.au>, HTTP Working Group <ietf-http-wg@w3.org>
Date: Wed, 31 Jul 2019 21:00:56 +0300 (EEST)
From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
CC: Lucas Pardue <lucaspardue.24.7@gmail.com>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>, HTTP Working Group <ietf-http-wg@w3.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Brad Lassey <lassey@chromium.org>, Kari Hurtta <khurtta@welho.com>
X-Mailer: ELM [version ME+ 2.5 PLalpha50a]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190731180108.D385BC3F0A@welho-filter2.welho.com>
Received-SPF: none client-ip=83.102.41.24; envelope-from=khurtta@welho.com; helo=welho-filter2.welho.com
X-W3C-Hub-Spam-Status: No, score=-4.5
X-W3C-Hub-Spam-Report: AWL=0.932, BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.201, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1hssvC-0000m6-EX 6f7f8d7d8e2fe9833977d286494d5619
X-Original-To: ietf-http-wg@w3.org
Subject: ENABLE =?UTF-8?Q?=E2=87=92_PROVIDE_=7C_Re:_SETTINGS=5FPRIORITY=5FSCHEME_=7C_Re:?= =?UTF-8?Q?_Setting?= to disable HTTP/2 Priorities
Archived-At: <https://www.w3.org/mid/20190731180108.D385BC3F0A@welho-filter2.welho.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36884
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: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

> On Wed., 31 Jul. 2019, 02:56 Lucas Pardue, <lucaspardue.24.7@gmail.com>;
> wrote:
> 
> > Hi Kari,
> >
> > On Tue, Jul 30, 2019 at 4:52 PM Kari Hurtta <hurtta-ietf@elmme-mailer.org>;
> > wrote:
> >
> >> Why boolean ("ENABLE") ?
> >
> >

> 
> At the risk of bike-shedding, I think calling it "enable" is a bit of an
> issue. The setting, as an advertisement of the sender's capability, should
> say something like "will ignore" (for disabling 7540 priorities) or "can
> understand" (for enabling some other scheme).
> 
> Unless we also feel the need to advertise "will not send"?
> 
> Cheers
> -- 
> Matthew Kerwin

Yes,


SETTINGS_ENABLE_* typically changes how HTTP/2 connection is
prosessed or allows some usages which otherwise produce
protocol error (example: SETTINGS_ENABLE_CONNECT_PROTOCOL).

Therefore these these typically allows only 0 ⇒ 1 transitions.
Feature which is enabled, is not allowed to be turned off because
it may effect handling of frames which are already sent by
other peer.

Therefore I think that

    SETTINGS_PROVIDE_HTTP2_PRIORITIES

is better name than

    SETTINGS_ENABLE_HTTP2_PRIORITIES


In other words this does not chahneg parsing of HTTP/2
frames. Even when this is set to 0, sending priorities
does not cause protocol error.

In SETTINGS_PROVIDE_HTTP2_PRIORITIES server asks
client to provide (or not provide) http/2 tree 
priorities.


( Another possible name is

  SETTINGS_PROVIDE_TREE_PRIORITIES

)

/ Kari Hurtta