Re: [quicwg/base-drafts] Congestion control during application limited state (#2554)

ianswett <> Mon, 08 April 2019 15:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D36CE1200C3 for <>; Mon, 8 Apr 2019 08:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Status: No, score=-3 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id m911zZYN-HgP for <>; Mon, 8 Apr 2019 08:28:24 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0B42F120174 for <>; Mon, 8 Apr 2019 08:28:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; 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=8MU3J6/AQw7FH+lEea1Irj3F0W0=; b=LwBIiBM3AMYzkgzj Bee0S5bSaXvaOeeqU0nazccVrM/dOo20pN3yTGsi6fLyUsPs7cYcFIaS4htwTCxJ MXSmocJQwxCzKEjIwonlb95qObcil6aoUcKts1znVl5U2P+rKAyDrKuUqznmx+jc kfqPliRvTq4NpJpjpy4ssztxGU4=
Received: by with SMTP id filter0414p1iad2-22640-5CAB6897-7 2019-04-08 15:28:23.120866264 +0000 UTC m=+13517.692026184
Received: from (unknown []) by (SG) with ESMTP id Z3xCmMD-RB-09b2qH1W92A for <>; Mon, 08 Apr 2019 15:28:22.954 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id D5F2EC0968 for <>; Mon, 8 Apr 2019 08:28:22 -0700 (PDT)
Date: Mon, 08 Apr 2019 15:28:23 +0000
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2554/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Congestion control during application limited state (#2554)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cab6896cf481_d3f3f801bcd45bc1253ca"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0aUQ5msX9MMO5aq3qe5X3CeGG4ADHLrfr14G GQrhY8pdDoGG9MYR/Mr9vH5uUbdXZGMGm686WVSj+d/+ZOy8IKM/XnnqbeMEH/h2HPMw2VOLXyf4j7 4GUNrskU43PE+jQzlwPwdWXROCn0KCPruBTGtGCzkjWQ0QueYoz83s1sWQ==
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Apr 2019 15:28:26 -0000

I found this in RFC4960(
"When cwnd is less than or equal to ssthresh, an SCTP endpoint MUST
      use the slow-start algorithm to increase cwnd only if the current
      congestion window is being fully utilized, an incoming SACK
      advances the Cumulative TSN Ack Point, and the data sender is not
      in Fast Recovery.  Only when these three conditions are met can
      the cwnd be increased; otherwise, the cwnd MUST not be increased."

The current QUIC recovery text tries to clarify what fully utilized means, particularly in the presence of pacing.

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