Re: [quicwg/base-drafts] Allow not creating QPACK codec streams (#2529)

Alessandro Ghedini <> Wed, 20 March 2019 18:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 423A5131216 for <>; Wed, 20 Mar 2019 11:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 oFYbjG5HZlty for <>; Wed, 20 Mar 2019 11:28:27 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 28842131210 for <>; Wed, 20 Mar 2019 11:28:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=pA5E2WmIfwKzwqD9xHxFQ+3L6CQ=; b=guAVg7ly4vnQ/IIt veXjznTmTLD1BXtlVsCtjcjmQTlJrzwYzGb/tx69xo7BoGR8mGYqxi1RxBTg93/Q GG8o5Ki4BR6DaTWZ6dIsADeJsAb1xNEUdGlTDTmy3ytwl5Ge2SClel+tKErlWwF8 LM1N/LvedzksKE0G2I3bGq+qstE=
Received: by with SMTP id filter1350p1mdw1-31674-5C92864A-7 2019-03-20 18:28:26.049719685 +0000 UTC m=+169127.137837138
Received: from (unknown []) by (SG) with ESMTP id j43DiPAqTEuzT_Mi-CUJjw for <>; Wed, 20 Mar 2019 18:28:25.986 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id EE45E2C0072 for <>; Wed, 20 Mar 2019 11:28:25 -0700 (PDT)
Date: Wed, 20 Mar 2019 18:28:26 +0000
From: Alessandro Ghedini <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2529/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Allow not creating QPACK codec streams (#2529)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c928649eca1c_5fc83fe54d8d45c43456d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ghedo
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2nATXZnol5y7zCUtB31NWRhOApMmHkQV3pkk zncAUO3B/kFooSZZpHHSCGOPZR79Lz+gdImVjU0PzXC6OGIugtrE9IkPkeBFzp89InJRjovFWD7Cjk j9kvco+O4bIB5sGAFa6+tZwXFpgMK7sXI7NQHaIkKWDzfH/2jsXOYutAcbjGOELq4uZUU9Hc05/xgg w=
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, 20 Mar 2019 18:28:30 -0000

ghedo commented on this pull request.

>  HTTP_WRONG_STREAM_COUNT. These streams MUST NOT be closed. Closure of either
 unidirectional stream type MUST be treated as a connection error of type
+An endpoint MAY avoid creating its own encoder stream if the maximum size of
+the dynamic table permitted by the peer is zero.
+An endpoint MAY avoid creating its own decoder stream if the maximum size of
+its own dynamic table is zero.
+An endpoint MUST allow its peer to create both encoder and decoder streams

Hmmm, I think I was reading wrong.

But yeah, the intention there was to disallow setting the uni streams limit to less than 3 in order to allow the other side to open all of their streams. This is effectively what the spec says right now I think, since each side MUST create their streams and if the peer's limits prevent that, than the endpoint can't create them.

I would also be fine aloowing one side to prevent the other from opening and making that not an error, but either way I think we should specifiy what to do since the spec right now is far from clear on this.

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