On 7/13/07, Gerrit Renker <gerrit@xxxxxxxxxxxxxx> wrote: > [DCCP]: Use maximum-RTO backoff from DCCP spec > > This removes another Fixme, using the TCP maximum RTO rather than the value > specified by the DCCP specification. Across the sections in RFC 4340, 64 > seconds is consistently suggested as maximum RTO backoff value; and this is > the value which is now used. > > I have checked both termination cases for retransmissions of Close/CloseReq: > with the default value 15 of `retries2', and an initial icsk_retransmit = 0, > it takes about 614 seconds to declare a non-responding peer as dead, after > which the final terminating Reset is sent. With the TCP maximum RTO value of > 120 seconds it takes (as might be expected) almost twice as long, about 23 > minutes. > > Signed-off-by: Gerrit Renker <gerrit@xxxxxxxxxxxxxx> Signed-off-by: Ian McDonald <ian.mcdonald@xxxxxxxxxxx> -- Web1: http://wand.net.nz/~iam4/ Web2: http://www.jandi.co.nz Blog: http://iansblog.jandi.co.nz - 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
