Re: [quicwg/base-drafts] Add max_bytes_before_ack to transport (#1715)

Christoph Paasch <notifications@github.com> Wed, 12 September 2018 16:51 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 5227E130DFD for <quic-issues@ietfa.amsl.com>; Wed, 12 Sep 2018 09:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.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, RCVD_IN_DNSWL_HI=-5, 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 4_KH0odWKT0a for <quic-issues@ietfa.amsl.com>; Wed, 12 Sep 2018 09:51:32 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [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 2E3EA130DF3 for <quic-issues@ietf.org>; Wed, 12 Sep 2018 09:51:32 -0700 (PDT)
Date: Wed, 12 Sep 2018 09:51:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1536771091; bh=LWpP68qSBoyKiDk8TU2ESfrdspEoPKoZ1We/XoqtOm0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pItMGMApnpD/it7W8K+khpr3fsT4pyHYKq5S9xPqvFDtiAZsx13I5l7PelsVFrnv4 UWyL/73JxqULUyMCkMlKSp1bELrOjzGuPN/q7ld20/2xmczLG0iE+LCb/cVhtcupJP Q4HyQkmwoseP5B7Oc99v5c0fge6KuVMQ/yZYnjFo=
From: Christoph Paasch <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab14112e681cc5db4b942b03cd5a68819340caa0b292cf0000000117b1061292a169ce152ea636@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1715/c420719877@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1715@github.com>
References: <quicwg/base-drafts/pull/1715@github.com>
Subject: Re: [quicwg/base-drafts] Add max_bytes_before_ack to transport (#1715)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b994413c52_46d03fbf3d8d45b41780dc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: cpaasch
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/GhBzpymJ2S13oCSFjedDKtNbVSQ>
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: Wed, 12 Sep 2018 16:51:34 -0000

I am to some extend agreeing with what @huitema is saying. This is adding complexity at a late stage, without giving clear guidance,... as to how to use the max_bytes_before_ack:
* What value should a congestion-control announce to the peer ?
* How exactly should the receiver use the value? During slow-start, should it ACK more frequently to allow the sender to build a rate-estimation? Or should it always wait for the necessary bytes?

AFAICS, this can easily be added later on as an extension once it is clearer how to use it.

-- 
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/1715#issuecomment-420719877