Re: SETTINGS_PRIORITY_SCHEME | Re: Setting to disable HTTP/2 Priorities

Matthew Kerwin <matthew@kerwin.net.au> Wed, 31 July 2019 23: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 8A5E21200FF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 31 Jul 2019 16:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.201, HTML_MESSAGE=0.001, 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 zNjTPDgDLOmy for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 31 Jul 2019 16:12: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 D79721200B5 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 31 Jul 2019 16:12: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 1hsxjf-0006tH-BO for ietf-http-wg-dist@listhub.w3.org; Wed, 31 Jul 2019 23:10:19 +0000
Resent-Date: Wed, 31 Jul 2019 23:10:19 +0000
Resent-Message-Id: <E1hsxjf-0006tH-BO@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 <phluid61@gmail.com>) id 1hsxjc-0006sW-NU for ietf-http-wg@listhub.w3.org; Wed, 31 Jul 2019 23:10:16 +0000
Received: from mail-io1-f54.google.com ([209.85.166.54]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <phluid61@gmail.com>) id 1hsxjZ-0005qM-Uv for ietf-http-wg@w3.org; Wed, 31 Jul 2019 23:10:16 +0000
Received: by mail-io1-f54.google.com with SMTP id f4so140120364ioh.6 for <ietf-http-wg@w3.org>; Wed, 31 Jul 2019 16:09:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kQYKdSXEBbJAqGde3gHqhedEBqY1GwnkxLScukwytI0=; b=YwUbFikEtNnbXN7ChRosheM/ixz1osEkNrQ6M6iGldZ5MRIKfDIBa+md6Uj9YpRayq 2527PQDS65gZsTglnQVstj4t4JAO3/NiQorxpmE9Mlb8kKjIrjncv/EFP0UcJ3X8yMz+ WqvMRryBrEUVfTa2YOztmGdqemGmUyR7l4+pc/Nej0EKBc5E8JXxDyDMdqhhPDDdSt3x mT511T91c+/Uqc+sxv1amW/NLrn4bIv/0Med6QChcoqgw3HuHm+8ud7LbXkpA1wIkPaw Rlt2QMctTDf7L06tQ8OKNz0r/iyfCmwKCDp7O7DcTkCUWwGS3xZjqOWvJfVJV35LJL1W f0DA==
X-Gm-Message-State: APjAAAV7GWT72Zciw7L6ZyrfjVvuL7tLrqDCfwXUqZW5/ohCLYA0kHGR exUnRZzvrGwXFFu0Ln5Od4Gm8yrjhDhmUt/pdC4=
X-Google-Smtp-Source: APXvYqxKYqP/yeJQ3RPEs+5Ry8VUIhr/V8fthpSYtuClS1PahDSFvPRr75fX824KnDI9Ryzfu2G0W0WaNYKiz4HW6oU=
X-Received: by 2002:a05:6602:1d2:: with SMTP id w18mr2996716iot.157.1564614592917; Wed, 31 Jul 2019 16:09:52 -0700 (PDT)
MIME-Version: 1.0
References: <20190725191746.GB12596@ubuntu-dmitri> <20190730154809.BBE3412178@welho-filter1.welho.com> <CALGR9oZnKo1JXnxLiKp+04kJeT5Uek3BiCPq=XSq4dG4B3AUBA@mail.gmail.com> <CACweHNDChKtVBTzQGctxAFdgZydrOKt8a9oAKrYbbq1JKLFPNg@mail.gmail.com> <CALGR9oaM2JaAnFJt+e6B87jNYgGd42_fRbycSrqU31tEgR=AEg@mail.gmail.com>
In-Reply-To: <CALGR9oaM2JaAnFJt+e6B87jNYgGd42_fRbycSrqU31tEgR=AEg@mail.gmail.com>
From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Thu, 1 Aug 2019 09:09:43 +1000
Message-ID: <CACweHNBdvqCvDMmgr+=5z9TkQyFYHnE6BMbdUcMG8AJoCDrf3g@mail.gmail.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, HTTP Working Group <ietf-http-wg@w3.org>, Brad Lassey <lassey@chromium.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Content-Type: multipart/alternative; boundary="00000000000005767a058f0239a7"
Received-SPF: pass client-ip=209.85.166.54; envelope-from=phluid61@gmail.com; helo=mail-io1-f54.google.com
X-W3C-Hub-Spam-Status: No, score=-4.6
X-W3C-Hub-Spam-Report: AWL=-1.123, BAYES_00=-1.9, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.201, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1hsxjZ-0005qM-Uv 7a77ae3d46b29cafd717f3547225e3d0
X-Original-To: ietf-http-wg@w3.org
Subject: Re: SETTINGS_PRIORITY_SCHEME | Re: Setting to disable HTTP/2 Priorities
Archived-At: <https://www.w3.org/mid/CACweHNBdvqCvDMmgr+=5z9TkQyFYHnE6BMbdUcMG8AJoCDrf3g@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36895
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 at 21:02, Lucas Pardue <lucaspardue.24.7@gmail.com>;
wrote:

> Hi Matthew,
>
>
> On Tue, 30 Jul 2019, 22:25 Matthew Kerwin, <matthew@kerwin.net.au>; wrote:
>
>>
>> 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"?
>>
>
> It's difficult for a server to guess at the client intent. Not sending
> PRIORITY information is also a signal to prioritise the request with
> default RFC7540 parameters (depend on root node with weight 16). So having
> a clear signal from client to server along the lines of "I don't intend to
> send, and don't infer any RFC7540 meaning from it" avoids that problem and
> my impression from Montreal was that this is a desirable goal.
>

A hint, then.  Different from all the "I will understand if you do this"
settings.  I feel it's important to reiterate, though, that the setting *can
not* say "don't infer meaning from it" -- you can't use a setting to tell
the other end how to respond to your frames, only how you will respond to
theirs.

What happens if the client connects to a server that doesn't understand the
setting?  Are you using it as a negotiation-lite signal, so the client
won't switch off its 7540-priority-tree code path until both ends have said
they're happy doing so?



> 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".
>
> Lucas
>

Eurgh, why?  Are we that short on frame types?

Cheers
-- 
  Matthew Kerwin
  https://matthew.kerwin.net.au/