Return-Path: 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 D71891201E7 for ; Fri, 12 Apr 2019 17:28:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.002 X-Spam-Level: X-Spam-Status: No, score=-8.002 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_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 CQhhVKvz4WIP for ; Fri, 12 Apr 2019 17:28:34 -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 A33AC12008B for ; Fri, 12 Apr 2019 17:28:34 -0700 (PDT) Date: Fri, 12 Apr 2019 17:28:33 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1555115313; bh=iWHBv2rtI6CxzLCmroZg3GXpH7AaaPP+qKoZkvUB8io=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wbaV9v9bq0Br7ywQF0H1W96UcqB0Vf97daxk7e3nZR8g1OXlgPRtX6JKA3jPxJcaf rkid73z1Ba2vc/xMq3pkeicU1dkDh6pwrHNX6OI9Fm2ubx98qVO8uXsIudu3ySvXD9 iwvDYCJHMki+TF5anq0wsY7bguS76tgPuCs7NgmY= From: Marten Seemann Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Add further guidance related to unidirectional stream TPs (#2612) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5cb12d317e965_289c3fc648ad45b4578226"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: marten-seemann X-GitHub-Recipient: quic-issues X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org Archived-At: X-BeenThere: quic-issues@ietf.org 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: Sat, 13 Apr 2019 00:28:37 -0000 ----==_mimepart_5cb12d317e965_289c3fc648ad45b4578226 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit marten-seemann commented on this pull request. > @@ -321,8 +321,19 @@ defined in this document: control streams ({{control-streams}}) and push streams ({{push-streams}}). Other stream types can be defined by extensions to HTTP/3; see {{extensions}} for more details. -Both clients and servers SHOULD send a value of three or greater for the QUIC -transport parameter `initial_max_uni_streams`. +The performance of HTTP/3 connections in the early phase of their lifetime is +sensitive to the creation and exchange of data on unidirectional streams. +Endpoints that set low values for the QUIC transport parameters +`initial_max_uni_streams` and `initial_max_stream_data_uni` will increase the +chance that the remote peer reaches the limit early. In particular, the value +chosen for `initial_max_uni_streams` should consider that remote peers may wish +to exercise reserved stream behaviour ({{stream-grease}}). Limits can be +increased post handshake at the cost of additional RTT, for example by +exchanging `STREAMS_BLOCKED` and `MAX_STREAMS` QUIC frames. To reduce the There's nothing you can do to force a peer to allow more streams. If a peer continues to misbehave, all you can do is close the connection. STREAMS_BLOCKED is just a debugging frame, so I agree with @ianswett that we should remove it from this PR. -- 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/2612#discussion_r275096535 ----==_mimepart_5cb12d317e965_289c3fc648ad45b4578226 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@marten-seemann commented on this pull request.

In draft-ietf-quic-http.md:

> @@ -321,8 +321,19 @@ defined in this document: control streams ({{control-streams}}) and push streams
 ({{push-streams}}).  Other stream types can be defined by extensions to HTTP/3;
 see {{extensions}} for more details.
 
-Both clients and servers SHOULD send a value of three or greater for the QUIC
-transport parameter `initial_max_uni_streams`.
+The performance of HTTP/3 connections in the early phase of their lifetime is
+sensitive to the creation and exchange of data on unidirectional streams.
+Endpoints that set low values for the QUIC transport parameters
+`initial_max_uni_streams` and `initial_max_stream_data_uni` will increase the
+chance that the remote peer reaches the limit early. In particular, the value
+chosen for `initial_max_uni_streams` should consider that remote peers may wish
+to exercise reserved stream behaviour ({{stream-grease}}). Limits can be
+increased post handshake at the cost of additional RTT, for example by
+exchanging `STREAMS_BLOCKED` and `MAX_STREAMS` QUIC frames. To reduce the

There's nothing you can do to force a peer to allow more streams. If a peer continues to misbehave, all you can do is close the connection.
STREAMS_BLOCKED is just a debugging frame, so I agree with @ianswett that we should remove it from this PR.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5cb12d317e965_289c3fc648ad45b4578226--