Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)

Robin MARX <robin.marx@uhasselt.be> Thu, 21 November 2019 02:11 UTC

Return-Path: <robin.marx@uhasselt.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8CF512090F for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 18:11:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uhasselt.be
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 UsXqj9F_-Eq8 for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 18:11:43 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D105120917 for <quic@ietf.org>; Wed, 20 Nov 2019 18:11:43 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id t5so1401839ljk.0 for <quic@ietf.org>; Wed, 20 Nov 2019 18:11:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uhasselt.be; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RVIiPLUBRLUkcv63jQhE2qIjGmGjYXLvhg5I0+02sNY=; b=ULBOUBhUhzKyluFrLHaJPWm/u17N+7ZejkKY8iGz52Pypvm8tBpYWzWDJFiBrTp56g UyPoiq9RI7R99FXqt0buUuHclf4OCGaXSUyLPAFMMIJgwvgI1r7tD1geI8ZRvtTE5uoS yMvKhW1jd5kzhlNjgCYMPjugyZAp6MRSlIjC0=
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=RVIiPLUBRLUkcv63jQhE2qIjGmGjYXLvhg5I0+02sNY=; b=EG2eVHOZZpDa87XC4e+EYyiRsqtCA/eNVdurYFHYAAsz2YHgFWemDNxA52CB2RUido jwOLuICPIGnf21g7/CTC9R8Mg3fHgsAXZtPJtMrfM0JhhWr77XVDMqTU3TFYsUo+fu9g HmxzC7RAgwRTioZcg9WCvPRxBeBqzPQFUPXtxpVmJvOvELjdHByvfpR6eccoLsrGGIoM Mzr/9tTGj8FzksnB1pXAPK25jbT14eSwe3UlxgOxbDKSjExPV7BKhqXJEQgeFSkOjjkb LFytMTCbKh4SWte9lK0xyc+5ujHOnnv8fwEk5NvCaw8sA/5/a2jVO4DLFY7zddshvCCD ECgg==
X-Gm-Message-State: APjAAAW1VxsitF9W1v74PYPmOXB57r02A6BnXWs2/MjAvr1oJI1HoVqy 19VtUGvKdtcVwyC7DWzyuxbxpvqmmOjAou/NUvRpBiTf9fw=
X-Google-Smtp-Source: APXvYqyedb9PimZcsmZnkXox3WJQkFx+jU0b2p9teJ4DBi/ShjjA7pCBiljM3rH7GlPpNOEw4bHNh7hz4RGGQ7ULeUw=
X-Received: by 2002:a2e:8654:: with SMTP id i20mr5233946ljj.224.1574302301183; Wed, 20 Nov 2019 18:11:41 -0800 (PST)
MIME-Version: 1.0
References: <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com> <421180B5-6939-4EB5-B2CA-1A97BA9BAEA9@gbiv.com> <a8f57134-114e-4d56-9076-7d880897b842@www.fastmail.com>
In-Reply-To: <a8f57134-114e-4d56-9076-7d880897b842@www.fastmail.com>
From: Robin MARX <robin.marx@uhasselt.be>
Date: Thu, 21 Nov 2019 10:11:29 +0800
Message-ID: <CAC7UV9bqo=jFearFt-yTr5M6q7noywvicG-bW6k4UQGq7bikuQ@mail.gmail.com>
Subject: Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
To: Martin Thomson <mt@lowentropy.net>
Cc: Roy Fielding <fielding@gbiv.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006e79f10597d1d141"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2LdPmu17JVga_EhErpJNn9bnXVU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 02:11:46 -0000

Hello Martin,

 > I understand that reprioritization was identified as being important by
the design team, but I don't recall seeing ever any evidence to support
that view.  Can we split that piece out and maybe pursue it separately?

Could you expand on this statement a bit more?
In my view, reprioritization has two sides: reprioritization from the
client after sending an initial priority and server-side reprioritization,
overriding the client's initial priority.

The first side comes into play when doing things like video/media streaming
when switching qualities (see e.g.,
https://github.com/kazuho/draft-kazuho-httpbis-priority/issues/92) or for
the "switching tabs" use case that e.g., Ian keeps mentioning.

The second side was discussed at some length in our paper (
https://h3.edm.uhasselt.be/files/HTTP3_Prioritization_extended_3jul2019.pdf)
and also in a series of Cloudflare blogposts (e.g.,
https://blog.cloudflare.com/better-http-2-prioritization-for-a-faster-web/).
It is also imo mirrored in the intent of the priority hints proposal from
the W3C (https://github.com/WICG/priority-hints/blob/master/EXPLAINER.md).
One of the main reasons for simplifying the H2 scheme (next to
implementation complexity) is to provide an "absolute" priority indication
so that it's easier to reprioritize the responses on the server side.

Are you talking about both or one of these sides?
While I would agree we have less data for the 1st side, I do feel everyone
on the design team agrees this should be kept in.
Removing the PRIORITY_UPDATE frame would also lead to significant push back
from the Chrome team, as I understood from Ian (though I don't want to put
words in his mouth), and would make the proxy-to-origin case difficult
again.

With best regards,
Robin


On Thu, 21 Nov 2019 at 10:00, Martin Thomson <mt@lowentropy.net> wrote:

> On Thu, Nov 21, 2019, at 09:53, Roy T. Fielding wrote:
> > Even with these minor issues, I think this draft is a great improvement
> > and is ready for adoption by the WG.
>
> Oh, I forgot this.  I agree with Roy, we should definitely adopt this
> now.  The issues I raise are minor enough that we can work them out in the
> working group.
>
>

-- 

Robin Marx
PhD researcher - web performance
Expertise centre for Digital Media

T +32(0)11 26 84 79 - GSM +32(0)497 72 86 94

www.uhasselt.be
Universiteit Hasselt - Campus Diepenbeek
Agoralaan Gebouw D - B-3590 Diepenbeek
Kantoor EDM-2.05