Re: [quicwg/base-drafts] PRIORITY frame on control stream referencing unopened request stream (#2502)

Lucas Pardue <> Wed, 08 May 2019 00:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5F44612006E for <>; Tue, 7 May 2019 17:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.464
X-Spam-Status: No, score=-6.464 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_20=1.546, 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 jydn-TKwuXNX for <>; Tue, 7 May 2019 17:45:06 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 00A1D120073 for <>; Tue, 7 May 2019 17:45:05 -0700 (PDT)
Date: Tue, 07 May 2019 17:45:04 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1557276304; bh=xx4gvfHINSBc3iVxO6dm8enahuKlHxMhyPT94t52G64=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DS0a+zEGS2Z/Xc0uVZeiHt83CwWDj0qJeAtfKForqseJJlpSntuOqISd3OIWfh4V8 E152QUoO04ypiiyY7un7RwmZHA7HpPPUAdtr3zWWFayFQZbIMjjyowZL85RHV8Q31R 6FQlBgJiBVjQgSUmrYlH18+ZWXJB9n3ZLFKFbU2g=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2502/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] PRIORITY frame on control stream referencing unopened request stream (#2502)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd22690b0ec1_7ac03fdb2b8cd96c89378"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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, 08 May 2019 00:45:09 -0000

A priority stream, in our current scheme, has some desireable properties because it aligns with the asymmetry, i.e. only client can create a priority stream. If anyone cared you could borrow QPACK encoder/decoder model so that the client has clear indication when priorities were processed. One could go as far as adopting that model further, 

1) priority stream(s) contains unframed instructions
2) PRIORITY frame on request is just a shell that contains references to priority state.

This opens a possibility to have alternative priority schemes based on opening different types of priority streams.

It all sounds terribly complicated though :D

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