On 9/25/07, Gerrit Renker <gerrit@xxxxxxxxxxxxxx> wrote: > Ian McDonald wrote: > | + * 16-20ms to match the typical multimedia inter-frame interval > | > + * 100ms as a reasonable compromise [default] > | > + * 1000ms corresponds to the lower TCP RTO bound (RFC 2988, 2.4) > | > + > | > | But Linux actually uses 250 ms for TCP here, not 1000 ms. You might > | want to add that. > | > The others are not guilty of this change - the text was copied verbatim from the CCID3 menu. > And the CCID3 menu was copied from emails on dccp@ietf. I think Colin Perkins suggested the > lower, frame-based value, whereas 100ms were suggested by Mark Handley. Good to know about > the Linux value -- this is all meant for experimentation, maybe the 1000ms can then go? > I have been using the default of 100ms for a long while, but not done feedback loss tests. I've just cced you all in on something I dug up through the iccrg list not so long ago. Makes interesting reading. Regards, Ian -- 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
