IETF Logo Mail Archive

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

Martin Thomson <notifications@github.com> Fri, 17 May 2019 10:35 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 97B9D12023B for <quic-issues@ietfa.amsl.com>; Fri, 17 May 2019 03:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.464
X-Spam-Level:
X-Spam-Status: No, score=-1.464 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 k4MoizgTiIVE for <quic-issues@ietfa.amsl.com>; Fri, 17 May 2019 03:35:12 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B1F812023C for <quic-issues@ietf.org>; Fri, 17 May 2019 03:35:12 -0700 (PDT)
Date: Fri, 17 May 2019 03:35:10 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558089310; bh=wSJTWYrp3Ey9nCT2EOZ64kP/yH14Gbnic8EhWhJFHJA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PKVLnxKbmE7dreuAcC0xLokSxPZauEa2EJpNBsXMVBdCUlCNGIL4OWrR3Zh6Lf7Sk AhflpIbKip0BDwM0DOekLX0jznVc7CZ+OsRvocznKGcrZMhjJnuh8ZzKr4clbqruG7 9ZIJTBfQvU2hP9g78QFgdt5v0Hw1LNCEdoH6RpjM=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6TAN6KYJULDZAW2Y525PAN5EVBNHHBVBMVX4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2711/493407812@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2711@github.com>
References: <quicwg/base-drafts/issues/2711@github.com>
Subject: Re: [quicwg/base-drafts] Prohibiting server-initiated streams for h3 (#2711)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cde8e5eccdb1_96c3fe1aaecd9685661de"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/JM8W-hQrL2x-PqWXsQKmP8raATc>
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: Fri, 17 May 2019 10:35:14 -0000

Right.  The transport only needs to concern itself with policing stream limits.  The question here is more about how the use of h3 constrains future extension.  As Mikkel says, if there is a use for the server-initiated streams, we shouldn't constrain 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/issues/2711#issuecomment-493407812

v2.23.0 | Report a Bug | By Email