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

Mike Bishop <> Mon, 29 July 2019 17:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E5C241201D7 for <>; Mon, 29 Jul 2019 10:36:41 -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 9m5yo4xZucRb for <>; Mon, 29 Jul 2019 10:36:39 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 481AA1203C1 for <>; Mon, 29 Jul 2019 10:36:38 -0700 (PDT)
Date: Mon, 29 Jul 2019 10:36:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1564421797; bh=FbDgKtunctTdfMP1YzJgr/hXKOMVOGsV0KR97VAe534=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GZ6FAhu0RCXIrlEn71XJfYZie3Yeamf2xYrb5pyYI+/AEGFyrFRPzv85bS+Zar3AC mccsPHKRB9y3idPgnOVn92I0ND4Xxt27sl2PFFGv+MzWTTYGqji1T/0ioUl6l4ClKz b4G7aHc9jxLz/WIU7YNQ19RCRG1vL1lAQDvd/6Dc=
From: Mike Bishop <>
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_5d3f2ea5651f0_25563ffd87ecd9601871c9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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: Mon, 29 Jul 2019 17:36:42 -0000

I think there's a compelling argument to be made for "HTTP Priorities" as a header that can traverse various versions and potentially be cached with a response.  HTTP/2 and HTTP/3 don't define any new headers, because headers are part of the semantic layer.  It seems to me like the paths we can choose are:

- Define "HTTP Priorities" in a separate draft, containing a header for initial values (and optionally frame(s) for mid-response reprioritization)
- Define a new HTTP/3 frame to carry priorities in the current draft
- Define a negotiation mechanism to select a priority scheme in the current draft; these scheme might involve frames or headers.

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