Quoting Ian McDonald:
| > Note: At some point of time this probably needs update wrt rfc3448bis, but
see
| > http://www.mail-archive.com/dccp%40ietf.org/msg00426.html
| >
|
| I agree that sending rate calculation, particularly after idle still
| needs work - but this is at the IETF level and this helps a lot by
| the looks.
Fully agree with that point and this should be revised as soon as there is some
stabilisation in the specification. Out of my head, the following things more or
less directly depend on this:
* Oscillation Prevention from RFC 3448 / rfc3448bis
- affects also `congestion control on LANs' (a point you raised)
- with the RTTs measured on layer 4, this would be useful
since when sending `blasts' of packets, the queue buildup is quickly
perceivable
* Faster Restart
* the CCID 3 definition of idle times - RFC 4342 (6.4) uses the max(0.2 sec,
2*RTT)
* ... other areas depending on the calculation I may have missed
-
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
