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

Igor Lubashev <> Sat, 18 May 2019 14:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8DF321201B7 for <>; Sat, 18 May 2019 07:51:45 -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 lIvrtoccCHSS for <>; Sat, 18 May 2019 07:51:43 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B09FC12009E for <>; Sat, 18 May 2019 07:51:43 -0700 (PDT)
Date: Sat, 18 May 2019 07:51:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558191102; bh=A829AYQsFu3lQPhi/dmtO/5rXcWEvZXE23iD3YeCPXs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tWgXWm0nFbEFAr2zhskkXGyHXT+TAfaBGRfzcPJ3US8yPlRvijPifsZeoMkJwwZtl UXU/zWwOlYFB6VvLwCH4GgdJyctYVi7Grj6vrxDv9qOnZ67Acd2fSZ/7OswlHoBn95 5DA4dFV/kzhC8R3gBYj2poEbh57ad2C+nkxVrRso=
From: Igor Lubashev <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2700/review/>
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_5ce01bfec545_35693fe6e0acd9681202047"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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: Sat, 18 May 2019 14:51:46 -0000

igorlord commented on this pull request.

 Requests may override the default initial values by including a PRIORITY frame
 (see {{frame-priority}}) at the beginning of the stream. These priorities
 can be updated by sending a PRIORITY frame on the control stream.
+Higher priority elements have all available data sent before elements of lower
+priority.  When multiple elements have the same priority, if a weight is
+specified, elements with weights are interleaved.  If a weight is 0, either
+because it is the default weight or it was not specified, then elements are
+delivered sequentially and all available data from one element is sent before
+any data from the next.  If a given priority level has some elements with
+weights and some without, the two groups share the available bandwidth equally.

You can have 10 elements with weights at some priority level, sharing bandwidth.  When you add a single element to that priority level without a weight, the bandwidth for the 10 elements is halved.  This does not seem right.

weights and some without, the two groups share the available bandwidth proportionally to the number of elements in each group.

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