From nobody Sun Mar 22 09:17:54 2020 Return-Path: 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 137923A07BB for ; Sun, 22 Mar 2020 09:17:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.482 X-Spam-Level: X-Spam-Status: No, score=-1.482 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, 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 OpUeSXbmTpDV for ; Sun, 22 Mar 2020 09:17:50 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A4D33A07B3 for ; Sun, 22 Mar 2020 09:17:50 -0700 (PDT) Received: from github-lowworker-39ac79b.ac4-iad.github.net (github-lowworker-39ac79b.ac4-iad.github.net [10.52.18.15]) by smtp.github.com (Postfix) with ESMTP id 57EF0C60224 for ; Sun, 22 Mar 2020 09:17:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1584893869; bh=hbfy3e3xezdiVyY0048IXFC7VuBeSghC0L/PLYvfTWA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F501b8Kp0JYzVaf7XV/E1tP7dBfbW28l4FwfFTcfm6uXBvFXgGGTJ1N3v3Hg/MrcS M9tZzeaeM71ixklJ984mg2uYjRIpBL8Oe1nYSxOgvUHRJnPP688KUUhtwwSG988hu+ a0E7FdRgtwMdkl76eabWa1WQ57bH8eMD+2c+4FWE= Date: Sun, 22 Mar 2020 09:17:49 -0700 From: ianswett Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Update ACK generation policy (#3501) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5e778fad48245_6c483ffae78cd96835615d"; 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: X-BeenThere: quic-issues@ietf.org 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: Sun, 22 Mar 2020 16:17:52 -0000 ----==_mimepart_5e778fad48245_6c483ffae78cd96835615d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit ianswett commented on this pull request. I don't want to land this for reasons posted in the issue. > @@ -3170,11 +3170,21 @@ delayed retransmissions from the peer. For Initial and Handshake packets, a max_ack_delay of 0 is used. The sender uses the receiver's `max_ack_delay` value in determining timeouts for timer-based retransmission, as detailed in Section 5.2.1 of {{QUIC-RECOVERY}}. +The max_ack_delay needs to be set so that at least several samples can When max_ack_delay is first sent, the path RTT is not known. > -In order to assist loss detection at the sender, an endpoint SHOULD send an ACK +An ACK frame SHOULD be generated for at least every tenth ack-eliciting There's no mention here of ACKing more frequently for N initial packets to avoid reducing the increase in slow-start. -- 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/3501#pullrequestreview-379020995 ----==_mimepart_5e778fad48245_6c483ffae78cd96835615d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

I don't want to land this for reasons posted in the issue.

In draft-ietf-quic-transport.md:

> @@ -3170,11 +3170,21 @@ delayed retransmissions from the peer. For Initial and Handshake packets,
 a max_ack_delay of 0 is used. The sender uses the receiver's `max_ack_delay`
 value in determining timeouts for timer-based retransmission, as detailed in
 Section 5.2.1 of {{QUIC-RECOVERY}}.
+The max_ack_delay needs to be set so that at least several samples can

When max_ack_delay is first sent, the path RTT is not known.

In draft-ietf-quic-transport.md:

>  
-In order to assist loss detection at the sender, an endpoint SHOULD send an ACK
+An ACK frame SHOULD be generated for at least every tenth ack-eliciting

There's no mention here of ACKing more frequently for N initial packets to avoid reducing the increase in slow-start.

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

----==_mimepart_5e778fad48245_6c483ffae78cd96835615d--