In message <50188eb0.2040...@mtcc.com> Michael Thomas writes: > Since I apparently got a few heads shaking today from my jabber > comment, I guess I should at least throw it on the list. > > My observation -- and I'm not necessarily saying it's a [good] > solution -- is that one way that we could deal with the ambiguity of > what fridge.local[site] means when I elsewhere is to say that > .local[site] is exactly what it says it is: a property of the local > site. As such, if I'm roaming and do not have topological > connectivity, the proper way to get that connectivity would be to use > some form of tunneling back to the .local[site] I actually intended > and thus be part of the .local[site] topology again. > > On the plus side, this puts it into the hands of somebody to deal with > the ambiguity. On the minus side, this puts it into the hands of > somebody to deal with the ambiguity. > > Mike
For a mobile device, including a laptop, sitelocal should reflect where you are. In someone else's house, printer.sitelocal should be their printer. If that someone else gives you authentication credentials or you give then a public key and they install it on the printer, then you can print. Today, more likely the home printer is USB and you plug it in to your laptop. Getting to your own fridge or printer from elsewhere would require that you have a domain name and know what your domain name is. Presumably you'd already have whatever you need for authentication. There is no ambiguity. It is a personal choice whether you want to put sitelocal first in the search path or your own domain first. I suggest that your own domain would be a better choice. fridge means the same thing no matter where you are. fridge.sitelocal means the fridge near you if you are elsewhere. fridge.sitelocal. is a FQDN with site local scope. fridge.yourdomain is a FQDN with global scope. Curtis _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
