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] The IoT WG Charter

Previous message (by thread): [iot-wg] ENISA study "Baseline Security Recommendations for IoT in the context of CII" is out
Next message (by thread): [iot-wg] next steps for the new WG

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Jim Reid jim at rfc1035.com
Wed Nov 29 14:01:58 CET 2017

In case anyone’s not noticed, the IoT WG was created at RIPE75. Those who were on the (now closed down) iot-discussion mailing list have been migrated to the WG’s list iot-wg at ripe.net. There’s also a home page for the new WG: https://www.ripe.net/participate/ripe/wg/iot. Many thanks to Marco and his colleagues at the NCC for taking care of that.

There was a little bit of wordsmithing on the proposed charter in Dubai. Here’s the text that got consensus in the IoT plenary.

• To discuss challenges and opportunities of "IoT” for the RIPE community
• To serve as a focal point for the RIPE NCC regarding community input to their IoT activities, including liaisons with other organisations
• To invite IoT communities for a dialogue on matters of operational relevance, including security, the numbering system, and applicability of standards
• To develop positions of the RIPE community on IoT matters

Thanks to everyone who contributed to this text.

Previous message (by thread): [iot-wg] ENISA study "Baseline Security Recommendations for IoT in the context of CII" is out
Next message (by thread): [iot-wg] next steps for the new WG

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ iot-wg Archives ]