From 3187cb3b5d05ee6d7c69b1b609412376439913f9 Mon Sep 17 00:00:00 2001 From: Jana Iyengar Date: Sun, 2 Aug 2020 14:47:28 -0700 Subject: [PATCH] marten and kazuho comments --- draft-ietf-quic-recovery.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md index 4d70576382..217b59c557 100644 --- a/draft-ietf-quic-recovery.md +++ b/draft-ietf-quic-recovery.md @@ -339,11 +339,11 @@ of min_rtt and smoothed_rtt ({{smoothed-rtt}}) after a disruptive network event, and because it is possible that an increase in path delay resulted in persistent congestion being incorrectly declared. -Endpoints MAY set the min_rtt to the newest RTT sample at other times in the -connection, such as when traffic volume is low, to refresh the -value. Implementations should be careful not to refresh this value too -frequently, since the actual minimum RTT of the path may not be frequently -observable. +Endpoints MAY re-establish the min_rtt at other times in the connection, such as +when traffic volume is low and an acknowledgement is received with a low +acknowledgement delay. Implementations should be careful not to refresh this +value too frequently, since the actual minimum RTT of the path may not be +frequently observable. ## Estimating smoothed_rtt and rttvar {#smoothed-rtt}