[resend] SETTINGS_HTTP2_PRIORITY_MODEL (or SETTINGS_PRIORITY_SCHEME again) | Re: SETTINGS_ENABLE_HTTP2_PRIORITIES default value | Re: Setting to disable HTTP/2 Priorities

Kari Hurtta <hurtta-ietf@elmme-mailer.org> Thu, 01 August 2019 05:12 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 026E3120026 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 31 Jul 2019 22:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.201, 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 cBzaYVnqPtav for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 31 Jul 2019 22:12:32 -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 1A14D12000F for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 31 Jul 2019 22:12:31 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ht3Lc-0008Ty-Tz for ietf-http-wg-dist@listhub.w3.org; Thu, 01 Aug 2019 05:09:52 +0000
Resent-Date: Thu, 01 Aug 2019 05:09:52 +0000
Resent-Message-Id: <E1ht3Lc-0008Ty-Tz@frink.w3.org>
Received: from titan.w3.org ([2603:400a:ffff:804:801e:34:0:4c]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <khurtta@welho.com>) id 1ht3La-0008ST-3h for ietf-http-wg@listhub.w3.org; Thu, 01 Aug 2019 05:09:50 +0000
Received: from welho-filter3.welho.com ([83.102.41.25]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <khurtta@welho.com>) id 1ht3LY-0006r1-41 for ietf-http-wg@w3.org; Thu, 01 Aug 2019 05:09:49 +0000
Received: from localhost (localhost [127.0.0.1]) by welho-filter3.welho.com (Postfix) with ESMTP id D5A4D2333; Thu, 1 Aug 2019 08:09:25 +0300 (EEST)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp1.welho.com ([IPv6:::ffff:83.102.41.84]) by localhost (welho-filter3.welho.com [::ffff:83.102.41.25]) (amavisd-new, port 10024) with ESMTP id EXiz9S-JJcAv; Thu, 1 Aug 2019 08:09:25 +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-smtp1.welho.com (Postfix) with ESMTPS id B23937A; Thu, 1 Aug 2019 08:09:16 +0300 (EEST)
In-Reply-To: <20190801044820.GA12279@1wt.eu>
References: <CALGR9oZ7CyJ3LD4rmJn+4=E83ad3qc93Nc82-uJMXjiRL+NQjA@mail.gmail.com> <20190731191053.1E66014197@welho-filter1.welho.com> <CALGR9oYddEX+GeA9yTXD+hH9ufdUC7qSpo2MW8-UcXUNqEgM-Q@mail.gmail.com> <20190801044108.GC11989@1wt.eu> <20190801044820.GA12279@1wt.eu>
To: Willy Tarreau <w@1wt.eu>, HTTP Working Group <ietf-http-wg@w3.org>
Date: Thu, 1 Aug 2019 08:09:16 +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>, Brad Lassey <lassey@chromium.org>
X-Mailer: ELM [version ME+ 2.5 PLalpha50a]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20190801050925.D5A4D2333@welho-filter3.welho.com>
Received-SPF: none client-ip=83.102.41.25; envelope-from=khurtta@welho.com; helo=welho-filter3.welho.com
X-W3C-Hub-Spam-Status: No, score=-4.6
X-W3C-Hub-Spam-Report: AWL=0.820, 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: titan.w3.org 1ht3LY-0006r1-41 d072ffde05e19903022599399fb74bad
X-Original-To: ietf-http-wg@w3.org
Subject: [resend] SETTINGS_HTTP2_PRIORITY_MODEL (or SETTINGS_PRIORITY_SCHEME again) | Re: SETTINGS_ENABLE_HTTP2_PRIORITIES default value | Re: Setting to disable HTTP/2 Priorities
Archived-At: <https://www.w3.org/mid/20190801050925.D5A4D2333@welho-filter3.welho.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36905
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, Jul 31, 2019 at 08:14:24PM +0100, Lucas Pardue wrote:
> > > If initial value for SETTINGS_ENABLE_HTTP2_PRIORITIES is really 1,
> > > then peer may assume that other ends supports HTTP/2 priorities
> > > until SETTINGS_ENABLE_HTTP2_PRIORITIES is seen.
> > >
> > > So there is inconsistence between chapters.
> > >
> > > / Kari Hurtta
> > >
> > 
> > Agreed. We should tighten this up for something that is practically
> > deployable and meets the needs of implementers. Ideally we can take
> > feedback so far and iterate through the design team process.
> 
> I think the confusing part comes from the ENABLE word in the setting
> name. We could proceed differently by exchanging a supported model
> for priorities :  SETTINGS_HTTP2_PRIORITY_MODEL
> It could then take the following values :
> 
>     0 (default) : as specified in RFC7540
>     1           : priorities not sent and silently ignored
>     2 and above : to be documented in future specifications
> 
> This way it seems more natural to consider that unless advertised, we
> stay on RFC7540 and nothing changes.
> 
> Willy

This is almost same than my SETTINGS_PRIORITY_SCHEME suggestion.

It have only 1 and 0 flipped.

https://lists.w3.org/Archives/Public/ietf-http-wg/2019JulSep/0140.html


Then incompatibility with HTTP/3's SETTINGS frame was cited.

https://lists.w3.org/Archives/Public/ietf-http-wg/2019JulSep/0141.html

/ Kari Hurtta