Hi all,
This week we had an interesting event at INRIA Paris, the lightweight IoT security hackathon. Various onboarding / bootstrap approaches were also discussed including new ones based on the EDHOC protocol and existing ones (Thread, 6tisch, cBRSKI). What I realized there is that all these zero-touch onboarding protocols basically need and can use the same mechanism of relaying data, as described in this draft. So it should be very well possible to make a really generic join-proxy definition that works for multiple methods (also future methods - which is great - existing legacy join proxies that don't even know about these new methods will just work for them, relaying the data). We already did start discussing this approach for new BRSKI variants but I think it can equally work for non-BRSKI onboarding methods. Basically the join proxy is just relaying data without knowing what's inside - it could be any data, any format. As long as it gets delivered to the right entity (e.g. a Registrar) that knows how to parse it and what to send back. Just wanted to say this, comments are welcome but if no comments then it's also fine ;-) Regards Esko
_______________________________________________ Anima mailing list -- anima@ietf.org To unsubscribe send an email to anima-le...@ietf.org
