Re: [quicwg/base-drafts] HTTP/3 priorities are too complex for a majority of implementations (#2739)

Lucas Pardue <> Wed, 22 May 2019 11:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DB68F12011C for <>; Wed, 22 May 2019 04:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Djgdct0r-Ro5 for <>; Wed, 22 May 2019 04:33:11 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DB5E512004D for <>; Wed, 22 May 2019 04:33:10 -0700 (PDT)
Date: Wed, 22 May 2019 04:33:09 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558524790; bh=Cb+fai5xSCHl8vwJyLeOBjJveaDkU9s4Ji9L9rQ9984=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VdzCCZtHDsTYdP8Avp+mb+n7zigj8m2TZzknzHcqzzgP0jd6jLcQC2TBR5XMZDhvv nnTNRxcWOmbyFGk4wl2rvJloJOYPlIyFMdOhuCViDBZ9Ks663hTSA/jKVSVsX5LJuL qIlQU49iQhh5rqsu1Bursq5jkobVvFwq7SBQNrMc=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2739/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] HTTP/3 priorities are too complex for a majority of implementations (#2739)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce53375eb696_119c3fb1812cd96480921c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 22 May 2019 11:33:12 -0000

It's good that there are ways to improve performance in such ways. However, I think that the HTTP/3 layer should allow prioritisation of resource loading. That way it applies to all user agents, not just those that have a DOM and or JavaScript engine.

> Also, I feel this is a separate topic that might require a different issue to not take away from the core issue being discussed here.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: