Merge pull request #313 from quicwg/mirjak-patch-51

Clarify Ack-Eliciting Threshold of 0 and 1

Author: mirjak

draft-ietf-quic-ack-frequency.md

@@ -458,7 +458,14 @@ the endpoint resumes sending acknowledgements based on the Ack-Eliciting
 Threshold or max_ack_delay. Therefore, CE-marking only triggers an immediate
 acknowledgement when there is a transition from non-CE-marked to CE-marked.
 
-Doing this maintains the peer's response time to congestion events, while also
+If the Ack-Eliciting Threshold is 0, every ack-eliciting packet is immediately
+acknowledged, CE marked or not. If the Ack-Eliciting Threshold
+is 1, the default behavior as specified in RFC9000 applies, which recommends to
+immediately acknowledge all packets marked with CE (see
+{{Section 13.2.1 of QUIC-TRANSPORT}}).
+
+Acknowledging the first CE marked packet immediately maintains
+the peer's response time to congestion events, while also
 reducing the ACK rate compared to {{Section 13.2.1 of QUIC-TRANSPORT}} during
 extreme congestion or when peers are using DCTCP {{?RFC8257}} or other
 congestion controllers (e.g. {{?I-D.ietf-tsvwg-aqm-dualq-coupled}}) that mark