Re: [quicwg/base-drafts] Recommend non-zero values for footgun TPs (#1806)

Kazuho Oku <notifications@github.com> Thu, 27 September 2018 08:46 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 8EA18130E6B for <quic-issues@ietfa.amsl.com>; Thu, 27 Sep 2018 01:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 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_PASS=-0.001, URIBL_BLOCKED=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 MGJ4Wcq6Plq8 for <quic-issues@ietfa.amsl.com>; Thu, 27 Sep 2018 01:46:04 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A471A130E13 for <quic-issues@ietf.org>; Thu, 27 Sep 2018 01:46:04 -0700 (PDT)
Date: Thu, 27 Sep 2018 01:46:03 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538037963; bh=HHdSTprkoD54G1zf8D7acwmWLxOVx+j+bsRa6KpQxy0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Fv7OcFimgYwIsrEudmnQkAB6k9ucjet9JaDRQwjQgnM6N0e6QHbTBJ6Y/M+MRFWNC OKkTQr+k7OBzchk/PnAHOYXDZnv8L4CQfH5/yw76JCLR/GmHK4P7G/fKC3Db4WE0wP JB35hTClwiWqxWdPXj30+M3t8ZKsXrUxuk3jwiZM=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab702ab986e51880341c0e6426020ce8911d2eaeee92cf0000000117c45acb92a169ce15b44a1d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1806/review/159340977@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1806@github.com>
References: <quicwg/base-drafts/pull/1806@github.com>
Subject: Re: [quicwg/base-drafts] Recommend non-zero values for footgun TPs (#1806)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bac98cbcfdc0_7b993ff9d10d45c095835a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/jcsKrj17Um-PuO2Vctjzbk8-8RQ>
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, 27 Sep 2018 08:46:08 -0000

kazuho commented on this pull request.



> @@ -261,16 +261,23 @@ the stream management.
 All client-initiated bidirectional streams are used for HTTP requests and
 responses.  A bidirectional stream ensures that the response can be readily
 correlated with the request. This means that the client's first request occurs
-on QUIC stream 0, with subsequent requests on stream 4, 8, and so on. HTTP/QUIC
-does not use server-initiated bidirectional streams. The use of unidirectional
-streams is discussed in {{unidirectional-streams}}.
+on QUIC stream 0, with subsequent requests on stream 4, 8, and so on. In order
+to permit these streams to open, an HTTP/QUIC client SHOULD send non-zero values
+for the QUIC transport parameters `initial_max_stream_data_bidi_local`. An
+HTTP/QUIC server SHOULD send non-zero values for the QUIC transport parameters
+`initial_max_stream_data_bidi_remote` and `initial_max_bidi_streams`.

I do not oppose to your point.

What I am looking for is a general guidance that is similar to what we have in RFC 7540, quote: _”It is recommended that this value be no smaller than 100, so as to not unnecessarily limit parallelism.”_

-- 
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/1806#discussion_r220840431