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

Mike Bishop <> Mon, 07 January 2019 20:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 513E712008A for <>; Mon, 7 Jan 2019 12:21:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.064
X-Spam-Status: No, score=-8.064 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_32=0.001, 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 Oa3D9Fnfy1kI for <>; Mon, 7 Jan 2019 12:21:44 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7940012D4F2 for <>; Mon, 7 Jan 2019 12:21:44 -0800 (PST)
Date: Mon, 07 Jan 2019 12:21:43 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1546892503; bh=/XLTfP4WE2DT/203F4I2WHSx7IPKnUVWf5AExoK6sys=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=a3oZxSV2lOSmr8TuMFmYATuHJTK0AxSqKac+i/xwZ/faSsMoYNJUzKKQfIbk7UBhz SlGXmuUgJJmMEmjP3kOrlttMW17PBMB1SvuGIcHADNarbW9xqF/QYou8ht0YeFL2kw TZ0n73VNg/i4bzZkn1piVz+KZwv/nczjsSgmrkNI=
From: Mike Bishop <>
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_5c33b4d7a8e96_62023fbab6ed45bc2231e9"; 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, 07 Jan 2019 20:21:47 -0000

Well, there's technically nothing preventing the use of push....  ;-)

More seriously, I don't feel like the prohibition adds much.  This maps the definition of the CONNECT method into H3 framing -- DATA frames == TCP payload.  In any other respect, it's an HTTP request and frames mean what they otherwise mean.

Is there a particular frame that *needs* to be prohibited?  HEADERS would indicate a trailer block; it might be worth upstreaming to the updated semantic draft that a CONNECT tunnel can't have trailers.

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