... If the key is generated randomly for each network, that's fine, but then how do the new nodes join? Either they get programmed with the randomly generated key for the particular network that they want to join
OK, ...
(which is not an acceptable solution to most end users) ...
Why don't users find this acceptable? It seems to me that vendors ought to provide tools that make this configuration process painless. Is the problems that vendors aren't delivering tools that make this configuration simple and painless? Or, do customers not want to have incoming products flow through a common point or process? It seems to me that some level of technical competence is necessary to install or even replace these nodes, and that this level of technical of competence ought to be adequate to pre-configure nodes (assuming that adequate tools are available). Of course, if these tools could be used by field technicians, then incoming nodes wouldn't have to flow through a common location or process. Alternatively, this pre-configuration seems to be something that vendors ought to provide, (as a service). (Presumably, this would stimulate the development of tools that would make the configuration process simple and painless.) Of course, it's not clear whether distributors would want to provide this process. Is there any technical reason that simple, reliable, end-user configuration tools couldn't be developed that pre-configure network-specific keys? -tjs _______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
