Re: [quicwg/base-drafts] Mandate allowing peer to create enough unidirectional streams for HTTP and QPACK (#2762)

Mike Bishop <> Thu, 06 June 2019 18:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DD576120111 for <>; Thu, 6 Jun 2019 11:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 BDseIJn-jrNk for <>; Thu, 6 Jun 2019 11:17:25 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 01C2D120094 for <>; Thu, 6 Jun 2019 11:17:24 -0700 (PDT)
Date: Thu, 06 Jun 2019 11:17:23 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1559845043; bh=9hQzN3i5xlmFlQ0VaY3I5HQSCKUPl0f3CnVDBBzi60M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mpqywq0Upwv5AL23NcrbKqy3CavWyyqIg6mpo1EzGfzYcWzA5zgfzGNNARwK8crii 71fDfu0/6XZXs3OUHfY9XrGflyS6/yC5+ib+hSEHdxPtrHKq/p59J1sYPoGBpCNuyq TOoUhDd1CBG39ummEXmYWTMLxR0G7+NoR4Wyhm/A=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2762/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Mandate allowing peer to create enough unidirectional streams for HTTP and QPACK (#2762)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cf958b39c3ad_71ef3fd2388cd96819085c"; 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: Thu, 06 Jun 2019 18:17:27 -0000

MikeBishop approved this pull request.

There's one nit which implies a design question; once that's settled one way or another, I'm happy with this.

> @@ -912,10 +912,20 @@ Endpoints that set low values for the QUIC transport parameters
 chance that the remote peer reaches the limit early and becomes blocked. In
 particular, the value chosen for `initial_max_uni_streams` should consider that
 remote peers may wish to exercise reserved stream behaviour ({{stream-grease}}).
-To reduce the likelihood of blocking, both clients and servers SHOULD send a
-value of three or greater for the QUIC transport parameter
-`initial_max_uni_streams`, and a value of 1,024 or greater for the QUIC
-transport parameter `initial_max_stream_data_uni`.
+To reduce the likelihood of blocking, both clients and servers MUST allow
+the peer to create one unidirectional stream for the HTTP control stream plus
+the number of unidirectional streams required by mandatory extensions (such as
+QPACK), by setting an appropriate value for the QUIC transport parameter

This comma doesn't flow as-is.  I'd try one of the following:
- remove it ("...MUST allow ... by setting an appropriate value....")
- make it a lead-in to options ("...MUST allow [...], either by setting an appropriate value for [...] or by sending a MAX_STREAMS frame immediately after opening the connection.")
- split into a new sentence ("...MUST allow [...].  This can be done by setting....")

The implicit question in those options is whether omitting the TP and immediately sending a MAX_STREAMS frame is acceptable behavior.

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