Re: [quicwg/base-drafts] Restarting from idle (#2023)

ianswett <notifications@github.com> Tue, 20 November 2018 20:21 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 38D1E12D4E9 for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 12:21:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LUdJUH6DmntD for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 12:21:25 -0800 (PST)
Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2261112785F for <quic-issues@ietf.org>; Tue, 20 Nov 2018 12:21:25 -0800 (PST)
Date: Tue, 20 Nov 2018 12:21:24 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542745284; bh=vDvt+BgeBIsKFBzH1cPbeWhG1J7ZRGdhs1SL71G2z3Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MDP9wD7pcENmYLs4Gv+iFYieTTtKofGwco3R+E1Pto5x5/h8qSqFM6oUUgN3apRAW GGrYbUUs1yfa7TgflIPkbK4kog6mLIyDxf89zmHjhl71pF+vMCv2DoH9eB11QWAf3A o5/bCK9S+XxvJESOtb2/QGxln7DuZH3/DAMgLKfc=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba38aca22a79b6ee2479a80ce7e5de8ae1b6dd44d92cf00000001180c2ec492a169ce16d1022c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2023/review/176957756@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2023@github.com>
References: <quicwg/base-drafts/pull/2023@github.com>
Subject: Re: [quicwg/base-drafts] Restarting from idle (#2023)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bf46cc4af3b7_69893f90604d45c4370682"; 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-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/VTAq6Y6OJQumO-6yZ78MB9VPUaw>
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: Tue, 20 Nov 2018 20:21:28 -0000

ianswett commented on this pull request.



> @@ -1040,6 +1040,24 @@ As an example of a well-known and publicly available implementation of a flow
 pacer, implementers are referred to the Fair Queue packet scheduler (fq qdisc)
 in Linux (3.11 onwards).
 
+## Resumption from idle
+
+A connection is idle if bytes in flight is 0 and there is nothing
+retransmittable to send.  This occurs when the connection is application
+limited and after a verified retransmission timeout.  In order to limit the
+size of bursts sent into the network, the behavior when restarting from idle
+depends upon whether pacing is used.
+
+If pacing is used, the connection should limit the initial burst of packets to
+no more than the initial congestion window and subsequent packets SHOULD be
+paced. The congestion window does not change while the connection is idle.

If the goal is to reduce bursts, I think we need to advocate for limiting the burst of a paced connection to nothing larger than the restarting window of an unpaced connection.

-- 
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/pull/2023#discussion_r235155723