I have submitted a revised version of draft-ietf-dccp-rfc3448bis-05.txt. The changes from -04 are as follows: * Added a mechanism for decaying the value in X_recv_set following a loss event in a data-limited interval, and restricting recv_limit to "max (X_recv_set)" for the next RTT. Also added a discussion to Appendix C of the response to a loss during a data-limited period. Following feedback from Gorry and Arjuna. * Removed a restriction in step 4) of Section 4.3 about checking if the sender was not data-limited, when the sender has been in initial slow-start. It is no longer needed. Feedback from Arjuna. * Added pseudocode to Section 8.2.1 on "Determining If an Interval Was a Data-limited Interval", fixing a bug in the procedure. Feedback from Arjuna. Many thanks to Gorry and Arjuna for feedback, in particular about dealing with loss events in data-limited intervals. I think this is now ready for Working Group Last Call (though I note that I have thought this before...) - Sally Begin forwarded message:
|