Re: [quicwg/base-drafts] Define stream limits as counts (#1906)

Ryan Hamilton <notifications@github.com> Thu, 25 October 2018 22:30 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74654130EAB for <quic-issues@ietfa.amsl.com>; Thu, 25 Oct 2018 15:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, 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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UjF4xD7xA2bo for <quic-issues@ietfa.amsl.com>; Thu, 25 Oct 2018 15:30:15 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35519130EBB for <quic-issues@ietf.org>; Thu, 25 Oct 2018 15:30:15 -0700 (PDT)
Date: Thu, 25 Oct 2018 15:30:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1540506614; bh=CwyPko54wSIrlG6DuHF0qxnjxwWqvw1LO1Cgwi6nVRo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sYhxAbe5YKbDAqiIm2Q6LyCILJ3Jy4Tgbd0k/ClZeYCtygFDjqwS9FkCqnLPtRHlo d48b/DGK6r5nAw3Cw3629RlKpdtuwDY/HCvA42Hd1EByW1S/X3qphQm567gn9d6kO5 c/AaTvtBHIDNo55t0azOvZmgwrtRO/LpPFM4/BWM=
From: Ryan Hamilton <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5ef6ec52e0eaa748abd4c31c92ffacd38aeac1b492cf0000000117ea05f692a169ce1646c612@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1906/review/168612858@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1906@github.com>
References: <quicwg/base-drafts/pull/1906@github.com>
Subject: Re: [quicwg/base-drafts] Define stream limits as counts (#1906)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bd243f64f1bd_2c2e3fbd114d45b4250562b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: RyanAtGoogle
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/3SQTDDofNcHvuDqS1RGqNaRa71M>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2018 22:30:17 -0000

RyanAtGoogle commented on this pull request.



>  
-The maximum stream ID is specific to each endpoint and applies only to the peer
-that receives the setting. That is, clients specify the maximum stream ID the
-server can initiate, and servers specify the maximum stream ID the client can
-initiate.  Each endpoint may respond on streams initiated by the other peer,
-regardless of whether it is permitted to initiate new streams.
+The stream limit is specific to each endpoint and applies only to the peer that
+receives the setting. That is, clients limit the number of streams the server

Hm I'm not in love with the "number of streams" terminology. With "maximum stream ID" it was very obvious what was being limited. If the max stream ID was X, you clearly could not open a steam with ID X+1 (or X+4 but whatever :>).

With a limit on the "number of a streams" this is less clear. If a server limits the client to 10, presumably the idea is that this is equivalent to a max stream id limit of the 10th client initiated stream ID. But it also seems like you could read this limit to permit the client to open any 10 steams. Like 0, 40, 80, 120, ... I think this is not the intent, but the terminology makes this much less clear to me.

For example, the text below:

"A peer MUST NOT initiate a stream with a higher stream ID than the largest limit
maximum stream ID it has received. "

Clearly the limit applies to stream ID, but using "number of streams" seems to obscure that.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/1906#pullrequestreview-168612858