Dear colleagues:
I have seen a lot of emails with the "HNCP security" heading. However,
is there a concise technical description of the security services to be
provided, the trust lifecycle of a device and network, including
configuration and authorization model?
The description below seems to only deal with group membership
enlargement (adding a new device), but not with pruning membership
(removal of a device, e.g., the one from a house guest that left). It
may very well be that one can connect a laptop to one of two printers,
where some user input is decided to determine which one, etc, etc.
Best regards, Rene
On 9/18/2014 12:43 AM, Mikael Abrahamsson wrote:
On Wed, 17 Sep 2014, Michael Thomas wrote:
Global symmetric keys certainly have their problems, but using public
keys have their own. Namely, if I want to enroll a new device each
other currently enrolled device needs to know about the public key of
the new enrollee. For 2 devices, that's possibly manageable but for
more I really don't want to run around my house looking for every
homenet device to enroll the new one.
If we were to do that, it might be nice to have a distributed
database of homenet devices such that I only had to enroll it on one
of my homenet devices, and then it's distributed to the rest.
That is exactly what I tried to propose.
--
email: [email protected] | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
