Re: [quicwg/base-drafts] Prohibit PADDING in response to ACK (#3104)

martinduke <> Thu, 17 October 2019 06:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EFDB712084C for <>; Wed, 16 Oct 2019 23:43:42 -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 HnP7ZJ5OaKCt for <>; Wed, 16 Oct 2019 23:43:41 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2BCA6120824 for <>; Wed, 16 Oct 2019 23:43:41 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 50E3496045D for <>; Wed, 16 Oct 2019 23:43:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571294620; bh=44QG2hOHzU0dZd1udbAGK9kHaW/xWnARAQ+4A0GCj+U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WTWtm7/KdgBZGPlzzsONz7YbuAJBn72F8NTOl7MhlEmAspRidw9HQ0ws6eOsAOgUa BknZkNhcB8rq/Ek7J2l+1NO13A1JFm3HUxzYMubZOaCC6Ka0FBAbp52diquZQfTrK4 cOxIPLJUhAv3J/P58bN+DzAXSnc72XGSiEyfxEeE=
Date: Wed, 16 Oct 2019 23:43:40 -0700
From: martinduke <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3104/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Prohibit PADDING in response to ACK (#3104)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5da80d9c419c5_8c23ff8d08cd968105347"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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 06:43:45 -0000

martinduke commented on this pull request.

> @@ -3061,14 +3061,15 @@ of doing so.
 Packets containing only ACK frames are not congestion controlled, so there are
 limits on how frequently they can be sent.  An endpoint MUST NOT send more than
-one ACK-frame-only packet in response to receiving an ack-eliciting packet (one
-containing frames other than ACK and/or PADDING).  An endpoint MUST NOT send a
-packet containing only an ACK frame in response to a non-ack-eliciting packet
-(one containing only ACK and/or PADDING frames), even if there are packet gaps
-which precede the received packet. Limiting ACK frames avoids an infinite
-feedback loop of acknowledgements, which could prevent the connection from ever
-becoming idle. However, the endpoint acknowledges non-ack-eliciting packets when
-it sends an ACK frame.
+one ACK-frame-only packet in response to receiving an ACK-eliciting packet

Actually, non-ack-eliciting is already defined, and would make this flow much better.

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