Re: [homenet] Let's make in-home ULA presence a MUST !?

[Mark Andrews <[e-mail]>]

In message <[e-mail]>, Michael Thomas writes:
> 
> On 10/15/14, 3:49 PM, Ted Lemon wrote:
> > On Oct 15, 2014, at 3:01 PM, Michael Thomas <[e-mail]> wrote:
> >> See, I don't find that ideal at all. If I'm swinging around on my backyard
>  trapeze watching
> >> the flying wallendas instructional video from my home jukebox, I really do
> n't want to have
> >> my network break connectivity because I happened to switch to my neighbor'
> s wifi and I
> >> was using a ULA when I could have kept connectivity with a GUA.
> > This is simply a non-sequitur.   It has nothing to do with homenet.   It ha
> s to do with how the stack works on your home, and what the propagation of ra
> dio waves looks like in your back yard.   The assumption that you will be abl
> e to access your jukebox over your neighbor's wifi contains packed in it so m
> uch new protocol work we could fork several working groups to handle it.
> If I use a GUA to my jukebox, the routing will just work regardless of which
> AP I'm currently connected to. With ULA's, not so much. That's hardly a 
> non-sequitur.
> 
> ULA's with mobility are very problematic IMO. I'm a lot more likely to 
> wander onto my
> neighbor's home network than to suffer a flash renumbering from one of 
> my providers.
> Mobility considerations aren't a distant future, they're now.
> 
> Mike

And when you move onto your neighbour's net you will be switching
ssid's and even if you open up your router to allow the traffic in
the BCP 38 filtering should be blocking your packets leaving your
neighbors router.

Now if you want to set up a tunnel between you and your neighbour
to make this work that's fine.  If you don't you will have a different
set of addresses on either network including ULA addresses.  Unless
you have really old stacks your device will pick the new GUA first
to talk to your jukebox when you are on your neighbor's network and
the ULA to talk to it when you are on your own.

Even if you have a old stack, if the application has taken the
lessons from Happy Eyeballs and made it more generic by decreasing
the time before starting the next connection attempt to 100's if
milliseconds when you have multiple server addresses, the resulting
HE algorithms would have fixed the issue for you when it fast failed
to the GUA of the jukebox after changing ssids.  Longest match would
result in the new GUA being used rather than the new ULA.

I tried hard to get the IETF to listen to this for HE.

Mark

> _______________________________________________
> homenet mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/homenet
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: [phone]                 INTERNET: [e-mail]