Hi, Let me jump-in from home appliance manufacturer perspective.
(2013/03/14 9:41), Michael Thomas wrote:
Recall that my initial point is that the arch document should provide more background, motivation and most especially requirements. There is *none* of that right now. My push back about "common" is against the notion that this is all self-evident. It's not.
As Chris mentioned in his presentation, protocols and services become complex day-by-day, but users don't. We can memorize many IP address, domain names, or URLs to select/specify communcation endpoint. But we cannot expect our home customers to do so.
Applications in home networks (including M2M applications like SEP2 but not limited to) naturally have their goal to communicate, but does not have a priori knowledge of the surrowinding environment. Thus they need some binding mechanism between a goal and communication endpoints that serve for the goal. In general, this kind of mechanism is called 'service discovery'.
Hoping it helps the discussion. // Yusuke DOI <[email protected]> _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
