Re: [quicwg/base-drafts] Prohibiting server-initiated streams for h3 (#2711)

MikkelFJ <> Fri, 17 May 2019 08:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E28F612010D for <>; Fri, 17 May 2019 01:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Status: No, score=-1.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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZmLsmDmybpkm for <>; Fri, 17 May 2019 01:02:21 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 654D3120127 for <>; Fri, 17 May 2019 01:02:20 -0700 (PDT)
Date: Fri, 17 May 2019 01:02:17 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558080137; bh=0KS/WA/2wnVdCugWF1/8kQ5BUTjjubr9BlWipzJH4VM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qxpPtFpn9lyZuYfzZhGhZp7vIqHxFW9d0NoyEwhqZbZkM4ovwzMYMYEE/XL75UIz6 MrUFsAc3pttXyA/9xyGbbSJXtdpXVDLp7rBDGEf58fEP9GeAxYmVn46a8GauNgI2EK x+11t25NxlGh6uoCYQcGZxdYaACKG2coMmmSx+Po=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2711/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Prohibiting server-initiated streams for h3 (#2711)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cde6a89b036e_41483fc8dc0cd96c76389a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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, 17 May 2019 08:02:23 -0000

I don't think the transport should police what streams are opened beyond managing resource consumption. It may well be, in some other app protocol, that a server is free to open bidi streams, but only if they start with a certain header, or none at all. The  app protocol should make both endpoints agree and what is permitted and police accordingly. An application layer could have credits similar to MAX_STREAMS to permit opening certain streams with or without a header. The transport need not deal with this.

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