1 / 8

TCP Friendly Rate Control (TFRC): Protocol Specification RFC3448bis

draft-ietf-dccp-rfc3448bis-05.txt S. Floyd, M. Handley, J. Padhye, and J. Widmer Testing and simulations from A. Sathiaseelan March 2008, DCCP Working Group. TCP Friendly Rate Control (TFRC): Protocol Specification RFC3448bis. Changes from draft-ietf-dccp-rfc3448bis-03:.

garth
Télécharger la présentation

TCP Friendly Rate Control (TFRC): Protocol Specification RFC3448bis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-ietf-dccp-rfc3448bis-05.txt S. Floyd, M. Handley, J. Padhye, and J. Widmer Testing and simulations from A. Sathiaseelan March 2008, DCCP Working Group TCP Friendly Rate Control (TFRC): Protocol SpecificationRFC3448bis

  2. Changes from draft-ietf-dccp-rfc3448bis-03: • Added text that the choice of b=1 is consistent with RFC3465bis. Feedback from Gorry. • Typos and such reported by Arjuna. • Updated terminology section, fixed typos and such. Feedback from Vladimir Moltchanov. • Added a section to the Appendix about how one would add CWV-style behavior to TFRC for data-limited periods, if one wanted to. Feedback from Gorry. • Added an implementation section about X_recv_set.

  3. Changes from draft-ietf-dccp-rfc3448bis-04: • 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.

  4. Changes from draft-ietf-dccp-rfc3448bis-04: • Protocol Response to a loss during a data-limited period • ------------- ----------------------------------------------- • Standard TCP: Set ssthresh, cwnd to FlightSize/2. • TCP with CWV: Same as Standard TCP. • Standard TFRC: Calculate X_Bps, send at most 2*X_recv. • Revised TFRC: Calculate X_Bps, send at most recv_limit. • In addition, modify X_recv_set. • Table 4: Response to a loss during a data-limited period. • (From Appendix C.4.)‏

  5. Changes from draft-ietf-dccp-rfc3448bis-04: • 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. • This 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.

  6. Changes since draft-ietf-dccp-rfc3448bis-05(not yet submitted): • Editing in response to AD review from Lars Eggert. • Using normative language (MAY, SHOULD, REQUIRE, OPTIONAL, etc.), fixing a few nits.

  7. Changes since draft-ietf-dccp-rfc3448bis-05(not yet submitted): • Added text about CCID-3 and CCID-4: • “CCID-3 and CCID-4 implementations SHOULD use this document (rfc3448bis) instead of RFC 3448.” • SHOULD or MAY, in the sentence above?

  8. Changes since draft-ietf-dccp-rfc3448bis-05(not yet submitted): • Editing in response to feedback from Gerrit Renker. • To be discussed on the mailing list.

More Related