IETF Logo Mail Archive

Re: [quicwg/base-drafts] Given recommendations on when/how often to send ACK frames (#230)

ianswett <notifications@github.com> Thu, 02 March 2017 13:57 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 40F0112958D for <quic-issues@ietfa.amsl.com>; Thu, 2 Mar 2017 05:57:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 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_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 Rx5Z6YXOx6ki for <quic-issues@ietfa.amsl.com>; Thu, 2 Mar 2017 05:57:53 -0800 (PST)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [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 7481612944C for <quic-issues@ietf.org>; Thu, 2 Mar 2017 05:57:53 -0800 (PST)
Date: Thu, 02 Mar 2017 05:57:52 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1488463072; bh=Mpsr+fXCihCTxLckxtLXdHV9A1b2r/lErs2PiuRksMU=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zpkYh84jtxWePPC6GS5mU+4kT7qIDLoSe+56bLvJy30xeRPPDIEsCzdZrQKsoLMmn Lr1B/VMXYXJ1W1BXQnp7eBN6Fi1acnyGHI1VQ30fwv9BiGfAr33I1dJA/rgCGSKeXW lKrRZsDr2iEJAcXgFQnRrSTxGRpJ3002JrxUVYR0=
From: ianswett <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/230/283659819@github.com>
In-Reply-To: <quicwg/base-drafts/issues/230@github.com>
References: <quicwg/base-drafts/issues/230@github.com>
Subject: Re: [quicwg/base-drafts] Given recommendations on when/how often to send ACK frames (#230)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58b824e02d4df_7bee3ffd10a61c2c899a"; 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/mRZ_ktBuhGuJ4SKjlOT_ANEFpJg>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
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: Thu, 02 Mar 2017 13:57:55 -0000

1:1 acking is ok as long as that excludes acks.  Acks must be acked at a rate much less than 1:1, I would advise at most 1 ack for every two acks.

GQUIC follows TCP's approach of N=2 with a delayed ack timer, but we use a delayed ack timer of 25ms.  TCP delayed ack timers vary substantially by platform in practice, but tend to default to ~200ms in internet environments.

I think we should recommend a default, for which I'd suggest as TCP/GQUIC's default, as well as the ability to negotiate other values of N and the delayed ack timer.  If we don't want to allow negotiation, we should at least allow the peer to inform the sender of their ack algorithm.

-- 
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/230#issuecomment-283659819

v2.45.0 | Report a Bug | By Email | System Status