[quicwg/base-drafts] Server might be unable to complete handshake due to MAX_STREAM_DATA (#725)

Martin Thomson <notifications@github.com> Fri, 11 August 2017 10:28 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 C3FA81275FD for <quic-issues@ietfa.amsl.com>; Fri, 11 Aug 2017 03:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.596
X-Spam-Level:
X-Spam-Status: No, score=-0.596 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_28=1.404, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 IDFNRMnyIbj6 for <quic-issues@ietfa.amsl.com>; Fri, 11 Aug 2017 03:28:25 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 8C5E91241F5 for <quic-issues@ietf.org>; Fri, 11 Aug 2017 03:28:25 -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=zoIGLpWDRDAsEQvtbskE/qEK+kA=; b=pEqOUseRLwYb2o+u GgKCu1DzYbrtU95GdE7Iaw+1EnySMSOWsCnGrphSXUuRDcdLnyJ0zhyBxglR5UBP pItovr2IjZB4cGG7m8d+ZHbJM8JrWczHlRa/uikIOw1fr1+nm2liqrsgiCGO2p7X L+pRGCEeZRYJTToRU0C9VyQu2dQ=
Received: by filter0939p1mdw1.sendgrid.net with SMTP id filter0939p1mdw1-6921-598D86C6-69 2017-08-11 10:28:22.833254691 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id gu7JoybwRiyzl-tAN4gulg for <quic-issues@ietf.org>; Fri, 11 Aug 2017 10:28:22.870 +0000 (UTC)
Date: Fri, 11 Aug 2017 10:28:23 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd7161eff17def2c5dba1d6ec2216641c2e26372592cf0000000115a548c692a169ce0ee08745@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/725@github.com>
Subject: [quicwg/base-drafts] Server might be unable to complete handshake due to MAX_STREAM_DATA (#725)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_598d86c6bb55d_2c963f9de5e97c2c359fc"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak31vBfKa+cJPezX6wlPmo2u437OUnurxiA90n lbZ40OKYX7huR3P0JTX5YCIw9loyEH1YDhsDIyUJYlOm9K7gcJGkcqQ/RdrN+Z252Z748i+EZjxDlW JXy5hBoCDZXxDB4xy/g0WN/PxpKh2NNaKM+tFn75jHY7iecfy746HKCzUJDTgZE4ixjJHKTOoezow+ s=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/rOIPreJaOHfyYBCWKhhnqulbVeY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 11 Aug 2017 10:28:27 -0000

MAX_DATA doesn't apply to stream 0, but MAX_STREAM_DATA does.  The server can increase the space available for the second flight of client handshake messages, but the client can't increase the space available to the server.  The initial value (in the client's transport parameters) determines how much space the server has to send.

Is this a problem?  should we exempt stream 0 (maybe just until the handshake completes)? or should we just advise against setting the value too low?

Note that the value is immutable, if a client wants a low value for general use, that might be a problem for the handshake.  I'm inclined to say that stream 0 can exceed the limit up until the point that the handshake completes, after which the limit strictly applies.  Then, if it has exceeded the limit, the server can't send anything until the client gives it more budget.

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