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

Robin Marx <> Thu, 23 May 2019 07:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2290112008A for <>; Thu, 23 May 2019 00:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Status: No, score=-3.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 bOKwO3bdsyxa for <>; Thu, 23 May 2019 00:41:34 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A94F9120019 for <>; Thu, 23 May 2019 00:41:34 -0700 (PDT)
Date: Thu, 23 May 2019 00:41:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558597293; bh=a1cSjshPvAO3bNvGB9OOk/9l3bFkis8gpO/vmGS3AKk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ha/Ozame14XbpBiZ+wcBGb06nUr6Il0Cg4eOC6lhvW1U4jII1wrnE+GGXt3uDmMXf Bcmkr264dRjurXPL7y7O5LX+9pkHZlni/oJxvpSgiPZwKti2ddMAVdKUTVk+7kP7nK 8l9uVB2ImKgYthL1ipOXpkjjbuorwtfcOs6u2GnA=
From: Robin Marx <>
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_5ce64ead80535_66363f85302cd9641036c7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: rmarx
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: Thu, 23 May 2019 07:41:37 -0000

Just to come back to my comment from before:

> It would also allow resolving #2690 in the same way as proposed in #2723 : just make priority 0, no weight the default for new nodes!

This is not entirely correct sadly... 
Main example is Safari/Edge behaviour: all nodes dependent on the root, setting explicit weights (but no priorities!).

If un-prioritized/default nodes are added with priority 0 + weight 0, they would share the bandwidth 50/50 with the weighted nodes, making this default even worse than the HTTP/2 of adding the nodes with weight 16... 

Potential solution is to add them with priority=0,weight=1, but then they will still get some part of the bandwidth (how much depends on the weights of other things) and we are again back to round-robin (which we don't want, we want FIFO in the default case). 

So, other solutions:
- Nodes without priorities and without weights (default): priority=0, weight=0. Nodes without priorities but WITH weights (explicit behaviour): priority=1,weight=incoming
- Special priority level -1 ("implicit orphan placeholder")
- Explicit orphan placeholder (#2690) (BUT then we can't implement this setup without any placeholders at all, which is possible at the moment)

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