[quicwg/base-drafts] Transport: Flow Control Tuning (#3216)

Gorry Fairhurst <notifications@github.com> Mon, 11 November 2019 17:53 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 91CAE120AF8 for <quic-issues@ietfa.amsl.com>; Mon, 11 Nov 2019 09:53:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 9IkfSiu-8TYW for <quic-issues@ietfa.amsl.com>; Mon, 11 Nov 2019 09:53:37 -0800 (PST)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7D9A120A59 for <quic-issues@ietf.org>; Mon, 11 Nov 2019 09:53:36 -0800 (PST)
Received: from github-lowworker-edec459.ac4-iad.github.net (github-lowworker-edec459.ac4-iad.github.net [10.52.18.32]) by smtp.github.com (Postfix) with ESMTP id 414298C041B for <quic-issues@ietf.org>; Mon, 11 Nov 2019 09:53:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573494816; bh=UoK2y3fJwy8PEn0H5y6lsxmOsViVTbjfwpCJ9WkOJnE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=DIKXTUZYhGz3OrwRlAHD1yNTDW+CgAo0T3CGqk0Q+wXga07G5lMEGKlGQzbr/edwW dau0nbGKkfP37b0+8ZHp4xXta2GxHaNeZaRQrG0B77aO+YEXjcG65L9+SEZ9weqnMS B+NW19wDthmDonfEbmrmN7Hw/MekoZ0Jn0X9ExbU=
Date: Mon, 11 Nov 2019 09:53:36 -0800
From: Gorry Fairhurst <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7YD6J7RLGMUKVFABV323JKBEVBNHHB6D3C4A@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3216@github.com>
Subject: [quicwg/base-drafts] Transport: Flow Control Tuning (#3216)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc9a0203240a_19913fb6008cd96c18458e1"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gorryfair
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/EAvPknNu7_o7bNsSHkzkLzEP3kU>
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: Mon, 11 Nov 2019 17:53:39 -0000

/ A receiver can use an autotuning mechanism to tune the frequency and
   amount of advertised additional credit based on a round-trip time
   estimate and the rate at which the receiving application consumes
   data, similar to common TCP implementations. 
/ 
- I think this has potential for strange pathologies where flow control interacts with ACKs within the transport. I now have at least some data where we have seen problems, from one policy that updated flow control too infrequently. Achieving similar behaviour to TCP could require more than currently stated.


-- 
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/3216