In message <[email protected]> Michael Richardson writes: > >>>>> "Curtis" =3D=3D Curtis Villamizar <[email protected]> writes: > Curtis> The issue is what happens when *my* fridge is not on the same h= > ome > Curtis> subnet as *my* home computer. (Sustituting a more realistic ex= > ample, > Curtis> like thermostats, water heater, alarm system, etc, where temp/t= > ime > 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 a= > t 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 regis= > tration > Curtis> fee. The subdomain might be the same as the email address prov= > ided 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. > > > =2D-=20 > Michael Richardson <[email protected]>, Sandelman Software Works=20
Getting sitelocal allocated should be no more difficult than getting local allocated. It is a TLD that does not resolve globally but does resolve differently at each site. It can be used in the absense of a DNS domain. It can also be used in the absense of IETF action and in the absense of provider cooperation because no one can stop you. :-) But I'm not advocating doing that. host fridge.sitelocal fridge.sitelocal is an alias for fridge.ipv6.occnc.com. fridge.ipv6.occnc.com has IPv6 address 2001:470:1f07:1545::4:f00d [ :-) no cooperation from IETF or from my provider required and no harm done. I could have made it an AAAA record rather than a CNAME. To see this you need to direct queries at my name server. fridge.sitelocal is entirely local. fridge.ipv6.occnc.com is in the global DNS. Please don't try to ping6 my fridge. It won't answer. ] Curtis _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
