You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gloinul opened this issue
Oct 12, 2020
· 3 comments
· Fixed by #4213
Labels
-recoveryeditorialAn issue that does not affect the design of the protocol; does not require consensus.ietf-lcAn issue that was raised during IETF Last Call.
"When there are no samples for a network path, and on the first RTT sample for the network path:
smoothed_rtt = rtt_sample
rttvar = rtt_sample / 2
Before any RTT samples are available, the initial RTT is used as rtt_sample. On the first RTT sample for the network path, that sample is used as rtt_sample. This ensures that the first measurement erases the history of any persisted or default values."
First of all this text uses "rtt_sample" while other places with the exception of the pseudo code uses latest_rtt variable. There are two issues with that. First that the value of rtt_sample is state dependent. If there exist an latest_rtt then that is used, if not the initial rtt. As the initial RTT is defined in Section 6.2.2 I think a forward reference is in place.
Finally, should this calculation in cases where latest_rtt exists be using min_ack_delay?
The text was updated successfully, but these errors were encountered:
gloinul
changed the title
Initial Smoothed_RTT values
Recovery-31: Initial Smoothed_RTT values
Oct 12, 2020
-recoveryeditorialAn issue that does not affect the design of the protocol; does not require consensus.ietf-lcAn issue that was raised during IETF Last Call.
In Section 5.3:
"When there are no samples for a network path, and on the first RTT sample for the network path:
smoothed_rtt = rtt_sample
rttvar = rtt_sample / 2
Before any RTT samples are available, the initial RTT is used as rtt_sample. On the first RTT sample for the network path, that sample is used as rtt_sample. This ensures that the first measurement erases the history of any persisted or default values."
First of all this text uses "rtt_sample" while other places with the exception of the pseudo code uses latest_rtt variable. There are two issues with that. First that the value of rtt_sample is state dependent. If there exist an latest_rtt then that is used, if not the initial rtt. As the initial RTT is defined in Section 6.2.2 I think a forward reference is in place.
Finally, should this calculation in cases where latest_rtt exists be using min_ack_delay?
The text was updated successfully, but these errors were encountered: