Re: The RTO=4*RTT thing in TFRC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> I am not a co-author of TFMCC, so I don't know all of the
> design decisons.

so I owe you even more thanks for taking the time to
deal with this stupid error that I made:


> The response function in RFC3448 (TFRC) is as follows:
>
>                                  s
>     X =  ----------------------------------------------------------
>          R*sqrt(2*b*p/3) + (t_RTO * (3*sqrt(3*b*p/8) * p * (1+32*p^2)))
>
> By using b=1 and t_RTO=4 RTT, you get the following:
>
>                                  s
>     X =  ----------------------------------------------------------
>          R*(sqrt(2*p/3) + (12 *(sqrt(3*p/8) * p * (1+32*p^2))))
>
> (Note the parentheses after R in the denominator.)

of course! Indeed I overlooked the parantheses, and
I'm extremely sorry for wasting your time with this.


> (Given that X is the transmit rate in bytes per second, I don't
> see why the factor of 8 is ok.  But it does use t_RTO = 4 RTT.)

oh, I was wrong when I looked at this at first -
the real reason for the factor of 8 is that in
the TFMCC spec, X is in bits/second.

So everything's fine and I was just confused, sorry again.

Cheers,
Michael



[Index of Archives]     [Linux Kernel Development]     [Linux DCCP]     [IETF Annouce]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [DDR & Rambus]

  Powered by Linux