IETF Logo Mail Archive

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

MikkelFJ <notifications@github.com> Wed, 18 July 2018 17:01 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 1DB97130E05 for <quic-issues@ietfa.amsl.com>; Wed, 18 Jul 2018 10:01:11 -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 qGpJAwvtTI0X for <quic-issues@ietfa.amsl.com>; Wed, 18 Jul 2018 10:01:08 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38E90130DE4 for <quic-issues@ietf.org>; Wed, 18 Jul 2018 10:01:08 -0700 (PDT)
Date: Wed, 18 Jul 2018 10:01:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1531933266; bh=roTCgiuMzRKOrBQF+q2ZwqeMh8XyzG74LeNlQYfgVLg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YmghdAU/UYDNRaLj0iUAGlZMpHQVCL8uO6im9NHDUdakQrAagDxUp8VdIjVc8UBqv ONHl/eX2npj2y6cORcd3v+CW63toiwNi717VxqBHWk+qGm0A3P6DM3absWwujD5Xcv f2ZfWhD8r0dBpNY17Op+OnMiEbR4jEZ4h+V9x9Oc=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab54e6e07b8f9bce41ee1738b9c4473dbb1a1b692892cf000000011767345292a169ce1467cce7@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/406003376@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_5b4f72525bae2_7d453f8b898bef80276258"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/dJ_NS-9auq7h6wIj5tFYy32H8FE>
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 17:01:11 -0000

It's not the transport protocols concern what an app does or does not do with the data.
A std. QUIC api would deliver data in order, but can arrange for data to be delivered out of order to the app and even ignored. It is the primarily the app the knows how much buffer capacity can absorbed but it may flow to the transport in different ways - for example the app can say this range is not important and this range has been received - leaving capacity in the transports receive buffer that it can then use to update MAX.
If this becomes a problem, the app needs to negotiate this with the local app/transport interface but it hasn't got anything to do with the wire protocol.

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

v2.23.0 | Report a Bug | By Email