This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[iot-wg] [BCOP] Adressing Thread & Matter for IoT
- Previous message (by thread): [iot-wg] [BCOP] Adressing Thread & Matter for IoT
- Next message (by thread): [iot-wg] work on revised IoT BCOP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Poonam Yadav
poonam.hiwal at gmail.com
Wed Mar 8 14:12:30 CET 2023
Hi Peter, I would be happy to volunteer myself for discussion on this topic. Best, Poonam On Wed, Mar 8, 2023 at 12:40 PM Peter Steinhäuser <ps at embedd.com> wrote: > Dear collegues, > > since the IoT WG released it's first BCOP document [1] some time has > passed. Several technologies discussed in the document – i.e. DPP, USP – > have become mandatory for large carriers and can be found the majority of > their roadmaps. The considerations regarding secure onboarding can also be > found in works of other researchers and became common ground – I think this > document was a good and useful first step, but technologies are evolving > and new options and requirements surface. > > Recent talks with carriers revealed that all intend to increase their > efforts in managing IoT devices in their customer's homes or start such > efforts. All of them refer to Thread [2] and Matter [3] as the technologies > of choice – which makes sense given that at these standards increase > compatibility and are backed up by large players like Google, Amazon & > Apple. Since Thread is based upon IPv6 it offers new options and > possibilities to integrate with existing network infrastructure an > standards. Nevetheless it also requires re-evaluation of threats and attack > vectors in such networks. > > I would like to initiate work on a follow-up BCOP document that centers > around the changes Thread and Matter do introduce to networks, but that > also takes into account our findings that got incorporated into the fist > BCOP document this WG has released. Especially the challenges regarding > onboarding and security in general remain the same and would be needed to > be evaluated in regards to the new technologies. > > An IPv6 based IoT networking protocol offers also new possibilities for > integrating IoT devices into networks and can change the way we look at > such networks. This should also be part of such a document. > > I would like to ask the members of this WG about their opinion about these > considerations. And I also want to ask for volunteers to work an such a new > BCOP document and would be glad to initiate and manage the process. > > Sincerely, > Peter > > [1] https://www.ripe.net/publications/docs/ripe-759 > [2] https://openthread.io/guides/thread-primer > [3] https://csa-iot.org/all-solutions/matter/ > *Peter Steinhäuser, CEO* > embeDD GmbH · Alter Postplatz 2 · 6370 Stans · Switzerland > Phone: +41 (41) 784 95 85 · Fax: +41 (41) 784 95 64 > > > _______________________________________________ > iot-wg mailing list > iot-wg at ripe.net > https://mailman.ripe.net/ > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://mailman.ripe.net/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/iot-wg/attachments/20230308/a6636f28/attachment-0001.html>
- Previous message (by thread): [iot-wg] [BCOP] Adressing Thread & Matter for IoT
- Next message (by thread): [iot-wg] work on revised IoT BCOP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]