IETF Logo Mail Archive

Re: [quicwg/base-drafts] ACK of ACK are useful (#2546)

ianswett <notifications@github.com> Sat, 23 March 2019 23:45 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 AEEAD130D7A for <quic-issues@ietfa.amsl.com>; Sat, 23 Mar 2019 16:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 Q6tan_IFVna6 for <quic-issues@ietfa.amsl.com>; Sat, 23 Mar 2019 16:45:15 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C106D12D550 for <quic-issues@ietf.org>; Sat, 23 Mar 2019 16:45:14 -0700 (PDT)
Date: Sat, 23 Mar 2019 16:45:13 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1553384713; bh=ICOSL1VOcbGDz0Gf18uJpSWOJXeN4/Lb26YjGOWFsdo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dZimGOpfqw/w3+WzylWhlnAUj0uX/PL8bCu9CAo27oX5hNKA4Jr2jwhoG0pWNppGc xOmG+pnzMbDNJx2aPkYs6voumhZxiVaD71+iNBdlu4E8xRYOfsNsSK5u83M9jBHRTi 6drDN2HclY6av7XVd9BT1F+y1UQXqL3LNI0FcCn8=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab3a9fcfd3869ce4a34a007384749d6cf28132f1d292cf0000000118ae870992a169ce194d6f49@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2546/475914488@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2546@github.com>
References: <quicwg/base-drafts/issues/2546@github.com>
Subject: Re: [quicwg/base-drafts] ACK of ACK are useful (#2546)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c96c509613b0_67383fe4c40d45c42645d2"; 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/8LkMbCAHdA359cdOQQA_sc9RTZ0>
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: Sat, 23 Mar 2019 23:45:17 -0000

I'd argue that ACK+PING isn't a hack, but instead a simple way for the sender, whose state we're trying to limit, to balance the amount of state it stores vs the extra ACKs being received.

Getting the peer to implement the correct ACK behavior by sending a single extra byte is much simpler and more robust in my experience than relying on the receiver to implement an "ACK every 10/20/etc ACKs" policy in a way that every sender is happy with.

This could likely use more text and there's still an outstanding editorial issue to move most of the ACK sending text that's in recovery into transport, so it's all in one place, since I believe there are currently a few subtle inconsistencies.

-- 
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/2546#issuecomment-475914488

v2.23.0 | Report a Bug | By Email