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

MikkelFJ <> Fri, 17 May 2019 07:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 51791120364 for <>; Fri, 17 May 2019 00:53:35 -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 C5FagCCk7pqk for <>; Fri, 17 May 2019 00:53:33 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C25F11201A1 for <>; Fri, 17 May 2019 00:53:27 -0700 (PDT)
Date: Fri, 17 May 2019 00:53:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558079605; bh=3ohyQpbA4Mz2f77qU2gHPXgaPXYJQriuBIgzG6NrdxQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LbCdShXRHujNqOTbW3t8oeKU9BG3UHCkcn5u000YJ0w54rgJPpCr0a5td4Nxop/Ww WyxNR3U73/U5M+KgS61crxwe79qw4/4Nf5CDj29k8sZiH9v+SZMeYU8Z3zLXhyrmvS cjE4KP3eI03AdkeM6IeyqVg4pXCuXAdKlou3T42M=
From: MikkelFJ <>
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_5cde687559bd6_75713ff149ccd95c25027"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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 07:53:37 -0000

If strict interruption is not critical, it would simplify the QUIC API if weights can be applied and updated to active QUIC streams such that the QUIC scheduler can use weighted round robin to decide what to send next without tracking which streams are currently blocked. It would also allow very small streams to complete even if they have low priority, for example small SVC icons. On the other hand, HTTP/3 probably shouldn't start new streams of lower priority while there are higher priority streams still transmitting or ready to be transmitted.

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