Re: [quicwg/base-drafts] HTTP/3 priorities are too complex for a majority of implementations (#2739)

Patrick Meenan <> Wed, 22 May 2019 13:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E51681200CC for <>; Wed, 22 May 2019 06:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.392
X-Spam-Status: No, score=-6.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, RCVD_IN_DNSWL_HI=-5, 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 gxiXaKNlt8XF for <>; Wed, 22 May 2019 06:32:12 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 78A56120033 for <>; Wed, 22 May 2019 06:32:12 -0700 (PDT)
Date: Wed, 22 May 2019 06:32:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558531931; bh=mAbnoLVP16Jex2Hh2wO5NTrRjtHtuo9BdN2fvlYHzfU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=v1c3xDouJVXLLbb58Pgd4Xi50UbVruNgQ1vyNDosYOQwVUGXZcsm31vOj3LIf8yYe 6rpH3ieSLGX/n+T57UlqhaKIwu9RnaYwxv9IQyAdiGeb4jnuyDa7bzoVuc+UomHm9q H9QIAb/AhBfd/CEACQ+NeU++i5r9u+A8IxJHRUR8=
From: Patrick Meenan <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2739/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] HTTP/3 priorities are too complex for a majority of implementations (#2739)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce54f5b7dea2_699a3f8b3d2cd9605374e2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: pmeenan
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, 22 May 2019 13:32:14 -0000

The other big change discussed yesterday by moving away from a tree we can move from a relative priority structure where each request needs to know about the others on the same connection to an absolute priority scheme where priority can be tied to the request itself without extra knowledge. Within the HTTP/2 implementation itself it may not make a big difference but exposing it as an API on the client and server side becomes much easier (and it allows for merging of priority decisions made on the client and server sides). 

A simpler API could always be mapped to the tree but managing equivalent mappings on both ends can become unwieldy if you have multiple clients you don't control or talk to servers you don't control.

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