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)

janaiyengar <notifications@github.com> Tue, 04 December 2018 01:18 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 440AF130DCE for <quic-issues@ietfa.amsl.com>; Mon, 3 Dec 2018 17:18:39 -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 lNxpyYlMy-V7 for <quic-issues@ietfa.amsl.com>; Mon, 3 Dec 2018 17:18:38 -0800 (PST)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC119130DBE for <quic-issues@ietf.org>; Mon, 3 Dec 2018 17:18:37 -0800 (PST)
Date: Mon, 03 Dec 2018 17:18:37 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543886317; bh=/kIvjTPmrF23aiDoqZjk5Ct9wpFwr4ZPo4jqx+1DM8c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=twiDUkRwaxjYWHfQxbNpRi0y68nKZrKbATIa7WJjrKfBinwI5BlfRDSsO/g2TyI5N 9BN4Uc7UujLh79YFIg/tFDnwKijn7h8DvtJGFmWVw45cekPtO+2WPV1r9V+bieNxay bMNl+v/saG0W2m/zSG0UaVeq4BIsEvOcREXbparY=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab613e0549c59b3b79e288e81d22ff92a7fa9758e092cf00000001181d97ed92a169ce17082871@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/443932966@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_5c05d5ed1185c_75a73ff1ea2d45bc270295"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/QA2GIk2VmhBMpHNOiacEEbnJNSE>
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: Tue, 04 Dec 2018 01:18:39 -0000

@ekr: Is the text you've proposed above your suggested rewording? That's not enough, because it doesn't capture what the sender needs to do when it receives a frame out of order. I'm happy to put together a PR but I'm not sure what you are after.

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

v2.23.0 | Report a Bug | By Email