Branching the subject line.... On 03/06/2012 11:24 PM, Colin Perkins wrote:
On 6 Mar 2012, at 13:24, Randell Jesup wrote:
On 3/6/2012 2:52 AM, Harald Alvestrand wrote:
On 03/06/2012 12:32 AM, Colin Perkins wrote:
Here's our initial attempt at a "circuit breakers" draft for RTCWeb. Comments welcome - this is very much a straw-man for discussion, rather than a final solution.
Colin Great - people have been doing this forever, but totally ad-hoc (and for different reasons).
In the past I've seen (and used) values in the 10-30 second timeframe used to drop calls with lack of connectivity, though for VoIP 30 seconds is *forever*; few people will wait that long before abandoning a phone call (more might wait that long before abandoning an online 'call', at least today). Most uses I've seen relied on the recipient to end the call, not the sender to do so via RTCP, since most failures in mid-call are loss of connectivity in both directions. A receiver-based circuit-breaker should be added too, I agree. This may be more application dependent, since a receiver that can't get packets through to the sender is not going to be able to stop the flow.
It can take various measures to get the message through to the sender that bad things are happening (RTCP, signalling), but these may be dependent on *something* working.