Re: [quicwg/base-drafts] HTTP/3 with strict priorities (#2700)

Dmitri Tikhonov <> Fri, 17 May 2019 17:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CCDF6120194 for <>; Fri, 17 May 2019 10:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Status: No, score=-3.009 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5kH3SYC2QE0V for <>; Fri, 17 May 2019 10:44:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 456D8120175 for <>; Fri, 17 May 2019 10:44:11 -0700 (PDT)
Date: Fri, 17 May 2019 10:44:09 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558115050; bh=fhQQKYLZf+yc8AKlQEVHuqlBhin3E2ePVgRJjZBbkbU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=r5GPInkEYuk6TWXsBwHYiI4P1ytAE/vI+O65Wp+TElHtPQzWF7anrVGJjzW2UkQmM bdQ9Xz7SK22MKBElcTvnZirz0jdJZki61s2AlhufKqXwmJlB0WK1EzCyW2ky/pgwPQ n5xztMtF3LaJuhvXhWND1qwqIp2egkQCnrbxWj/Y=
From: Dmitri Tikhonov <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2700/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] HTTP/3 with strict priorities (#2700)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cdef2e9f07b6_2e5e3fdcf72cd968531862"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: dtikhonov
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: Fri, 17 May 2019 17:44:26 -0000

@mikkelfj writes:
> Code reuse from an old spec is IMO not a good basis on which to make design decisions for a new spec, while proven concepts could be.

I agree.  My point is mostly that one technology already works.

@lucasp writes:
> Which stacks do you have in mind?

I mean mostly browsers.  It is they that have to figure out how to use priorities effectively.  The servers just have to follow what the client says.

> Yes, we don't want to throw the baby out with the bathwater. However, we should also be aware that there's going to be a ton of work to determine how HTTP/3 performs in real-world usage scenarios. Predicting the effects of HTTP/3's design on that work is hard.

The logical next step is to make prioritization configurable?

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