Re: [quicwg/base-drafts] Clarify ACK of ACKs and bundling a PING (#2794)

ianswett <> Wed, 19 June 2019 21:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 92F1512025B for <>; Wed, 19 Jun 2019 14:17:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.605
X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 9TGI29SajmDh for <>; Wed, 19 Jun 2019 14:17:14 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B9076120072 for <>; Wed, 19 Jun 2019 14:17:14 -0700 (PDT)
Date: Wed, 19 Jun 2019 14:17:13 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560979033; bh=56lRMafcXNVyh6io6e1I9GsN3H4aXNWsjOjkN3ExjrA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hFK6FUmkh/tEawLD1sfVW95yLZx1mVMpzR+Qd1tHPGFK3GisCagsNOUQFFIKMiWeR VL0ZHkk5iyoZ9iObRX/chBrN/7eV3NhAVkf+Km5WJi8USq8dk337N4BNM4vN37Aiyl IbF3D9iIqsYPYag/HLgeXFh+GMp+20CHWZrDeUoY=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2794/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Clarify ACK of ACKs and bundling a PING (#2794)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d0aa659a9ca4_4dfb3ff848ccd960493839"; 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, 19 Jun 2019 21:17:17 -0000

ianswett commented on this pull request.

> @@ -2860,12 +2860,13 @@ valid frames? -->
 ### Sending ACK Frames
 An endpoint MUST NOT send more than one packet containing only an ACK frame per
-received packet that contains frames other than ACK and PADDING frames.
-An endpoint MUST NOT send a packet containing only an ACK frame in response
-to a packet containing only ACK or PADDING frames, even if there are packet
-gaps which precede the received packet. This prevents an indefinite feedback
-loop of ACKs. The endpoint MUST however acknowledge packets containing only
-ACK or PADDING frames when sending ACK frames in response to other packets.
+received non-ACK-eliciting packet(ie: one containing only ACK and/or PADDING

This text is actually backwards, fixing it to remove the non

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