Re: [quicwg/base-drafts] Update ACK generation policy (#3623)

[Martin Thomson <[e-mail]>]

@martinthomson commented on this pull request.

Copyedit only.  I'll let this debate continue.

> @@ -3261,8 +3261,14 @@ a max_ack_delay of 0 is used. The sender uses the receiver's `max_ack_delay`
 value in determining timeouts for timer-based retransmission, as detailed in
 Section 5.2.1 of {{QUIC-RECOVERY}}.
 
-An ACK frame SHOULD be generated for at least every second ack-eliciting packet.
-This recommendation is in keeping with standard practice for TCP {{?RFC5681}}.
+

```suggestion
```

> @@ -3261,8 +3261,14 @@ a max_ack_delay of 0 is used. The sender uses the receiver's `max_ack_delay`
 value in determining timeouts for timer-based retransmission, as detailed in
 Section 5.2.1 of {{QUIC-RECOVERY}}.
 
-An ACK frame SHOULD be generated for at least every second ack-eliciting packet.
-This recommendation is in keeping with standard practice for TCP {{?RFC5681}}.
+
+An ACK frame SHOULD be generated for at least every 10th ack-eliciting packet
+(the QUIC IW). A receiver could send an ACK frame at least every second 
+ack-elicitingpacket (recommended practice for TCP {{?RFC5681}}). QUIC permits 

```suggestion
ack-eliciting packet (recommended practice for TCP {{?RFC5681}}). QUIC permits 
```

> @@ -3261,8 +3261,14 @@ a max_ack_delay of 0 is used. The sender uses the receiver's `max_ack_delay`
 value in determining timeouts for timer-based retransmission, as detailed in
 Section 5.2.1 of {{QUIC-RECOVERY}}.
 
-An ACK frame SHOULD be generated for at least every second ack-eliciting packet.
-This recommendation is in keeping with standard practice for TCP {{?RFC5681}}.
+
+An ACK frame SHOULD be generated for at least every 10th ack-eliciting packet
+(the QUIC IW). A receiver could send an ACK frame at least every second 
+ack-elicitingpacket (recommended practice for TCP {{?RFC5681}}). QUIC permits 
+a larger ratio between ACKs and data,which can reduce

```suggestion
a larger ratio between ACKs and data, which can reduce
```

> @@ -3261,8 +3261,14 @@ a max_ack_delay of 0 is used. The sender uses the receiver's `max_ack_delay`
 value in determining timeouts for timer-based retransmission, as detailed in
 Section 5.2.1 of {{QUIC-RECOVERY}}.
 
-An ACK frame SHOULD be generated for at least every second ack-eliciting packet.
-This recommendation is in keeping with standard practice for TCP {{?RFC5681}}.
+
+An ACK frame SHOULD be generated for at least every 10th ack-eliciting packet
+(the QUIC IW). A receiver could send an ACK frame at least every second 
+ack-elicitingpacket (recommended practice for TCP {{?RFC5681}}). QUIC permits 
+a larger ratio between ACKs and data,which can reduce
+the number of ACK frames that are sent and need to be processed.
+The receiver can provide a higher rate of acknowledgements
+(e.g. every ack-eliciting packet) for the first 100 packets.

```suggestion
(e.g., every ack-eliciting packet) for the first 100 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/3623#pullrequestreview-404708350