[R-C] Congestion control requirements - I-D format, -01a version
Harald Alvestrand
harald at alvestrand.no
Sun Mar 4 11:49:03 CET 2012
On 03/04/2012 11:42 AM, Fred Baker wrote:
> You realize that this mechanism, whatever it turns out to be, has one of the problems of reliable multicast; if the RTP service is one to many, the RTCP service is many to one, and that can be a lot for the one. You find yourself wanting to find some way to collude with it.
>
> If for example it is built on conex, it will collect CE flags in the outbound path, and you will want some way of reporting the fact back. Imagine it's 1:1000000, CE gets set on the first hop out, and a million receivers decide to reply...
Yep, I regard the multicast case as a distraction for RTCWEB, however,
since it seems that trying to solve both multicast and unicast at the
same time usually results in either no solution or no deployment.
Another thing to make clear in the introduction - that this is solving
for the unicast case....
More information about the Rtp-congestion
mailing list