[quicwg/base-drafts] Why is the crypto stream not subject to connection flow control (#800)
Subodh Iyengar <notifications@github.com> Wed, 27 September 2017 22: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 5E2CF135168 for <quic-issues@ietfa.amsl.com>; Wed, 27 Sep 2017 15:45:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.402
X-Spam-Level:
X-Spam-Status: No, score=-0.402 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_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 WORP9xVPjvH9 for <quic-issues@ietfa.amsl.com>; Wed, 27 Sep 2017 15:45:11 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 71D06135166 for <quic-issues@ietf.org>; Wed, 27 Sep 2017 15:45:11 -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=mzW8eLe6nbBFyBeuTQWuIYR4ht4=; b=w8uGT//0W1hVZeNM srkbKBnuBAi4Dnqlf24ugrHnhokMvw6pd1T6jVpdSa4BRJolzNO2K0BvJm9lE6Kw 1spKxLqIB7CX0NtEg3oIXiSvouMYLWS1k2wowAWfJoH9xyVwX5Y6unzbiHdtx8X6 mSugn3gTUeBVQGOfm0qGs9EhjQg=
Received: by filter1080p1mdw1.sendgrid.net with SMTP id filter1080p1mdw1-21030-59CC29F6-F 2017-09-27 22:45:10.491375834 +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 ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id 64crcSJPRFG7QcWc49vsUA for <quic-issues@ietf.org>; Wed, 27 Sep 2017 22:45:10.445 +0000 (UTC)
Date: Wed, 27 Sep 2017 22:45:10 +0000
From: Subodh Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf9fee91f7e47f10448b846f6070d6340a27f534992cf0000000115e3ebf692a169ce0f90b19d@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@github.com>
Subject: [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_59cc29f64f997_4c313fec98db0f2893871"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: siyengar
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2exeWSiFTbLy/y3UqhcvYNJdVOlsDT80Qf3J HbdCfDvoLEHavJDegq/xv35nh2xktfAXARR/GmNe6iA0m63O07JuiaBbVdWWjsZ7qSnIeCsj2GxZyg vZzRvQPFwxCDrG+lQ6xeVNGdY91wlZ0KuRdPrX8FbPAN8V7nzRsHwMpq97+/6jCM0yjhgP83FzVbq0 k=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/VsCsjAl7ZQgZbWOPud5LLesSTCc>
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 22:45:12 -0000
IIRC previously this was not done because flow control messages for the connection were sent on the stream 0. However with MAX_DATA frames they are not sent over stream id 0 any more. Having only crypto streams not be subject to connection level flow control creates a bunch of workaround code to check for if (stream == cryptoStream) before you increment the cumulativewritedataoffset for the connection which is used to track conn flow control. -- 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
- [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