IETF Logo Mail Archive

Re: [quicwg/base-drafts] Remove PRIORITY (#2922)

Kazuho Oku <notifications@github.com> Mon, 22 July 2019 19:57 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E988C12008C for <quic-issues@ietfa.amsl.com>; Mon, 22 Jul 2019 12:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 eGl-esszi0l5 for <quic-issues@ietfa.amsl.com>; Mon, 22 Jul 2019 12:57:02 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E78D612008F for <quic-issues@ietf.org>; Mon, 22 Jul 2019 12:57:01 -0700 (PDT)
Date: Mon, 22 Jul 2019 12:57:00 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1563825421; bh=PTsyXQiN59R2g66v+/KlQL4yXqC1P0shdCEqBtH8jKU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xeJ4Cci3XiwsM4zVp3SvKQ7z7MsF6J720vT7PHQMQXmYq/4IAw3pfQc/+cqs5m1TQ /P6bA79pjbIjKY45aSXx5iZFzbrlUSs/snRPa7jCSS6TS6zW7y52eMV5Wscu24jPKX ENctviBAUB4c+2P01pMAt2XSF7ejqnN6BbdPfzj4=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK23RSOXG5HAQ2TU2XF3INDYZEVBNHHBYFV37I@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2922/c513930838@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2922@github.com>
References: <quicwg/base-drafts/pull/2922@github.com>
Subject: Re: [quicwg/base-drafts] Remove PRIORITY (#2922)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d36150ceda3f_5f4c3fc75a2cd95c2570ec"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/A7OkQPVDy-R7BycQ1W1zuDJKol8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jul 2019 19:57:04 -0000

I think that this is the correct thing to do.

At the very least, I'd assume that server-driven prioritization using content-type would work well to some extent. Since the early days of H2, we've doing that for browsers that does not use dependency, and it is my understanding that it has been working OK. Though it would be preferable to have the capability of servers and clients providing "hints", especially to distinguish between a render-blocking JavaScript file and a asynchronously-loaded one.

> Does this mean it goes away in v1, or restarting from scratch?

I'd assume that once the QUIC and HTTP working group agree to drop priorities from H3, it would become the task of the HTTP WG to determine what to do.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2922#issuecomment-513930838

v2.23.0 | Report a Bug | By Email