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 BB495130DC0 for ; Wed, 7 Nov 2018 00:54:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.47 X-Spam-Level: X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, 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] 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 UbCIgzODGn_n for ; Wed, 7 Nov 2018 00:54:57 -0800 (PST) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B890D128CB7 for ; Wed, 7 Nov 2018 00:54:57 -0800 (PST) Date: Wed, 07 Nov 2018 00:54:56 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1541580896; bh=PfAcIP/BFSdO09uHaKqe0Khsrg2i9Rfs/xLJUlX0h18=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=VICNZvU0vR1StZGnzUKQrDk2eqNsMvXS9AeVM8U85VVEyR/plDBAlvwqXFIqxjFmm e+MNnMkvTA8+vPYtEGADmRygu572hwXjJyyVr6w+hifPd0gYrjYIgXCVqt/3hNka86 9nkXsU/qIx2Zxc4vS4eTqm+/BLcXunQEs+ugO7w8= From: Bob Briscoe Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Sender-Controlled Delayed ACK Ratio (#1978) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5be2a860ea4f9_34133fcd3a4d45bc110303b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: bbriscoe 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: Wed, 07 Nov 2018 08:55:06 -0000 ----==_mimepart_5be2a860ea4f9_34133fcd3a4d45bc110303b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yesterday Jana said the WG is open to the possibility of a sender-controlled ack_ratio. A simpler approach: a 3-bit field in each direction, in every packet, carrying ack_exp where > > ack_ratio` = 2^ack_exp.` Exactly how many bits to use is up for discussion, but I believe ack_ratio=16 and growing is already common in DCs, so 2 bits isn't quite enough. Receiving ack_exp would be defined to mean: "From now, please try to ACK at least every 2^ack_exp packets". No negotiation. No need to detect loss of messages. Just repetition of a hint. Of course a variable can be constant, e.g. for implementers of a sender who want to leave adaptation code for later, just set ack_exp=1 in every packet. I think this would address all the scenarios in #1428 (related but closed). -- 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/1978 ----==_mimepart_5be2a860ea4f9_34133fcd3a4d45bc110303b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Yesterday Jana said the WG is open to the possibility of a sender-controlled ack_ratio.

A simpler approach: a 3-bit field in each direction, in every packet, carrying ack_exp where

ack_ratio = 2^ack_exp.
Exactly how many bits to use is up for discussion, but I believe ack_ratio=16 and growing is already common in DCs, so 2 bits isn't quite enough.

Receiving ack_exp would be defined to mean: "From now, please try to ACK at least every 2^ack_exp packets". No negotiation. No need to detect loss of messages. Just repetition of a hint.

Of course a variable can be constant, e.g. for implementers of a sender who want to leave adaptation code for later, just set ack_exp=1 in every packet.

I think this would address all the scenarios in #1428 (related but closed).

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

----==_mimepart_5be2a860ea4f9_34133fcd3a4d45bc110303b--