Re: [quicwg/base-drafts] Try to clarify interaction of PADDING and ACK (#1923)

[ianswett <[e-mail]>]

ianswett commented on this pull request.

Agreed, the current text is awkward, but the idea of eventually acknowledged is both not always true and potentially confusing.

> @@ -2772,13 +2772,13 @@ there are packet gaps which precede the received packet.  The endpoint MUST
 however acknowledge packets containing only ACK or PADDING frames when sending
 ACK frames in response to other packets.
 
-While PADDING frames do not elicit an ACK frame from a receiver, they are
-considered to be in flight for congestion control purposes
-{{QUIC-RECOVERY}}. Sending only PADDING frames might cause the sender to become
-limited by the congestion controller (as described in {{QUIC-RECOVERY}}) with no
-acknowledgments forthcoming from the receiver. Therefore, a sender should ensure
-that other frames are sent in addition to PADDING frames to elicit
-acknowledgments from the receiver.
+While PADDING frames are only eventually acknowledged, they are still considered

```suggestion
While PADDING frames may never be acknowledged, they are still considered
```

-- 
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/1923#pullrequestreview-168831320