Samuel, -
| However, in my tests, DCCP clamps the sending rate down to three packets
| per second after a short idle period (a few seconds) and then never
| attempts to increase that rate. This seems to be a very unusual and
| counter-intuitive behavior.
| Has anyone else seen similar behavior? This seems to contradict RFC4341
| section 5.1 which says that CCID2 should slow start after an idle
| period. Is this not implemented yet or is it a bug?
I took another look through the patches and found an implementation of
TCP Congestion Window Validation (CWV, RFC 2861) at home. This implements
slow-start after idle as a byproduct.
When I originally tested this I found that CWV proved very worthwhile to
have in CCID-2.
Could I thus ask you to pull
git://eden-feed.erg.abdn.ac.uk/dccp_exp [subtree 'dccp']
once again and retry with CWV (it is the ccid2_do_cwv module parameter,
per default it is on)? To me it seems likely that this could be helpful
for what you are trying to do.
The patch is at
http://eden-feed.erg.abdn.ac.uk/cgi-bin/gitweb.cgi?p=dccp_exp.git;a=commitdiff;h=9e67a3025b17d07d72d30bc48d08accb9a6487f3
and will also, per forma, be submitted to the list just now.
--
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
