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/iot-wg@ripe.net/
[iot-wg] work on revised IoT BCOP
- Previous message (by thread): [iot-wg] work on revised IoT BCOP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Steinhäuser
ps at embedd.com
Fri Mar 24 08:42:22 CET 2023
> Am 23.03.2023 um 19:40 schrieb Michael Richardson <mcr+ietf at sandelman.ca>: > > > In a thread that I lost, Peter asked: > >> 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. > > That's really news to me. I guess maybe this is about USP more than it is > about DPP. I'm unware that DPP has become mandatory. You can see DPP in the context of the EasyMesh efforts - not in regards to USP. While mesh topologies are also getting covered by USP I think that DPP is not a topic, yet. > As for the USP (TR-369), I'd like to know more: it's quite a fungible spec, > and what part exactly has become mandatory, and what transports? > In our BCOP, we said we needed a standard phone/browser <-> home gateway API > such that we could have innovation at the edge. > (Right now, it's a market vertical with a new app for every home gateway) From what I can see in the projects the major use case for USP (TR-369) will be replacing TR-069 for managing the gateways. But so far the large carriers do not seem to have a migration strategy, yet. Since both transports (TR-369 & TR-069) use the same underlying data model (TR-181) that’s technically not a huge step. > So I'd love to have some discussion, maybe there are even presentations, > about where we are here. > >> 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. > > yes, but I think that the carriers are gonna find that they have some serious > privacy implications if they get involved. I think that it is gonna bite > Google and Apple and Amazon too. > >> 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. > > One thing that might be useful is to have a Thread and Matter (they are > different and also dependant) reference networks that we could play with in > person at a future RIPE meeting. Probably too soon for Rotterdam, but maybe > in the fall. (Wherever that will be) I think organizing a Hackathon or similar might be an approach, what do you think? >> 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. > > In general, I think that it's too soon to say anything useful in a new > document in 2023, but that we should be spending some time understanding > what's going on. I think you’re right, there are a lot of announcements but what really happens needs to be seen… Thanks! Peter > -- > Michael Richardson <mcr+IETF at sandelman.ca> . o O ( IPv6 IøT consulting ) > Sandelman Software Works Inc, Ottawa and Worldwide > _______________________________________________ > 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 -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6125 bytes Desc: not available URL: </ripe/mail/archives/iot-wg/attachments/20230324/79bc276d/attachment.p7s>
- Previous message (by thread): [iot-wg] work on revised IoT BCOP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]