Skip to content

Commit 3a7437d

Browse files
committed
Rephrase the text about one-way text
1 parent 503027d commit 3a7437d

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

draft-ietf-quic-transport.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2548,10 +2548,14 @@ receiver SHOULD track which ACK frames have been acknowledged by its peer. Once
25482548
an ACK frame has been acknowledged, the packets it acknowledges SHOULD NOT be
25492549
acknowledged again.
25502550

2551-
A receiver that is only sending ACK frames will not receive acknowledgments for
2552-
its packets. Sending an occasional MAX_DATA or MAX_STREAM_DATA frame as data is
2553-
received will ensure that acknowledgements are generated by a peer. Otherwise,
2554-
an endpoint MAY send a PING frame once per RTT to solicit an acknowledgment.
2551+
Because ACK-only packets are not acknowledged, a receiver that is only
2552+
sending ACK frames will only receive acknowledgements for its packets
2553+
if the sender piggybacks them on other packets. In order to enable
2554+
this, senders SHOULD prioritize sending ACKs along with their data.
2555+
In addition, if a receiver regularly issues additional flow control
2556+
credit rather than just issuing infinite flow control credit at the
2557+
beginning of the connection, the MAX_DATA and MAX_STREAM_DATA frames
2558+
will elicit acknowledgements from the sender
25552559

25562560
To limit receiver state or the size of ACK frames, a receiver MAY limit the
25572561
number of ACK blocks it sends. A receiver can do this even without receiving

0 commit comments

Comments
 (0)