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] some suggestions on "work items" for the WG
- Previous message (by thread): [iot-wg] next steps for the new WG
- Next message (by thread): [iot-wg] some suggestions on "work items" for the WG
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Wed Nov 29 15:01:14 CET 2017
Here are a few random thoughts about the sorts of things the WG might do. I hope these will spark some discussion. Please note I’m not saying the WG will or won’t adopt any of these suggestions. Or that these are the only topics of interest. This is just an attempt to get everyone to think about the WG’s activities and come forward with their own suggestions. 1) Interaction with SDOs and industry fora How could/should the WG engage with these? Do we want updates from (say) AIOTI, IETF, ETSI and so on? Are any members of the WG involved in the IoT work at these sorts of organisations? 2) Liaison with government/regulators What is and isn’t appropriate here? 3) Advice/support to the NCC The NCC gets asked about IoT. They are going to want the WG to provide advice or present the consensus view (if any) of the RIPE community. 4) Academia We had a few IoT themed presentations at RIPE75 from academics. Does the WG want more (or less) of that sort of thing? What’s the best way to collaborate with academia and what does the WG want to get from that? 5) Training & Documentation Should the WG try to develop training materials/tutorials on IoT, white papers, use cases, best practices and so on? [Probably yes.] If so, what should these focus on and are there any volunteers to help produce these? 6) IP(v6) Addressing Issues What are the main issues around IP(v6) addressing/subnetting schemes for IoT devices and networks? 7) Security Anyone interested in the security aspects of IoT, both in terms of the edge devices and their potential role in DDoS attacks like Mirai? Could the WG develop some recommendations or advice? 8) Policy Making What sort of policies (and on what) could the WG develop for the NCC to implement? 9) Tools and toys Does anyone have new/interesting tools for playing with IoT devices or have useful development environments for them, say for writing/debugging code on a Raspbery Pi or even cheaper chipsets? 10) Anything else? Er.... Let’s hear what you all have to say about the above. Or other things I’ve either overlooked or forgotten about. Over to you...
- Previous message (by thread): [iot-wg] next steps for the new WG
- Next message (by thread): [iot-wg] some suggestions on "work items" for the WG
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]