Re: [quicwg/base-drafts] Can I send non-data frames on CONNECT streams? (#2229)

Kazuho Oku <> Fri, 21 December 2018 02:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8DE6B12D4E9 for <>; Thu, 20 Dec 2018 18:41:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.447
X-Spam-Status: No, score=-6.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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] 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 Obg5yOxvmkcB for <>; Thu, 20 Dec 2018 18:41:56 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 99E21130DD1 for <>; Thu, 20 Dec 2018 18:41:51 -0800 (PST)
Date: Thu, 20 Dec 2018 18:41:50 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1545360110; bh=vn05Qvyhp/aDEo8DhMjy8x7rsNRg7MSevHJthRMhLcs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gr1F/2doF2pKgEE670ksvo/cb/72O0SWzMDJR7gbJwGsCCr1iELELyp/j3pBZkYsB qSaaQFFNZOjFNM6j8XAkk9P7WNBZHZJ4PImo8Eye+Kdg4W/zTX1B3n5P+KWjZdfoG1 iSPsvFs3ZhrvPZExc/ViaoiWE/4lq0HgLtZvccaA=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2229/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Can I send non-data frames on CONNECT streams? (#2229)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1c52eee47b3_45993fa85ccd45bc15874b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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: Fri, 21 Dec 2018 02:41:59 -0000

Wouldn’t it be better to just prohibit the HEADERS stream?

We might want to introduce a frame that changes the priority of a stream (e.g., max bitrate). I do not think there’s a strong reason to forbid such kind of extensions only on CONNECT stream.

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