IETF Logo Mail Archive

Re: [quicwg/base-drafts] hq: Does ignored data/frames cause flow control updates? (#1580)

Lucas Pardue <notifications@github.com> Fri, 20 July 2018 17:28 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 9F222130F90 for <quic-issues@ietfa.amsl.com>; Fri, 20 Jul 2018 10:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, 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 KPBnAGB0qaay for <quic-issues@ietfa.amsl.com>; Fri, 20 Jul 2018 10:28:02 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03F13130F74 for <quic-issues@ietf.org>; Fri, 20 Jul 2018 10:28:02 -0700 (PDT)
Date: Fri, 20 Jul 2018 10:27:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1532107679; bh=f5HXloIy+/gFK0P9+MQduur8b0Ttua2MOcSLtMY4LJk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KfkOoK0vtVDHk4KU4Xp/yMXoSu5j9H0F2Tk2htvgrDBwqXGwXbj9MF6Xc3nxd8xr1 sU3SUaOv1iTALsWRvRbDGS+VkxjWEzF0uw7Uk97eYjR7zz6O6SH5jir7tXL/OcpDDs ZgWEEvXIzv122mT+yWZ4MsvCIhnNaZKNIcZvaRIA=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbd63ef729448fd8789268a00ed7e6f4a622c765692cf000000011769dd9f92a169ce1467cce7@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1580/406670552@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1580@github.com>
References: <quicwg/base-drafts/issues/1580@github.com>
Subject: Re: [quicwg/base-drafts] hq: Does ignored data/frames cause flow control updates? (#1580)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b521b9feffb0_6cd23fcf92ebe6185393a9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/zXETuJ1iLYwnDaNdNhzGQ8-zTd0>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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, 20 Jul 2018 17:28:05 -0000

So perhaps my understanding of ignoring is misaligned. I'd write a client that doesn't close a read stream (for unidirectional reserved streams) and just carry on telling the transport layer I processed the data when in fact I did nothing with it. From transport layer perspective I suppose I handled it..

-- 
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/1580#issuecomment-406670552

v2.23.0 | Report a Bug | By Email