IETF Logo Mail Archive

Re: [quicwg/base-drafts] Why ignore MAX_STREAM_DATA or MAX_DATA that don't increase the flow control limits (#2082)

ekr <notifications@github.com> Mon, 03 December 2018 20:01 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 E35C7130F99 for <quic-issues@ietfa.amsl.com>; Mon, 3 Dec 2018 12:01:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.46
X-Spam-Level:
X-Spam-Status: No, score=-4.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 LiXupX9PGo4q for <quic-issues@ietfa.amsl.com>; Mon, 3 Dec 2018 12:01:29 -0800 (PST)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 D1437130EBF for <quic-issues@ietf.org>; Mon, 3 Dec 2018 12:01:27 -0800 (PST)
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=T7r7Tt+l7GAyzwUK9seng3Ehono=; b=J9moApueg7XK7uVc i1GsKjGGpc+HRd4j+abioeoc1WM2Cqz7xeWafxfwxr2PNIdZICjAlCTMpxeJWRRv 00fbjs6WYwxStp7+Dh/g51SPI/pw+ibYOatILfYLUTQbJE8msACfCNBkrcgq+Pks znssdOF4Yik3AI4IAOq5iZ6JTRg=
Received: by filter0287p1iad2.sendgrid.net with SMTP id filter0287p1iad2-5062-5C058B92-4D 2018-12-03 20:01:22.83270536 +0000 UTC m=+323858.472180751
Received: from github-lowworker-cef7735.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0030p1iad2.sendgrid.net (SG) with ESMTP id gw8s-jIhShe96wIt98WQsg for <quic-issues@ietf.org>; Mon, 03 Dec 2018 20:01:22.824 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-cef7735.cp1-iad.github.net (Postfix) with ESMTP id B969D1E1466 for <quic-issues@ietf.org>; Mon, 3 Dec 2018 12:01:22 -0800 (PST)
Date: Mon, 03 Dec 2018 20:01:22 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe730bffa73ba08a665a4384ebf08431de863551292cf00000001181d4d9292a169ce17082871@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2082/443849879@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2082@github.com>
References: <quicwg/base-drafts/issues/2082@github.com>
Subject: Re: [quicwg/base-drafts] Why ignore MAX_STREAM_DATA or MAX_DATA that don't increase the flow control limits (#2082)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c058b92b816c_118b3fbe52cd45c42911df"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3kv1q+g5SIPWDsObN3OaQFzuK+FhpE2/JF8n cJ07+fmn2DdkVB0liiq2UJQzQwTx8yFAJy36va0N3+CMLDBhHv2N/MFSa9ZQljkRi+fyBOYh0BioEM u7KT5UHOUz/oyYG0Y8uMfigOjJPzySPKLwL8Z0E79C3JtZACuVjuHF4FNQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ix62SiYFpioIObOJZGE9fEYE2O4>
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: Mon, 03 Dec 2018 20:01:37 -0000

I don't find this persuasive, but as I said, I recognize I'm in the rough. Regardless, if that's the behavior we want, the text needs some rework

-- 
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/2082#issuecomment-443849879

v2.23.0 | Report a Bug | By Email