[quicwg/base-drafts] Are Separate Uni and Bidi Stream Limits Meaningful? (#2358)

martinduke <notifications@github.com> Tue, 22 January 2019 18:50 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 3A339130EE1 for <quic-issues@ietfa.amsl.com>; Tue, 22 Jan 2019 10:50:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.935
X-Spam-Level:
X-Spam-Status: No, score=-10.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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, 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 mZn7b57DADwt for <quic-issues@ietfa.amsl.com>; Tue, 22 Jan 2019 10:50:53 -0800 (PST)
Received: from out-16.smtp.github.com (out-16.smtp.github.com [192.30.254.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D7A712875B for <quic-issues@ietf.org>; Tue, 22 Jan 2019 10:50:53 -0800 (PST)
Date: Tue, 22 Jan 2019 10:50:52 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548183052; bh=msonlQ/qy/4sCb24642KvACAvYVIHkq0UD6fiUu/JzA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=VYhKkH+4QZtPWqprV5cr1JNnw9PV4dnFaYiP49XupEjwyrZYIpD4Z8c+Dbwkl/V/J 7g1L5d37XEpfNqc3SNQaiUD/oyuvLPb9cYIocXpvSGc3xHrXkMPfw12Ayo8PaddIze w69LGunc6h/TF+ahbPD4mMpKqriAbkEa5uAZ29l0=
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb27021ab4b1386720748f8d3d7ae8d5427ba232792cf00000001185f280c92a169ce17f4906c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2358@github.com>
Subject: [quicwg/base-drafts] Are Separate Uni and Bidi Stream Limits Meaningful? (#2358)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c47660c866b9_30563fabf6ad45bc155444"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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/1SZyVGODqfKw89O97qd8jouq8hI>
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: Tue, 22 Jan 2019 18:50:55 -0000

I believe there's loophole in these limits.

If the peer has given me uni credit but not bidi credit, I can open a uni send stream and send data. Are we counting on all applications to handle this correctly? (e.g. HTTP/3 will prohibit a request on a uni stream)

Similarly, if I have bidi credit but not uni credit, I can open a bidi stream with a STOP_SENDING.

Are we comfortable that the abuse cases are benign? Now that there is no "max-stream-id" parameter, it is more straightforward for stream limits to be global, should we decide that's better.

-- 
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/issues/2358