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

[Martin Thomson <[e-mail]>]

martinthomson approved this pull request.



>  To limit ACK Ranges (see {{ack-ranges}}) to those that have not yet been
 received by the sender, the receiver SHOULD track which ACK frames have been
 acknowledged by its peer. The receiver SHOULD exclude already acknowledged
 packets from future ACK frames whenever these packets would unnecessarily
-contribute to the ACK frame size.
-
-Because ACK frames are not sent in response to ACK-only packets, a receiver that
-is only sending ACK frames will only receive acknowledgements for its packets if
-the sender includes them in packets with non-ACK frames.  A sender SHOULD bundle
-ACK frames with other frames when possible.
+contribute to the ACK frame size.  When the receiver is only sending non
+ACK-eliciting packets, it can bundle a PING with a fraction of them, such as one

non-ACK-eliciting?

> @@ -2883,16 +2884,21 @@ needing acknowledgement are received.  The sender can use the receiver's
 Strategies and implications of the frequency of generating acknowledgments are
 discussed in more detail in {{QUIC-RECOVERY}}.
 
+ACK-only packets are only sent in response to ACK-eliciting packets, so a
+receiver that is only sending ACK frames will only receive acknowledgements
+for its packets if the sender includes them in packets with ACK-eliciting

An endpoint that is only sending ACK frames won't receive acknowledgments from its peer unless those acknowledgements are included in packets [...] 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2794#pullrequestreview-251394349