Re: [quicwg/base-drafts] Retransmitting an ACK frame warning (#3049)

ianswett <> Wed, 18 September 2019 02:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D55E91201A3 for <>; Tue, 17 Sep 2019 19:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-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 li3zVolgyZAc for <>; Tue, 17 Sep 2019 19:33:36 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 77C97120096 for <>; Tue, 17 Sep 2019 19:33:36 -0700 (PDT)
Date: Tue, 17 Sep 2019 19:33:35 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1568774015; bh=Bc3Q+PJ+YfoWOOo89XGdiPndJ/Q+IyZ2f3g/CWh3Mjk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bJZ/RSXhmTBToQmELFh3NUd/SFh4x0+HIe7BbqbZTm5kXyhCD2AjtQ/4IF6ByUN+D hi6kxPwl3W0rBu3iRnI4KrlkX5vlZE768SRT/3E6I0Ou1r7T9Ovf4W+VCqRL1ACmb2 HsGRfUDEWY3MvJebbjxVzLMudtcDT6+bEtxSFcf8=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3049/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Retransmitting an ACK frame warning (#3049)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d81977fa34e7_670b3fcff82cd960386382"; 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.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, 18 Sep 2019 02:33:38 -0000

ianswett commented on this pull request.

> @@ -3183,7 +3183,8 @@ containing that information is acknowledged.
 * The most recent set of acknowledgments are sent in ACK frames.  An ACK frame
   SHOULD contain all unacknowledged acknowledgments, as described in
-  {{sending-ack-frames}}.
+  {{sending-ack-frames}}.  Retransmitting an ACK frame can result in an

There is already text that says "When only non-ACK-eliciting packets need to be acknowledged, an endpoint MAY wait until an ACK-eliciting packet has been received to bundle an ACK frame with outgoing frames."  I'm not sure that's sufficient, but your suggestion adds a SHOULD, which makes this change no longer editorial.  The ACK generation text needs a full rewrite, and I'd rather tackle that suggestion as part of that PR.

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