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, though I might want to discover it were I to get an off-the-shelf IP enabled version from, say, oregon scientific. 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. 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. That browser-centric view of the world knows nothing about .local. 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. So there's one problem. Mike _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
