The code here predates me but I think the reason for it might be to do with RFC4342 (remember to read 3448 in conjunction with this). If the sender never receives a feedback packet from the receiver, and as a consequence never gets to set the allowed sending rate to one packet per RTT, then the sending rate is left at its initial rate of one packet per second, with the nofeedback timer expiring after two seconds. The allowed sending rate is halved each time the nofeedback timer expires. Thus, if no feedback is received from the receiver, the allowed sending rate is never above one packet per second and is quickly reduced below one packet per second. NB I'm not saying the old code is correct - I'm just guessing that the above is reason for it... Your thoughts Gerrit? (I haven't re-read the code or checked any of it out properly)
Just realised I didn't explain what I actually meant. I'm wondering whether initially no feedback timer was used to maintain 1 packet per second (which is the wrong way to do it). -- Ian McDonald Web: http://wand.net.nz/~iam4 Blog: http://imcdnzl.blogspot.com WAND Network Research Group Department of Computer Science University of Waikato New Zealand - 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
