Re: [quicwg/base-drafts] MUST ACK each ack-eliciting packet once (#3092)

Jana Iyengar <> Thu, 17 October 2019 18:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8EA9A120B69 for <>; Thu, 17 Oct 2019 11:26:03 -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 fErWdo3HRK8t for <>; Thu, 17 Oct 2019 11:26:00 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 51055120B66 for <>; Thu, 17 Oct 2019 11:25:43 -0700 (PDT)
Date: Thu, 17 Oct 2019 11:25:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571336742; bh=te/jJER9pZla4xnujFZfHeh+51up6fp+SQfP+vDKj1Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OzgY2wBjGJ0zJqeHmixx/MjlLODJdIycWNsJ52VjCy+lqa4k2dj8a3PapmwLnSMC4 d7QkAUGEo09IcSikhHdZmkpYXdJZ2KwOIBD7ZBj4SHcR4wRUH+dOJ/qpK7xqnNWNUD 09eXY8l+8sPqIUf3T2Z5rychx/PlDJTIbYhRdMmA=
From: Jana Iyengar <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3092/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] MUST ACK each ack-eliciting packet once (#3092)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5da8b2264b996_29ac3f8ab26cd960989e0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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: Thu, 17 Oct 2019 18:26:04 -0000

janaiyengar commented on this pull request.

> @@ -3013,18 +3013,21 @@ guidance offered below seeks to strike this balance.
 An ACK frame SHOULD be generated for at least every second ack-eliciting packet.
 This recommendation is in keeping with standard practice for TCP {{?RFC5681}}.
+Every ack-eliciting packet MUST be acknowledged in at least one transmitted
+ACK frame, and SHOULD typically be acknowledged in more than one ACK frame.

I would rephrase this. "A receiver is expected to commonly acknowledge a received packet in multiple subsequent ACK frames, to increase the chances of the acknowledgement being received by the sender.  A receiver MUST acknowledge every received ack-eliciting packet at least once."

Also, move this to the top of the section.

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