Hello, sorry to break the threading by not replying directly to a post, but until now I have only been reading the list passively. So I have no mail to reply to...
I followed your discussion regarding group multicast and how to encrypt them. I see the problem, but I think one single approach to solve it either way will not be enough: - The 200ms barrier for lighting products is quite fix. If we build products with a reaction time that is too long, nobody is going to use it. - On the other hand, I am scared of IoT products that could have bigger latency, but still use a somewhat weaker crypto. I'm thinking of Fire/Smokedetectors at big airports or the like. Even toggling all lights of an airport in a one-second rhythm could cause huge problems. - So we need both, but can hardly have it. For me, this leads to multiple security levels: 1) Basic security: fast response, low cost with lower security: use symmetric keys. Use this where the risk is low. 2) High security, low cost: Allow slow(er) response times, because of the ECC calculations. Kind of a compromise... 3) High security, higher cost: add some crypto hardware. For high risk environments with low latency I don't think that we will be able to cover the whole range of requirements with one single approach. Implementing the lowest level would be relatively easy for first concepts. Best regards, Markus Grunwald Development Engineer OSRAM GmbH DS D LMS-COM DE-1 Parkring 33 85748 Garching, Deutschland Tel. +49 89 6213-3678 mailto:[email protected] www.osram.com Bitte prüfen Sie der Umwelt zuliebe, ob der Ausdruck dieser Mail erforderlich ist! OSRAM GmbH: Vorsitzender des Aufsichtsrates: Peter Bauer; Geschäftsführung: Dr. Olaf Berlien (Vorsitzender), Dr. Stefan Kampmann; Sitz der Gesellschaft: München; Registergericht: München, HRB 201526; WEEE-Reg.-Nr. DE 71568000
_______________________________________________ Ace mailing list [email protected] https://www.ietf.org/mailman/listinfo/ace
