SETTINGS_ENABLE_HTTP2_PRIORITIES default value | Re: Setting to disable HTTP/2 Priorities

Kari Hurtta <hurtta-ietf@elmme-mailer.org> Wed, 31 July 2019 19:13 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 D943D12004F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 31 Jul 2019 12:13:36 -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 ZRmCpKu__MwC for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 31 Jul 2019 12:13:34 -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 51FA712006D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 31 Jul 2019 12:13:34 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hsu0P-0005j5-1K for ietf-http-wg-dist@listhub.w3.org; Wed, 31 Jul 2019 19:11:21 +0000
Resent-Date: Wed, 31 Jul 2019 19:11:21 +0000
Resent-Message-Id: <E1hsu0P-0005j5-1K@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 1hsu0M-0005iK-CN for ietf-http-wg@listhub.w3.org; Wed, 31 Jul 2019 19:11:18 +0000
Received: from welho-filter1.welho.com ([83.102.41.23]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <khurtta@welho.com>) id 1hsu0K-0005yv-88 for ietf-http-wg@w3.org; Wed, 31 Jul 2019 19:11:18 +0000
Received: from localhost (localhost [127.0.0.1]) by welho-filter1.welho.com (Postfix) with ESMTP id 1E66014197; Wed, 31 Jul 2019 22:10:53 +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 H_LfT8Gp6ylt; Wed, 31 Jul 2019 22:10:52 +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 EE27972; Wed, 31 Jul 2019 22:10:44 +0300 (EEST)
In-Reply-To: <CALGR9oZ7CyJ3LD4rmJn+4=E83ad3qc93Nc82-uJMXjiRL+NQjA@mail.gmail.com>
References: <CALGR9oZ7CyJ3LD4rmJn+4=E83ad3qc93Nc82-uJMXjiRL+NQjA@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Date: Wed, 31 Jul 2019 22:10:44 +0300 (EEST)
From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
CC: Lucas Pardue <lucaspardue.24.7@gmail.com>, Willy Tarreau <w@1wt.eu>, 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: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20190731191053.1E66014197@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.5
X-W3C-Hub-Spam-Report: AWL=0.892, 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 1hsu0K-0005yv-88 b8930d5601536d4a0448c239fc6ca09e
X-Original-To: ietf-http-wg@w3.org
Subject: SETTINGS_ENABLE_HTTP2_PRIORITIES default value | Re: Setting to disable HTTP/2 Priorities
Archived-At: <https://www.w3.org/mid/20190731191053.1E66014197@welho-filter1.welho.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36886
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>

> The aim is to maintain todays default behavior of endpoints supporting H2.
> This is achieved by defining the initial value of the setting as 1;
> endpoints "opt out" by sending 0.
> 
>Do you think we have mis-specced this compared to our aim?


There is  "If a client or server does not send the setting, the peer 
SHOULD NOT make any assumptions about its support for HTTP/2 priorities.".

https://datatracker.ietf.org/doc/draft-lassey-priority-setting/?include_text=1

------------
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.  The
   value of the parameter MUST be 0 or 1 to indicate not supporting or
   supporting HTTP/2 priorities respectively.  If either side sends the
   parameter with a value of 0, clients SHOULD NOT send priority frames
   and servers SHOULD NOT make any assumptions based on the presence or
   lack thereof of priority frames.  If both sides send the parameter
   with a value of 1, then both parties MAY use HTTP/2 priorities as
   they see fit.  A sender MUST NOT send the parameter with the value of
   0 after previously sending a value of 1.  If a client or server does
   not send the setting, the peer SHOULD NOT make any assumptions about
   its support for HTTP/2 priorities.
-------------

This section indicates that default value is undefined, because it says
that if SETTINGS_ENABLE_HTTP2_PRIORITIES is not seen, the peer SHOULD NOT 
make any assumptions about other ends support for HTTP/2 priorities.

-------------
4.1.  A New HTTP/2 Setting

   This document registers an entry in the "HTTP/2 Settings" registry
   that was established by Section 11.3 of [RFC7540].

   Name: SETTINGS_ENABLE_HTTP2_PRIORITIES

   Code: 0xTBD

   Initial Value: 1

   Specification: This document
--------------

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