reserved bit from Flags field | Re: new type number versus repurpose of existing field | … | Re: Setting to disable HTTP/2 Priorities
Kari Hurtta <hurtta-ietf@elmme-mailer.org> Fri, 09 August 2019 05:30 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 87F1F1200A3 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 8 Aug 2019 22:30:28 -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 ZAhoSNr-Qmas for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 8 Aug 2019 22:30:27 -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 20214120094 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 8 Aug 2019 22:30:26 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hvxR5-0001yz-2G for ietf-http-wg-dist@listhub.w3.org; Fri, 09 Aug 2019 05:27:31 +0000
Resent-Date: Fri, 09 Aug 2019 05:27:31 +0000
Resent-Message-Id: <E1hvxR5-0001yz-2G@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 1hvxR0-0001yE-FH for ietf-http-wg@listhub.w3.org; Fri, 09 Aug 2019 05:27:26 +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 1hvxQy-0004gi-CH for ietf-http-wg@w3.org; Fri, 09 Aug 2019 05:27:26 +0000
Received: from localhost (localhost [127.0.0.1]) by welho-filter1.welho.com (Postfix) with ESMTP id 1C4A4157CD; Fri, 9 Aug 2019 08:27:01 +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 CPHdcHBjYxez; Fri, 9 Aug 2019 08:27:00 +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 B8E7172; Fri, 9 Aug 2019 08:26:50 +0300 (EEST)
In-Reply-To: <20190808173909.F07B645B6B@welho-filter4.welho.com>
References: <20190808173909.F07B645B6B@welho-filter4.welho.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Date: Fri, 09 Aug 2019 08:26:49 +0300
From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
CC: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, Matthew Kerwin <matthew@kerwin.net.au>, HTTP Working Group <ietf-http-wg@w3.org>, Lucas Pardue <lucaspardue.24.7@gmail.com>, Brad Lassey <lassey@chromium.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.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: <20190809052701.1C4A4157CD@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.987, 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, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1hvxQy-0004gi-CH 3a7d016566cbe2ebf4fcd41aff938436
X-Original-To: ietf-http-wg@w3.org
Subject: reserved bit from Flags field | Re: new type number versus repurpose of existing field | … | Re: Setting to disable HTTP/2 Priorities
Archived-At: <https://www.w3.org/mid/20190809052701.1C4A4157CD@welho-filter1.welho.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36963
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>
> < ⋯ > > > > In Montreal we also discussed a possible experiment where the H2 PRIORITY > > > frame contents would be repurposed, which requires a compatible server to > > > read it correctly. In this case the signal would be more like "will send in > > > an RFC7540-incompatible format". > > Yes, it makes sense to allocate new type number for PRIORITY when frame > content is repurposed. > > Also is make sense to allocate new type number for HEADERS when > "Stream Dependency" or "Weight" field of HEADERS frame conrent is repurposed. > > That avaind dance about on what point on time change of "Stream Dependency" / "Weight" field" > field happens. Then there is also third possibility: Invent new field for new stype priority information (say "PRIORITY2"). Indicate presense of PRIORITY2 field with (currently) reserved bit from Flags field (which is on part 9-octet header of all frames). There is unused flags bit available for both HEADERS and PRIORITY frame. And fourth possibility is indicate repurpose of current "Stream Dependency" / "Weight" field" with (currently) reserved bit from Flags field. These possibilities also avoid dance on what point on time change of "Stream Dependency" / "Weight" field" field happens. / Kari Hurtta
- Setting to disable HTTP/2 Priorities Brad Lassey
- Re: Setting to disable HTTP/2 Priorities Dmitri Tikhonov
- Re: Setting to disable HTTP/2 Priorities Lucas Pardue
- Re: Setting to disable HTTP/2 Priorities Brad Lassey
- Re: Setting to disable HTTP/2 Priorities Willy Tarreau
- Re: Setting to disable HTTP/2 Priorities Lucas Pardue
- Re: Setting to disable HTTP/2 Priorities Willy Tarreau
- RE: Setting to disable HTTP/2 Priorities Mike Bishop
- Re: Setting to disable HTTP/2 Priorities Kazuho Oku
- Re: Setting to disable HTTP/2 Priorities Willy Tarreau
- RE: Setting to disable HTTP/2 Priorities Mike Bishop
- SETTINGS_PRIORITY_SCHEME | Re: Setting to disable… Kari Hurtta
- Re: SETTINGS_PRIORITY_SCHEME | Re: Setting to dis… Lucas Pardue
- Re: SETTINGS_PRIORITY_SCHEME | Re: Setting to dis… Matthew Kerwin
- Re: Setting to disable HTTP/2 Priorities Willy Tarreau
- Re: SETTINGS_PRIORITY_SCHEME | Re: Setting to dis… Lucas Pardue
- ENABLE ⇒ PROVIDE | Re: SETTINGS_PRIORITY_SCHEME |… Kari Hurtta
- SETTINGS_HTTP3_PRIORITY_MASK? | Re: SETTINGS_PRIO… Kari Hurtta
- Re: ENABLE ⇒ PROVIDE | Re: SETTINGS_PRIORITY_SCHE… Lucas Pardue
- SETTINGS_ENABLE_HTTP2_PRIORITIES default value | … Kari Hurtta
- Re: SETTINGS_ENABLE_HTTP2_PRIORITIES default valu… Lucas Pardue
- Re: SETTINGS_HTTP3_PRIORITY_MASK? | Re: SETTINGS_… Lucas Pardue
- Re: ENABLE ⇒ PROVIDE | Re: SETTINGS_PRIORITY_SCHE… Matthew Kerwin
- Re: SETTINGS_PRIORITY_SCHEME | Re: Setting to dis… Matthew Kerwin
- Re: ENABLE ⇒ PROVIDE | Re: SETTINGS_PRIORITY_SCHE… Kari Hurtta
- HTTP/2 (RFC7540) tree priorities exit (opt out) |… Kari Hurtta
- Re: SETTINGS_ENABLE_HTTP2_PRIORITIES default valu… Willy Tarreau
- Re: SETTINGS_ENABLE_HTTP2_PRIORITIES default valu… Willy Tarreau
- [resend] SETTINGS_HTTP2_PRIORITY_MODEL (or SETTIN… Kari Hurtta
- Re: [resend] SETTINGS_HTTP2_PRIORITY_MODEL (or SE… Willy Tarreau
- Repurpose of priority | Re: SETTINGS_PRIORITY_SCH… Kari Hurtta
- Re: Repurpose of priority | Re: SETTINGS_PRIORITY… Lucas Pardue
- Repurpose of protocol elements | Re: Repurpose of… Kari Hurtta
- Re: Repurpose of protocol elements | Re: Repurpos… Lucas Pardue
- new type number versus repurpose of existing fiel… Kari Hurtta
- Re: new type number versus repurpose of existing … Lucas Pardue
- Re: new type number versus repurpose of existing … Matthew Kerwin
- Re: new type number versus repurpose of existing … Lucas Pardue
- reserved bit from Flags field | Re: new type numb… Kari Hurtta
- Re: reserved bit from Flags field | Re: new type … Lucas Pardue
- Re: reserved bit from Flags field | Re: new type … Kari Hurtta
- Re: reserved bit from Flags field | … | Re: Setti… Kari Hurtta
- Re: reserved bit from Flags field | … | Re: Setti… Lucas Pardue
- RE: Repurpose of protocol elements | Re: Repurpos… Mike Bishop
- Re: Repurpose of protocol elements | Re: Repurpos… Lucas Pardue