Mikael, > On Mar 3, 2015, at 10:34 AM, Mikael Abrahamsson <swm...@swm.pp.se> wrote: > ... > So where is the sweet spot? 10 minutes? 30 minutes? 1 hour? 3 hour? 6 hour? > 12 hour?
My guess is around 1 hour, but clearly that is something that should be tested to verify (and ideally be configurable). > I just tried this. I was on the same subnet on wired ethernet and on wifi > (etablished the call on wired with disabled wifi, enabled wifi, waited 30 > seconds, then unplugged wired) using my OSX macbook, using Skype voice > session with another skype user, and it took around 10 seconds to detect the > outage, and another 20 seconds to re-establish the call. 30 seconds is not a huge amount of time, and certainly that could be improved, but it doesn't point to a need for or that it would be useful to make massive changes to the core networking APIs... > I tried the same procedure with Facetime audio, and it disconnected the call > after 10 seconds and didn't try to establish it again until I manually did > something. I think FaceTime audio doesn't reconnect while FaceTime video does, but I'm not connected to the team that does that software so I'm not 100% sure... Regardless, that is just a marketing/HI decision, not a technical one. > Mosh fixes this with a 1-2 second outage. Good for Mosh. > I have no reason to believe the above behavior would be different if the call > was over IPv6 (which I presume it wasn't) and the address went away because > of a renumbering event. I agree. > So I'd say that at least two of the top VoIP clients on the market have no > functionality to gracefully (30 second customer outage isn't gracefully) > handling moving between two addresses. So applications need to get a *lot* > better at being endpoint address independent. Need is a strong word - certainly they do not meet your high expectations, and there is likely room for improvement, but what works for Mosh and the recovery times it has may not be reflective of what other protocols can do. _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
