On Mar 11, 2012, at 8:02 AM, Ralph Droms <[email protected]> wrote: > This point is what I was trying to get at with my second bullet. Ted, who is > the "you" in the "where you connected": the homenet, the device, ???
IOW, when a device is configured locally, how does that configuration propagate through the homenet gateway to the real world, when the gateway isn't necessarily connected when the device configures? My preferred answer is that the homenet gateway is authoritative for the zone that's being updated, and can process updates even when disconnected. I realize that MDNS-style solutions are in some sense easier, but they don't give you a consistent name, so you wind up with the search list problem Ray is talking about. Of course, in this scenario, if the homenet is disconnected, a roaming device would be unable to update it until it reconnected. I think this is probably okay. I realize this is a bit more heavyweight than what some people have been talking about, and I'm not claiming they're wrong and I'm right; I'm just saying that this is how I would want my homenet to work, and I think it ties into the idea of end-to-end functionality for homenets, both internally and externally.
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
