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

[MikkelFJ <[e-mail]>]

mikkelfj commented on this pull request.



>  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.
 
+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.  When the receiver is only sending ACK-only
+packets, it can bundle a PING with a fraction of them, such as one per round
+trip, to drop unnecessary ACK ranges and any tracking state associated with the
+previously sent ACK-only packets.  The receiver MUST NOT bundle a PING with all
+packets that would otherwise be ACK-only, in order to avoid an indefinite

```suggestion
packets that would otherwise not be ACK-eliciting, in order to avoid an indefinite
```
PADDING+PING

-- 
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-250633910