On Tue, 3 Mar 2015, Michael Sweet wrote:
True, but most video conferencing software and live video feeds handle
disconnects gracefully (enough) already, and most streaming video is not
done using a single file/URL but with a series of files/URLs, with each
file/URL representing a "chapter" or other divisible unit within the
program/movie being watched - there you will either seamlessly
transition to the new address when the next chapter is fetched, or the
application will detect the lost connection/stalled data and then
attempt a reconnect which gets the new address.
So don't assume there will be problems when a network is renumbered - a
lot of the work that's been done to deal with unreliable networks is
equally useful for network changes, so long as the client application
does not assume the network address of a named service won't change.
So where is the sweet spot? 10 minutes? 30 minutes? 1 hour? 3 hour? 6
hour? 12 hour?
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.
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.
Mosh fixes this with a 1-2 second outage.
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.
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.
--
Mikael Abrahamsson email: [email protected]
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
