Re: [quicwg/base-drafts] Define "under-utilization" of cwnd (#2630)

Gorry Fairhurst <notifications@github.com> Sat, 11 May 2019 09: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 B242F12012F for <quic-issues@ietfa.amsl.com>; Sat, 11 May 2019 02:28:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 36QUmpZfNj4R for <quic-issues@ietfa.amsl.com>; Sat, 11 May 2019 02:28:26 -0700 (PDT)
Received: from out-18.smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD2A41200FD for <quic-issues@ietf.org>; Sat, 11 May 2019 02:28:25 -0700 (PDT)
Date: Sat, 11 May 2019 02:28:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557566905; bh=L8rfLVgc9ES3F+g06KpxwSNkH28Wbz4XKCB8nkeNJB4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uplkiWbVhdq3V43ARUqGs9/02cLKweL+an8Z5IChQtCaScZunBLYO+fPM5dvpSDsv DYztHa8QJfWeVd+I/5NvLVjPZ00CoIcBeCBkVfqO837J+Crt5msaEDjGzPRW+gD50G MD6snZ440BPgCz7RTAR2hmH+YP9GIgjvz6z+rsAQ=
From: Gorry Fairhurst <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2OOEJN4Y2QO7SQLJN24PEDTEVBNHHBTZE2DQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2630/491495325@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2630@github.com>
References: <quicwg/base-drafts/issues/2630@github.com>
Subject: Re: [quicwg/base-drafts] Define "under-utilization" of cwnd (#2630)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd695b9106ed_6d103fb0fa0cd95c34969a"; 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/Mv46enhP0wZf_OaUdnhF5hkQ7MU>
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, 11 May 2019 09:28:28 -0000

This seems to be digging in the correct place. I think we would agree the aim of some form of cwnd-validation is to stop cwnd growth when there is no growth of inflight data by the upper layer. And I think we'd agree tussle comes when the CC is trying to expand the cwnd - because the upper layer has more data to send, but that doesn't mean cwnd was necessarily fully utilised last RTT.

When would in-flight > cwnd ?


-- 
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/2630#issuecomment-491495325