IETF Logo Mail Archive

Re: [quicwg/base-drafts] Pacing when under-utilizing the Congestion Window (#2686)

Gorry Fairhurst <notifications@github.com> Wed, 22 May 2019 14:52 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 CB617120170 for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 07:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level:
X-Spam-Status: No, score=-1.392 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 mVEQl1UkkkXO for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 07:52:56 -0700 (PDT)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B7ED120074 for <quic-issues@ietf.org>; Wed, 22 May 2019 07:52:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=eWwkuud1l97Ez5q/zK0EZj7GCAM=; b=Cktr6/5ERdjxY0/t By4j+fnSvjwPk9DMk1XnM864oRpSh22xow/UnhyJqXsB6w8qzjoVCifeH4dgnD1D /VUmYwO0Oq3eDSGKQD8GhAKsadb2odPDzPVQjrfnwxfuEHpTCOxHMEIkaHC/VrlJ 2tZNM2ZIqpw70dn30h+vFdMu5Jg=
Received: by filter1668p1mdw1.sendgrid.net with SMTP id filter1668p1mdw1-21909-5CE56246-18 2019-05-22 14:52:54.814985184 +0000 UTC m=+140830.580905540
Received: from github-lowworker-1c220e1.cp1-iad.github.net (unknown [140.82.115.6]) by ismtpd0036p1iad1.sendgrid.net (SG) with ESMTP id 3dMXOiEwRZOcX84b_vpVkQ for <quic-issues@ietf.org>; Wed, 22 May 2019 14:52:54.707 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-1c220e1.cp1-iad.github.net (Postfix) with ESMTP id 9FD1C160028 for <quic-issues@ietf.org>; Wed, 22 May 2019 07:52:54 -0700 (PDT)
Date: Wed, 22 May 2019 14:52:54 +0000
From: Gorry Fairhurst <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6FZROXJE3BL27B2L526KKMNEVBNHHBUYOIOQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2686/494837702@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2686@github.com>
References: <quicwg/base-drafts/issues/2686@github.com>
Subject: Re: [quicwg/base-drafts] Pacing when under-utilizing the Congestion Window (#2686)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce562469cc46_560c3ff6db2cd96023162b0"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1HDiYVWp2TTyf7EyseWwXQfQuxmpb+ojiWbd 8XzsGcaiyFsx/eLlSOVL4umFFvvdrh2Cc5ekAMfmyUG4RHAdPtle2XhHRajMdqk1qvfeCWgSD9Nq0r nV0F8aRFW3toGh/J6cdD8kCYscXk8zuKtNkbJtajmDae01mtXpJYrUvhhD4XOXIz2d9OWPeCQl5qVX w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/8H9RvXKPQZtvLCV7yrt2HZe1qmU>
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: Wed, 22 May 2019 14:52:58 -0000

I'm not advocating a max burst size of 4 (although I do believe this is safe, other sizes larger may also be safe), however my thought was that the draft infers IW as a safe size to burst - I don't know that this is always true - especially if we look to the future use of a larger IW. You could (I think you do) argue that IW is an upper bound to this safe burst size without pacing.

I will try just a little more: 
• I think we **should** limit the cwnd when coming out of an app-limited period. 
• I think we should limit a burst <= some size or that pacing is needed, or if not then it MUST (!) reduce to a safe IW.

Does that help?

-- 
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/2686#issuecomment-494837702

v2.23.0 | Report a Bug | By Email