[quicwg/base-drafts] Need a way to send big values in stream 0 (#825)
ekr <notifications@github.com> Tue, 03 October 2017 18: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 9337D133200 for <quic-issues@ietfa.amsl.com>; Tue, 3 Oct 2017 11:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.181
X-Spam-Level:
X-Spam-Status: No, score=-3.181 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_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=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 t9f8PxsAgl9q for <quic-issues@ietfa.amsl.com>; Tue, 3 Oct 2017 11:45:17 -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 4D509133090 for <quic-issues@ietf.org>; Tue, 3 Oct 2017 11:45:16 -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=O6+DfT+lmt/0Dy78S3YI8pE+iIU=; b=hrSh28ZtH1dyPgLR deJPHFkJ+mOuPYMEBo0UOjprYXjRS/RelvBRPKDhGaLFXLp1jq9fxzHCGGq4MGQz lXJ+69o11KfBX7723NGjqNOb8dmo5K4gKxQyz0/n4PkP9WT7iMKL8z84mlNThxdi z/uLr1axLwTA2Ej+sHbCoQhtnzk=
Received: by filter0212p1iad2.sendgrid.net with SMTP id filter0212p1iad2-30575-59D3DABB-E 2017-10-03 18:45:15.330979099 +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 ismtpd0015p1iad2.sendgrid.net (SG) with ESMTP id iFd05Cq4RlqfO6XiVPE6Zg for <quic-issues@ietf.org>; Tue, 03 Oct 2017 18:45:15.322 +0000 (UTC)
Date: Tue, 03 Oct 2017 18:45:15 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe868600fadac5f62fb7c616ede399b3e4238ef3992cf0000000115eb9cbb92a169ce0fa614bd@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/825@github.com>
Subject: [quicwg/base-drafts] Need a way to send big values in stream 0 (#825)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59d3dabb3a64a_37383fe45d8d6f2c3056c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak14yInED04EJ8lTYbcbWVsQ0uS9YPvxdzzHwO F5D61y6P1woGsOWgwuUWsaXwF/2fZfEKu+NW/1rejPCe1IT6b48MPDmPZ2gfTpHKa0EaMgvn2zcapf S0UntasRLwfYmGB5aBG7UQJhNyLL+fHtf6pKN2aaUy+m0+r39BMBq3eDyg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/VdjFH0dA3hAJ_MAMBEb9QBAvqwQ>
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: Tue, 03 Oct 2017 18:45:19 -0000
Currently we have a set of bad properties: - You can't MAX_STREAM_DATA in stream 0 - Stream 0 is stream-level flow controlled - People have big certs When you put these all together, we are going to have problems. There are a number of options: 1. Allow MAX_STREAM_DATA 2. Exempt stream 0 from flow control 3. Prohibit big certs 4. Have a fixed flow control window refreshed by the ACK. -- 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/825
- [quicwg/base-drafts] Need a way to send big value… ekr
- Re: [quicwg/base-drafts] Need a way to send big v… Martin Thomson
- Re: [quicwg/base-drafts] Need a way to send big v… jpinner-lyft
- Re: [quicwg/base-drafts] Need a way to send big v… Mike Bishop
- Re: [quicwg/base-drafts] Need a way to send big v… Mike Bishop