Re: [quicwg/base-drafts] When/how often to send ACK frames (#230)
mirjak <notifications@github.com> Mon, 14 August 2017 10:10 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 D04CE13217D for <quic-issues@ietfa.amsl.com>; Mon, 14 Aug 2017 03:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.799
X-Spam-Level:
X-Spam-Status: No, score=-9.799 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=-2.8, 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 5Lm7PZFRe5L0 for <quic-issues@ietfa.amsl.com>; Mon, 14 Aug 2017 03:10:24 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext5.iad.github.net [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 281E8132143 for <quic-issues@ietf.org>; Mon, 14 Aug 2017 03:10:24 -0700 (PDT)
Date: Mon, 14 Aug 2017 03:10:23 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1502705423; bh=5MpuGon6TTDBz6SA2TZx8pGi7L3A2kHO/l7WQDGQ5h4=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0w4dTpDtc9+zova2V9mbS8dNLq/F26f9PeShMwswIwnttFrW8taInsxiiFMj3MyMY oXsgjFW/NjEi6FOQznIyvxiMWWXYu05LTfLSFlOYSpT6a0ibdPxQDkpCbQsDfk9d5b mnd+OcHbx2/TdzwqyxOBCG8MvhBjwuILlboZYLeA=
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab010d345dcb4a1ddd30163f308a6982af747b182392cf0000000115a9390f92a169ce0c19f54a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/230/322152628@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] When/how often to send ACK frames (#230)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5991770f48a8b_70e3fbafe62dc2c81465"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
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/rp7ne98YkwYUbPXJtOGrKbhQr-w>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 14 Aug 2017 10:10:26 -0000
In TCP this is would be useful to do a more appropriate RTT and RTO estimation. However, in QUIC you have more fine grained timing information in the ACK frame itself, so maybe that's actually not that useful anymore. However, there is a trade-off between overhead and responsiveness (of †he congestion control). I think it would actually be useful to some kind of negotiation, where the data sender/ack receiver can specify a min and may ack rate, because that peer a) might know something about any access link restrictions (-> don't send more ACK than this because otherwise it will overload my link), and b) know the congestion control use (my cc scheme needs at least an ack every x packets to function correctly). -- 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-322152628
- [quicwg/base-drafts] Given recommendations on whe… mirjak
- Re: [quicwg/base-drafts] Given recommendations on… Martin Thomson
- Re: [quicwg/base-drafts] Given recommendations on… mirjak
- Re: [quicwg/base-drafts] Given recommendations on… ianswett
- Re: [quicwg/base-drafts] Given recommendations on… acmacm
- Re: [quicwg/base-drafts] Given recommendations on… Martin Thomson
- Re: [quicwg/base-drafts] Given recommendations on… Al Morton
- Re: [quicwg/base-drafts] Given recommendations on… Martin Thomson
- Re: [quicwg/base-drafts] Given recommendations on… ianswett
- Re: [quicwg/base-drafts] Given recommendations on… Martin Thomson
- Re: [quicwg/base-drafts] When/how often to send A… Martin Thomson
- Re: [quicwg/base-drafts] When/how often to send A… mirjak
- Re: [quicwg/base-drafts] When/how often to send A… Al Morton
- Re: [quicwg/base-drafts] When/how often to send A… Martin Thomson
- Re: [quicwg/base-drafts] When/how often to send A… Al Morton
- Re: [quicwg/base-drafts] When/how often to send A… mirjak
- Re: [quicwg/base-drafts] When/how often to send A… ianswett
- Re: [quicwg/base-drafts] When/how often to send A… ianswett
- Re: [quicwg/base-drafts] When/how often to send A… pravb
- Re: [quicwg/base-drafts] When/how often to send A… Martin Thomson
- Re: [quicwg/base-drafts] When/how often to send A… ianswett
- Re: [quicwg/base-drafts] When/how often to send A… ianswett