On Tue, 3 Mar 2015, Ted Lemon wrote:
Why? The only case where it will matter is for long-lived connections that can't restart. So your overnight ssh, or your very long download. Any other use will survive the renumbering event because you gave an hour's notice. Deprecated addresses already shouldn't be selected for new connections by the stack--there's no need to modify the application.
Yes, but I want to make sure also these long lived connections can survive the renumbering event.
I use "mosh" which gives me this for my ssh. I have completely stopped using TCP for ssh, because it just sucks. Right now I connect to a wifi and before I can basically switch to my terminal application, mosh has already reconnected. This is how I want things to work.
I can imagine a stream video application that uses a single TCP session, and watching a movie over this can easily take more than an hour. I need to check, but I would imagine for instance xbmc accessing a http(s) based file server would just use a single TCP session for the entire session. I can verify this if it's of interest.
-- Mikael Abrahamsson email: [email protected] _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
