SETTINGS_PRIORITY_SCHEME | Re: Setting to disable HTTP/2 Priorities

Kari Hurtta <hurtta-ietf@elmme-mailer.org> Tue, 30 July 2019 15:51 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 72E63120187 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2019 08:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level:
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, TRACKER_ID=0.1] 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 8xGmi83gxbIX for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2019 08:51:31 -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 A3C9D1201B4 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 30 Jul 2019 08:51:19 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hsUMg-0006lT-WD for ietf-http-wg-dist@listhub.w3.org; Tue, 30 Jul 2019 15:48:39 +0000
Resent-Date: Tue, 30 Jul 2019 15:48:38 +0000
Resent-Message-Id: <E1hsUMg-0006lT-WD@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 1hsUMc-0006kI-Ud for ietf-http-wg@listhub.w3.org; Tue, 30 Jul 2019 15:48:34 +0000
Received: from welho-filter1.welho.com ([83.102.41.23]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <khurtta@welho.com>) id 1hsUMb-0008Iq-8I for ietf-http-wg@w3.org; Tue, 30 Jul 2019 15:48:34 +0000
Received: from localhost (localhost [127.0.0.1]) by welho-filter1.welho.com (Postfix) with ESMTP id BBE3412178; Tue, 30 Jul 2019 18:48:09 +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-filter1.welho.com [::ffff:83.102.41.23]) (amavisd-new, port 10024) with ESMTP id nTxFsWaCgl_d; Tue, 30 Jul 2019 18:48:09 +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 D14D328C; Tue, 30 Jul 2019 18:48:02 +0300 (EEST)
In-Reply-To: <20190725191746.GB12596@ubuntu-dmitri>
References: <20190725191746.GB12596@ubuntu-dmitri>
To: HTTP Working Group <ietf-http-wg@w3.org>
Date: Tue, 30 Jul 2019 18:48:01 +0300 (EEST)
From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
CC: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Brad Lassey <lassey@chromium.org>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>
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: <20190730154809.BBE3412178@welho-filter1.welho.com>
Received-SPF: none client-ip=83.102.41.23; envelope-from=khurtta@welho.com; helo=welho-filter1.welho.com
X-W3C-Hub-Spam-Status: No, score=-4.4
X-W3C-Hub-Spam-Report: AWL=0.858, BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001, TRACKER_ID=0.1, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1hsUMb-0008Iq-8I f388de81f5018611354e63eb1b5c054a
X-Original-To: ietf-http-wg@w3.org
Subject: SETTINGS_PRIORITY_SCHEME | Re: Setting to disable HTTP/2 Priorities
Archived-At: <https://www.w3.org/mid/20190730154809.BBE3412178@welho-filter1.welho.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36877
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>

> From the draft:
> 
> " 3.  The SETTINGS_ENABLE_HTTP2_PRIORITIES SETTINGS Parameter
> " 
> "    This document adds a new SETTINGS parameter to those defined by
> "    [RFC7540], Section 6.5.2.
> " 
> "    The new parameter name is SETTINGS_ENABLE_HTTP2_PRIORITIES.
> 
> Including "HTTP2" in the name is superfluous:  Since this is an
> HTTP/2 setting, it deals with HTTP/2 priorities.
> 
> Or was "HTTP2" added to the name to differentiate it from possible
> future priority mechanisms?  In that case, I suggest s/HTTP2/RFC7540/
>
>  - Dmitri.

Why boolean ("ENABLE") ?

I suggests SETTINGS Parameter

SETTINGS_PRIORITY_SCHEME

with values

 • 0             Sender of SETTINGS frame indicates that
                 it does not process or send priority 
                 values

 • 1             Sender of SETTINGS frame indicates that
                 it process or send RFC7540 priorities

 • unknown value (for recipient of SETTINGS frame)

                 Sender of SETTINGS frame indicates that
                 it is willing process some priority information  
                 or that it sends some priority information
                 (but recipient of SETTINGS frame does
                  not recognize these priorities)


Default value for SETTINGS_PRIORITY_SCHEME is 1
( RFC7540 priorities aka current HTTP/2 tree priorities).

Peer of HTTP/2 connection should send SETTINGS frame
with SETTINGS_PRIORITY_SCHEME once

Peer of HTTP/2 connection may send second SETTINGS frame
with SETTINGS_PRIORITY_SCHEME if it's value is same
than which it is received for peer on SETTINGS frame.


That is:
    Suggest SETTINGS_PRIORITY_SCHEME once
    and send SETTINGS_PRIORITY_SCHEME second time
    after that when you agreed with peer.


That makes SETTINGS_PRIORITY_SCHEME switch to
new priority scheme (when that is defined).

/ Kari Hurtta