Re: [quicwg/base-drafts] When the sender is using standard Reno congestion control, ack every ~2 packets (#1428)
ianswett <notifications@github.com> Sun, 10 June 2018 22:38 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 D2B52130F03 for <quic-issues@ietfa.amsl.com>; Sun, 10 Jun 2018 15:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Level:
X-Spam-Status: No, score=-3.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 Aw7ffGpYrarh for <quic-issues@ietfa.amsl.com>; Sun, 10 Jun 2018 15:38:43 -0700 (PDT)
Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 109EE127332 for <quic-issues@ietf.org>; Sun, 10 Jun 2018 15:38:43 -0700 (PDT)
Date: Sun, 10 Jun 2018 15:38:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528670322; bh=yjzQ5rMm7u7tPbh8F7oJT7kYqMntCZ4sDMvgUyya7ns=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CTTjC2JaQEx0ZrKWdH/pw7W4BAHck03KgZCkLov0JlkJvbaXqjZJVdZ77YLsWh50U vn3stZm8faEw2EfPU5qitoIA/1VvWvzZeN2aFwZitTXgqFEqD8z0RSp/ErHiTGc87W ztQrGWGtAKOhNcanCsOfhMCsIb4fe2ImswBZ2abU=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab58242915468fff3e4b3ca6ea6c6358106cedc68b92cf0000000117356a7292a169ce13ae108c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1428/396087604@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1428@github.com>
References: <quicwg/base-drafts/issues/1428@github.com>
Subject: Re: [quicwg/base-drafts] When the sender is using standard Reno congestion control, ack every ~2 packets (#1428)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b1da87282ea4_2a902aacccd98f5c264bf"; 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/6Rwo9fatIo2QzV4SEavXx6qxZXI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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: Sun, 10 Jun 2018 22:38:45 -0000
To clarify, my proposal is that we should document an acknowledgement approach we expect to work well with the described congestion controller, Reno. Do you think that would not be useful? If we want to add a mechanism to indicate to the receiver that acknowledging packets less frequently is ok, then as you said, we need one or more transport parameters. What transport parameter(s) do you have in mind? The two I can think of are the max number of packets newly acked at once and the interval between acks in fraction of an RTT or absolute time. The current BBR approach is very adaptive, so it doesn't need to know the details of the receiver's behavior. It's not clear to me how other congestion controllers will adapt to this, so it's not clear to me what information they need? -- 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/1428#issuecomment-396087604
- [quicwg/base-drafts] When the sender is using sta… ianswett
- Re: [quicwg/base-drafts] When the sender is using… janaiyengar
- Re: [quicwg/base-drafts] When the sender is using… ianswett
- Re: [quicwg/base-drafts] When the sender is using… janaiyengar
- Re: [quicwg/base-drafts] When the sender is using… ianswett
- Re: [quicwg/base-drafts] When the sender is using… MikkelFJ
- Re: [quicwg/base-drafts] When the sender is using… ianswett
- Re: [quicwg/base-drafts] When the sender is using… ianswett
- Re: [quicwg/base-drafts] When the sender is using… MikkelFJ
- Re: [quicwg/base-drafts] When the sender is using… mirjak
- Re: [quicwg/base-drafts] When the sender is using… ianswett
- Re: [quicwg/base-drafts] When the sender is using… Praveen Balasubramanian
- Re: [quicwg/base-drafts] When the sender is using… Magnus Westerlund
- Re: [quicwg/base-drafts] When the sender is using… Nick Banks
- Re: [quicwg/base-drafts] When the sender is using… ianswett
- Re: [quicwg/base-drafts] When the sender is using… Magnus Westerlund
- Re: [quicwg/base-drafts] When the sender is using… Christian Huitema
- Re: [quicwg/base-drafts] When the sender is using… MikkelFJ
- Re: [quicwg/base-drafts] When the sender is using… ianswett
- Re: [quicwg/base-drafts] When the sender is using… Christian Huitema
- Re: [quicwg/base-drafts] When the sender is using… ianswett
- Re: [quicwg/base-drafts] When the sender is using… ianswett
- Re: [quicwg/base-drafts] When the sender is using… Martin Thomson
- Re: [quicwg/base-drafts] When the sender is using… Martin Thomson