Re: [quicwg/base-drafts] Resending ACKs increases max_ack_delay unnecessarily (#1438)

ianswett <> Thu, 28 June 2018 17:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 35177130E9D for <>; Thu, 28 Jun 2018 10:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Status: No, score=-8.009 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ujeOyFV1hm3k for <>; Thu, 28 Jun 2018 10:02:07 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E9FB6130F93 for <>; Thu, 28 Jun 2018 10:02:05 -0700 (PDT)
Date: Thu, 28 Jun 2018 10:02:03 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1530205323; bh=hkTr72o3RvsEdDTCGOLYmANYgRJ6ezSC+JF6fbrnJkI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rWFFYHAw6/YWMluyFp7JDmGVtT1o31M56ja/VmeKVegs0afoi2lUKc/AfK4ZTTbz6 IR7O7srwkvPOvE+/glKSEcgGAzHdFDYBUEd9UwwwG9myL1A+sxgyQf7Ep34gFiCX3M slid81f7NIC80HxCPH7AyRouf2L2aryLnStmb+2w=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/1438/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Resending ACKs increases max_ack_delay unnecessarily (#1438)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b35148bd46f9_8fc3fdc645fef80124158"; 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
Archived-At: <>
X-Mailman-Version: 2.1.26
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: Thu, 28 Jun 2018 17:02:10 -0000

You only increase max_ack_delay if there's a newly acknowledged largest acked packet.  So sending old acks by itself doesn't increase max_ack_delay.

Explicit communication is a way to bound this, and in theory it seems unnecessary, but I suspect adding it could mitigate some very weird edge cases.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: