Re: [quicwg/base-drafts] Why is the crypto stream not subject to connection flow control (#800)
Martin Thomson <notifications@github.com> Wed, 27 September 2017 23:00 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 0E688135170 for <quic-issues@ietfa.amsl.com>; Wed, 27 Sep 2017 16:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 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_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 TaLFLyjodcuy for <quic-issues@ietfa.amsl.com>; Wed, 27 Sep 2017 16:00:35 -0700 (PDT)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 93AEA1344A9 for <quic-issues@ietf.org>; Wed, 27 Sep 2017 16:00:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=+SQfwsygDcqkKs9TaTSHoh+GEWU=; b=V7WlINGL5cq1MXc5 xVXwqfMQTg4r+5qp232MyZ5rtqxQIiC4xTLXSoLc/NAn0IAYrLh7q3H2yUVWf+Pt wEn7YWZUdRuaTQDgdLjvy/3rZ9mC4BZXQy2b6mbprRWmFOLdLqMnJDYM5Mw7y+RS 3yIuLzdkY1om9fIeaJpSE+lclS8=
Received: by filter0943p1mdw1.sendgrid.net with SMTP id filter0943p1mdw1-1150-59CC2D90-25 2017-09-27 23:00:32.621537966 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id tvkOAY7cSTif3H3YaDhqkA for <quic-issues@ietf.org>; Wed, 27 Sep 2017 23:00:32.578 +0000 (UTC)
Date: Wed, 27 Sep 2017 23:00:32 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abade72861778c3582609a55ae4cf276730c723c9c92cf0000000115e3ef9092a169ce0f90b19d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/800/332679382@github.com>
In-Reply-To: <quicwg/base-drafts/issues/800@github.com>
References: <quicwg/base-drafts/issues/800@github.com>
Subject: Re: [quicwg/base-drafts] Why is the crypto stream not subject to connection flow control (#800)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59cc2d9054717_1b80d3fa219324f38535c"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1/fDQ06LhYGPHPcIGFLju46dphRk+v6Th1xj pKuwXjjXicEoLLODQbY4KznlpbW7Sr0/MgXTVGhcaASsnucqPy0OcDjte9FTaQHE1ufuAeuZau6wOG nhuNfFp+ntvJshoBTagYyKcDEwIZdQEcup1fXmWjRJ/j+lEC/4V295BH4ZJC5XZprL7zj5KFdCB4Au w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/LV-kgNml_Egc0WpNrgBdGVGzOhE>
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: Wed, 27 Sep 2017 23:00:37 -0000
The problem is early data and the handshake. It is possible that early data will exhaust the connection flow control window. I fact, that's a feature: we use the connection flow control window to limit the amount of early data, just as there is an early data limit in TLS. If that happens, there is no room to send the client Finished (and Certificate[Verify]). That would block handshake completion, which is bad. Also, the server doesn't really have a good way to send authenticated MAX_DATA frames to the client at this point, so it doesn't easily resolve itself. Yeah, it's a real pain. Stream 0 is too special for my liking also. -- 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/800#issuecomment-332679382
- [quicwg/base-drafts] Why is the crypto stream not… Subodh Iyengar
- Re: [quicwg/base-drafts] Why is the crypto stream… Martin Thomson
- Re: [quicwg/base-drafts] Why is the crypto stream… Martin Thomson
- Re: [quicwg/base-drafts] Why is the crypto stream… Subodh Iyengar
- Re: [quicwg/base-drafts] Why is the crypto stream… janaiyengar