IETF Logo Mail Archive

[quicwg/base-drafts] H3 spec fails to warn about initial_max_stream_data_uni (#2589)

Christian Huitema <notifications@github.com> Thu, 04 April 2019 02:45 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 90AB51200F1 for <quic-issues@ietfa.amsl.com>; Wed, 3 Apr 2019 19:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.597
X-Spam-Level:
X-Spam-Status: No, score=-1.597 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_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 fR3E-S54d5Sq for <quic-issues@ietfa.amsl.com>; Wed, 3 Apr 2019 19:45:51 -0700 (PDT)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C1A01201D8 for <quic-issues@ietf.org>; Wed, 3 Apr 2019 19:45:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=G+QXvE3eQa9QkYyRF4ntMJUldwI=; b=b2R/qFfWlbPYE6f4 kbQY5Jzrrs79wsjBy3lCQPuYx2JiMcWdhpx5AQByGSg8xhnnf8OhW/nQQHmeHzVY p3adB+HlMgZPi9Y4IYiCRhh1hYvEsdIPHKBl8gUwxKYcJlmRAIMv1YM1K7vwXMFg ZjnATHz4YprU6XvgATNXOR14VTk=
Received: by filter0368p1iad2.sendgrid.net with SMTP id filter0368p1iad2-2725-5CA56FDE-B 2019-04-04 02:45:50.225527956 +0000 UTC m=+553282.047247966
Received: from github-lowworker-0c86143.cp1-iad.github.net (unknown [192.30.252.43]) by ismtpd0012p1iad1.sendgrid.net (SG) with ESMTP id txWiLP7BQla1S3YshArDoQ for <quic-issues@ietf.org>; Thu, 04 Apr 2019 02:45:50.214 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-0c86143.cp1-iad.github.net (Postfix) with ESMTP id 325E8240067 for <quic-issues@ietf.org>; Wed, 3 Apr 2019 19:45:50 -0700 (PDT)
Date: Thu, 04 Apr 2019 02:45:50 +0000
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb1462404b5d1cdafe8f25e2ba040aedd3b14382d92cf0000000118bd31de92a169ce1992e751@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2589@github.com>
Subject: [quicwg/base-drafts] H3 spec fails to warn about initial_max_stream_data_uni (#2589)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ca56fde312b8_38d13fdc356d45c4297758"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2XvMF1SFWb/yZyRng/LAdnPYkfNQRsLPAFVQ MTz+S30V61Y8sni32eJt2UIyUnZnsvI4cEQMXltgxU0LCpIWZHHRXjpZXGyaU3sQUcEAXy9d/gveyA wmSkdc6qwTAvTQ43otuKAuwedTBSKp/K5rNdhGzPgj3gI6YjIEz2KHbuAuFgmNDhHyB1aq/daH8gyh Q=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/8O8URG6eCeGqTRo_JwBHErYBItE>
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, 04 Apr 2019 02:45:54 -0000

If the transport parameter `initial_max_stream_data_uni` is not set, HTTP 3 will just stall. That's because the HTTP3 implementations are supposed to send the "Settings" before sending any request or response, but they can only do that if there are flow control credits for Uni streams. Of course, the HTTP3 spec says that "Both clients and servers SHOULD send a value of three or greater for the QUIC transport parameter initial_max_uni_streams." But it fails to mention that there should be some sensible value for `initial_max_stream_data_uni`.

The bug was found during interop testing between `picoquic` and `ats`. It really is a spec bug. Section 3.1 of the HTTP3 spec has text stating that _"it is recommended that `initial_max_bidi_streams` be no smaller than 100, so as to not unnecessarily limit parallelism."_ I think that we need similar text in section 3.2.

-- 
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/2589

v2.30.2 | Report a Bug | By Email | System Status