diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md
index 0bf8fd2517..206de16139 100644
--- a/draft-ietf-quic-transport.md
+++ b/draft-ietf-quic-transport.md
@@ -2430,11 +2430,10 @@ an endpoint MAY send a PING frame once per RTT to solicit an acknowledgment.
 To limit receiver state or the size of ACK frames, a receiver MAY limit the
 number of ACK blocks it sends.  A receiver can do this even without receiving
 acknowledgment of its ACK frames, with the knowledge this could cause the sender
-to unnecessarily retransmit some data.  When this is necessary, the receiver
-SHOULD acknowledge newly received packets and stop acknowledging packets
-received in the past.  Removing ack blocks before the peer has received them
-increases the chances the peer never received an acknowledgement, will declare
-the packet lost, and spuriously retransmit information.
+to unnecessarily retransmit some data.  Standard QUIC {{QUIC-RECOVERY}}
+algorithms declare packets lost after sufficiently newer packets are
+acknowledged.  Therefore, the receiver SHOULD repeatedly acknowledge newly
+received packets in preference to packets received in the past.
 
 ### ACK Frames and Packet Protection