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

Lucas Pardue <notifications@github.com> Wed, 18 July 2018 18: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 BA4FA130F69 for <quic-issues@ietfa.amsl.com>; Wed, 18 Jul 2018 11:18:48 -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 mcbjWYQKWJXq for <quic-issues@ietfa.amsl.com>; Wed, 18 Jul 2018 11:18:42 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C11BC131004 for <quic-issues@ietf.org>; Wed, 18 Jul 2018 11:18:37 -0700 (PDT)
Date: Wed, 18 Jul 2018 11:18:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1531937917; bh=PCIPeovWkwLsLgkaA49QwdrO5yuWfz6qyCbJxWMzb2s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=flIK4doiyHfirWaCb1nMaPdzofHcYhmj39A8KJp0mZWE3Ed9mXrvDMoBZEim3oCub qXj/yrjdh+0p3R80l0GZrPeIDZijfTNtSPGkPj3r5oUCG/6vehyivXzFULQ1WXipc3 Aydft8mXBEWILf4Z6YC8jvCAQhHn6gVRoVpfOMm8=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1b0788733635dae6f3d72724a729a27160c4decb92cf000000011767467d92a169ce1467cce7@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/406026704@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_5b4f847d208dd_446f3fce058bef801639f4"; 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/g8kewSMp0I1qQOLRfrBY4RpinxA>
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: Wed, 18 Jul 2018 18:18:54 -0000

I'm not suggest, this is what the current text implies (from Section 9). 

> HTTP/QUIC can rely on QUIC’s own PADDING frames or employ the reserved frame and stream types discussed in Section 4.2.1 and Section 3.3.1.

As Martin suggests, it might be better to define an explicit padding stream extension for anyone that actually wants that behaviour (which I think could be useful).

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