>>>>> "Curtis" == Curtis Villamizar <[email protected]> writes: Curtis> The issue is what happens when *my* fridge is not on the same home Curtis> subnet as *my* home computer. (Sustituting a more realistic example, Curtis> like thermostats, water heater, alarm system, etc, where temp/time Curtis> profiles might be altered, but we'll stick with the fridge Curtis> example).
this is an issue, and we have some proposals to solve this.
It's not the issue that I'm talking about. I'm saying that I want to
leverage the sitelocal host discovery protocol to also discover a global
name for the host. I'm suggeting that an application (e.g. browser,
cups, etc.) on a mobile device should never (by default) actually
bookmark "fridge.local", because it's not globally meaningful.
Curtis> A separate issue is how to address the fridge from a computer at
work
Curtis> or a mobile phone where clearly neither are on the same site. Here
a
Curtis> domain name has to be assigned and most likely something of the form
Curtis> <subdomain>.<provider-fqdn> if there is not going to be a
registration
Curtis> fee. The subdomain might be the same as the email address provided
by
Curtis> most home providers or <email>.site.<provider-fqdn>. At worst the
Curtis> mobile phone would need to have <email>.site.<provider-fqdn> in the
Curtis> DNS search path so "fridge" can be resolved.
Curtis> The sitelocal name then only serves a purpose when the site is not
Curtis> connected to the provider and doesn't know its domain name.
It's not a hard problem, technically (layer 1-7)
It's a hard layer 8/9 problem, and I'm suggesting that maybe we need to
think about whether there are layer-5/6/7 things that we can do as we
are specifying the sitelocal discovery process to ease the layer 8/9
problem.
--
Michael Richardson <[email protected]>, Sandelman Software Works
pgpep1mIIPkH8.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
