[quicwg/base-drafts] Recommend autotuning (#2083)

ekr <notifications@github.com> Sat, 01 December 2018 02:07 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 []) by ietfa.amsl.com (Postfix) with ESMTP id AA97612D4EF for <quic-issues@ietfa.amsl.com>; Fri, 30 Nov 2018 18:07:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id v42AlwWUTvv0 for <quic-issues@ietfa.amsl.com>; Fri, 30 Nov 2018 18:07:33 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3681129C6A for <quic-issues@ietf.org>; Fri, 30 Nov 2018 18:07:32 -0800 (PST)
Date: Fri, 30 Nov 2018 18:07:31 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543630051; bh=mnxWlQB+chn3H4ISd2hWv8LJFpWDkw7jDdAgwdclOCs=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=CDDBz0AQIhx/ZcTmE1aX+gjYXr6+0xoTfKZYAe7I9+MNmfk4632WcCjvx6/jpvp/a KTWGJnH/eA+VhiXBeLjmazWJLbkUnWKC7rKQPQB4k9CsofD7Ndh+2CeFZv1Jnr6jz+ 3+MNFMskG6VrNxIWoN9PiDYCPSJPxExWfHL/+Y7o=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab95074b2d08bba2bd249d03d68c197d6a8c6e0f0792cf000000011819aee392a169ce17082968@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2083@github.com>
Subject: [quicwg/base-drafts] Recommend autotuning (#2083)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c01ece374f4a_7e5c3fb00b6d45c04053ae"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/BaorgVt25zv4-DAK0AMxgO07dSw>
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: Sat, 01 Dec 2018 02:07:35 -0000

This document leaves when and how many bytes to advertise in a MAX_STREAM_DATA
or MAX_DATA frame to implementations, but offers a few considerations.  These
frames contribute to connection overhead.  Therefore frequently sending frames
with small changes is undesirable.  At the same time, larger increments to
limits are necessary to avoid blocking if updates are less frequent, requiring
larger resource commitments at the receiver.  Thus there is a trade-off between
resource commitment and overhead when determining how large a limit is

A receiver MAY 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

In light of the first paragraph which says that I can do whatever I want, what is the purpose of this MAY? It seems like you should either recommend that people do this or just remove the normative language.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: