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

MikkelFJ <> Wed, 24 July 2019 07:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3EDEE12032E for <>; Wed, 24 Jul 2019 00:06:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RCw6nDBs0BuT for <>; Wed, 24 Jul 2019 00:06:55 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 819D31202DF for <>; Wed, 24 Jul 2019 00:06:55 -0700 (PDT)
Date: Wed, 24 Jul 2019 00:06:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1563952014; bh=9HDAd66RJK3yXZCHGqaDIcAYOV5QdIPjZFk9nsFpd7U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u1DCGiWN/IV+dIx1HYwII0W3p6Z1vfUPm5cykRSUwxlFCMCZesuQ3cZrtkpnRgz14 ZkzGBhJI0nhxGw1ZSvU/qNgrk8kaMupYEBGBlzsUOcv4wipB6Vj+RPmUTAhYoFTHuT mt3Tn5JWo6XW+C8zHwYdLD5bvZVTGuYW3D4OmH+4=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2924/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Remove PRIORITY (#2924)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d38038e5c042_61d03f85696cd968147014"; 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: Wed, 24 Jul 2019 07:06:57 -0000

For reference, here is the pmeenan scheme:

The scheme states the bandwidth splitting is implementation dependent. That makes me wonder if Weighted Round Robin scheduling would make sense - it is certainly something I would build into the core transport scheduler based on app provided priorities. It would be neat if H/3 tapped into such a framework.

This means the low priority content is not 100% excluded by higher priority content such that small content can get through eventually. But likely there could be some tunable parameter for how much residual bandwidth is reserved for the next lower priority. E.g. 0% or 10% etc. 

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