Update draft-ietf-quic-recovery.md

quicwg · Apr 9, 2020 · 5226e28 · 5226e28
1 parent 53b4584
commit 5226e28
Showing 1 changed file with 6 additions and 6 deletions.
diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md
@@ -500,12 +500,12 @@ packet on a PTO expiration before confirming that the server is able to decrypt
 0-RTT packets, and prevents a server from sending a 1-RTT packet on a PTO
 expiration before it has the keys to process an acknowledgement.
 
-When a PTO timer expires, the PTO period MUST be set to twice its current
-value.  The PTO period is set based on the latest RTT information when
-receiving an acknowledgement if the peer has completed address validation.
-The PTO backoff is not decreased while the peer is validating the
-address, to ensure the client's anti-deadlock timer does not fire too
-aggressively when the server does not yet have handshake data to send.
+When a PTO timer expires, the PTO backoff MUST be increased, resulting in the
+PTO period being set to twice its current value.  The PTO period is set based
+on the latest RTT information when receiving an acknowledgement. The PTO backoff
+is not decreased while the server is validating the client's address, to ensure
+the client's anti-deadlock timer does not fire too aggressively when the server
+does not yet have handshake data to send.
 
 This exponential reduction in the sender's rate is important because
 consecutive PTOs might be caused by loss of packets or acknowledgements due to