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

Marten Seemann <notifications@github.com> Sat, 01 December 2018 02:14 UTC

Return-Path: <noreply@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 2F96012D4EF for <quic-issues@ietfa.amsl.com>; Fri, 30 Nov 2018 18:14:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.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_HI=-5, 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 iIxm4KAije00 for <quic-issues@ietfa.amsl.com>; Fri, 30 Nov 2018 18:13:59 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8D4D1293FB for <quic-issues@ietf.org>; Fri, 30 Nov 2018 18:13:58 -0800 (PST)
Date: Fri, 30 Nov 2018 18:13:58 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543630438; bh=qZHWt5S4V3Mdehyi0iqu4B6dbo5IaEAANZTI0Cgus60=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QRm78mpG+pXNsUZdQ12tPyly6k6GuYKo2i4mXhB1cW7hyrJ0raUQFb9kRhegxK0CZ djit4ExQ9zWO2JoAC3NOD11cDTS53KiBh99i0/DLa6iaf2ss2NqxNiCNwQHp7NC2Ni B/JTPcASwOXBor+xHLSvleEWh/eTboc/ASgornuQ=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe693f947b62beb38725874c94ee428cc569832df92cf000000011819b06592a169ce17082871@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/443391030@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_5c01ee65f3f89_b9e3f8d652d45c4342594"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/0V7O8UJ1bGGb4egHOlUN6HwuGyA>
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: Sat, 01 Dec 2018 02:14:00 -0000

We discussed this in #1612 and decided to not prohibit this. 

-- 
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-443391030