On Aug 6, 2012, at 2:30 PM, Michael Thomas <[email protected]> wrote: > I've been rereading the charter and the -arch document and they both > seem to make a presumption that we actually know what the problems > are in a homenet. At the very least, I'm not convinced that we've captured > what those problems are. The charter seems to say that we have some > tools (dns, zeroconf...) that we should be able to tweak. The -arch document > seems to be very "device" oriented -- as in from the dns-sd perspective, > where my printer is the canonical example. I think there's more to this. > > Maybe an example is in order. I have a weather station: > > http://mtcc.com/~mike/sanchez.php > > This is not a service to be discovered like a printer, Why not?
> though I might want > to discover it were I to get an off-the-shelf IP enabled version from, say, > oregon scientific. Isn't that the kind of thing we're talking about? If your weather station doesn't do IP, then perhaps it's simply out of scope. > It's much more like a web site. I want to be able to see > it not only at home, but when I'm away so that I can see whether my > Pioneer house has snow in the driveway. > Sure. > I've done this using v4, but I'm a geek. What I think we want to enable is > non-geeks to be able to install these kinds of devices in a v6 world > with some minimum muss and fuss. That is, we need to account for not > just services, but *servers* in the form of traditional web-headed servers. > That is, the normal browser-centric view of the world. > Right, which is why I can bookmark things like OranHomeNas1.local, and my browser does mDNS lookups and finds it just fine. > That browser-centric view of the world knows nothing about .local. What browser are you using? Safari and I think Chrome know about .local just fine. > Nor > do I want to learn about .local either. I want to have a real name that I > can use as a real URL to send -- as I just did -- to people that might want > to see my weather station. And I want -- literally -- for my mother to be > able to do the same. It is beyond her now. > For that you definitely need a global DNS domain registration, so we've cycled back to where we started - things you want to be accessed globally from anywhere on the internet need global names that can be resolved from anywhere on the internet. > So there's one problem. > Yes, and a fairly hard one given the manual/administrative nature of domain registrations and the geek factor of secure dynamic DNS updates for all services to the global DNS. Much as it would be great for Homenet to solve this problem and get a lot more functionality for users, this may be a bridge too far for the current work, which is focused on getting routing and naming INSIDE the home seamless and completely auto-configuring. I think the problem of disambiguating names of resources in the home has to be dealt with to prevent users whose devices are mobile from violating the principle of least astonishment. I don't think the ability to resolve names of home resources from anywhere on the Internet has to be solved in order to solve the disambiguation problem. > Mike > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
