Re: [quicwg/base-drafts] MAX_DATA doesn't comply with MAX_STREAM_DATA (#1812)

Mike Bishop <notifications@github.com> Fri, 28 September 2018 21:47 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 62FEF127148 for <quic-issues@ietfa.amsl.com>; Fri, 28 Sep 2018 14:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.456
X-Spam-Level:
X-Spam-Status: No, score=-8.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, 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 0MqkBfxhxrEH for <quic-issues@ietfa.amsl.com>; Fri, 28 Sep 2018 14:47:53 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D51B130E66 for <quic-issues@ietf.org>; Fri, 28 Sep 2018 14:47:53 -0700 (PDT)
Date: Fri, 28 Sep 2018 14:47:52 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538171272; bh=NnSmt/eadXrTLr/L9KBkj3OW3DgtcTquOgZCsiV/Wfc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=op13x2OMyzYDlUEv9cR01kVJsKNyXSuoyH/cqRkftvzeGy9cWjjWUEjIMl2ydaYwc 9cXRGDisIVXd5QXDyrmu88C8HV6eQFBDmxa6tZGXIr4vNL/QaeG/dW4JE5mTkJ7yUa DdWpxmCa1J5XaCoMexfhIjbWtcEesePIu7Ombiio=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbfe0f83c63416bac9abcc6695c40851f3d5a7c4b92cf0000000117c6638892a169ce15c2187c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1812/425575377@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1812@github.com>
References: <quicwg/base-drafts/issues/1812@github.com>
Subject: Re: [quicwg/base-drafts] MAX_DATA doesn't comply with MAX_STREAM_DATA (#1812)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5baea1885ac57_39be3f8b23cd45b8209822"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/DtnxpXWM87g9ACBkfgwt7M64Vk4>
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: Fri, 28 Sep 2018 21:47:56 -0000

That's not misbehavior, it's reflecting the fact that stream- and connection-level flow control may have different constraints.

-- 
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/1812#issuecomment-425575377