Re: [quicwg/base-drafts] How long idle is idle? (#2138)

ianswett <> Thu, 13 December 2018 14:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6E45B1252B7 for <>; Thu, 13 Dec 2018 06:14:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.056
X-Spam-Status: No, score=-3.056 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_IMAGE_ONLY_28=1.404, 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 b9_LLCmOgyDO for <>; Thu, 13 Dec 2018 06:14:43 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D0058124408 for <>; Thu, 13 Dec 2018 06:14:42 -0800 (PST)
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=aiWP6UR1MGU0FvJcPLAOxGcsGgo=; b=uI5tNYMpwKUqE55U 0pZWz5ZshoUz8+lBstNAWS5Nczrfa2q1KvZsQOo3NNolZXxOQwKvgArkSgjH9fyL sgk9zDbodRzgsQvPm2R+BMquYtCAwunFX8QbE4+rShmYIsCGyhraX/SKI2aAmE0k wwBBmCLZXF5Z2K8PmfmwH9UO3P4=
Received: by with SMTP id filter0008p1iad2-32705-5C12694B-11 2018-12-13 14:14:35.123310255 +0000 UTC m=+226478.316806159
Received: from (unknown []) by (SG) with ESMTP id TGOMuwPEQS-wzRla4lXjhA for <>; Thu, 13 Dec 2018 14:14:35.172 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 21FFB80316 for <>; Thu, 13 Dec 2018 06:14:35 -0800 (PST)
Date: Thu, 13 Dec 2018 14:14:35 +0000 (UTC)
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2138/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] How long idle is idle? (#2138)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12694b205b1_b3b3fa0502d45bc19761d"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0WG4bTswxkvJynpwAIm+msBjjNPKXUz9NX/1 N5Xyqq2A/AIt670dzguIbYfbllDFEMGTyoq1IK9TRvHwit4qgVv9KPl4pcQV1D4POdmd+27XxDksIf Aa5LezyfUgh384woZ7rEuX1aFYd4eUE4YXYRDRf35RdoOkrNOfKbo8CJt/j8ZS1PdVPfMOgB+U1XTv 8=
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: Thu, 13 Dec 2018 14:14:46 -0000

The intent is this is triggered after an idle period of any length.  As it says in the draft, the reason is to limit bursts into the network.

It turns out bursting 100 packets at once into the network almost always causes losses, and two solutions are pacing and resetting the CWND to a lower value out of idle and allowing ack-clocking to smooth the flow.

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