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
There is more discussion on this already in PR #3978 and PR #4005.
@ianswett proposed by email the following alternative wording:
MUST reduce the CWND to the ssthresh by the time recovery is exited and implementations MAY use a variety of mechanisms to reduce bytes in flight, including reducing it immediately, packet conservation, PRR(RFC6937) or decreasing the pacing rate.
@janaiyengar noted this text from RFC5861 which works as well:
Second, until all lost segments in the window of data in question are
repaired, the number of segments transmitted in each RTT MUST be no
more than half the number of outstanding segments when the loss was
detected.
The text was updated successfully, but these errors were encountered:
The recovery draft currently has the following text:
However, in https://tools.ietf.org/html/rfc5681#section-4.3 ssthresh is reduced upon entering recovery but cwnd is set to ssthresh when leaving recovery.
There is more discussion on this already in PR #3978 and PR #4005.
@ianswett proposed by email the following alternative wording:
@janaiyengar noted this text from RFC5861 which works as well:
The text was updated successfully, but these errors were encountered: