August 2020 - iot-wg - mailman.ripe.net

it's co-chair selection time!
by Jim Reid 16 May '22

16 May '22

My term as WG co-chair ends at RIPE80 or theresabouts. I will not be standing for another term. First of all, bringing in new and hopefully younger faces to freshen things up is long overdue. Second, I only volunteered to bootstrap the new WG. That has been completed. So it’s time to step away and let the WG find somebody else. There’s some info on WG co-chair responsibilities in RIPE692. Anyone interested in applying who wants more advice on what the job entails, likely time commitments and so on is welcome to contact Sandoche or myself. Or any other recent/current WG co-chair for that matter. I would also ask potential candidates to start a *new thread* -- eg "Your name for co-chair" or something like that -- when they post on the list so there are meaningful and relevant Subject: headers which make it easier to make a consensus judgement. It’ll save the current co-chairs reading every message on the mailing list to decide if they contain something in favour or against a particular candidate. This will also make it clearer for other members of the list to express their support (or not) for a candidate. Anyone can volunteer to become a co-chair and you can even nominate yourself. There’s no requirement to have N people nominating a candidate for them be considered for selection (for values of N > 1). Ideally, it would be good to be able to announce the new co-chair at RIPE80. Though that could be too short notice since the meeting’s just under 4 weeks away. If you think more time is needed to decide, please speak up. There’s no firm deadline and we should take our time about making this appointment - provided of course the new co-chair is in place in plenty of time for RIPE81. Although I think 4 weeks (ish) should be long enough to find a new co-chair, this is for the WG to decide too.

11 19

Fwd: interesting article?
by sandoche Balakrichenan 19 Aug '20

19 Aug '20

Dear all, Vesna (RIPE) send us this document (https://www.cigionline.org/publications/standards-cybersecure-iot-devices-w…) to check if it could be interesting for the group. After skimming through it, I felt that the document could be useful, even though the contents are not entirely new AFAIK. Sandoche.

2 2

[Defcon 2020] Paul Marrapeses' speech about IoT P2P protocol design flaws
by Peter Steinhäuser 10 Aug '20

10 Aug '20

Dear Collegues, Paul Marrapese did some excellent work on researching about protocol vulnarabilities in popular IoT devices. https://www.youtube.com/watch?v=Z_gKEF76oMM Unfortunately I did not find a transcript, yet. Nevertheless the conclusion is to keep IoT devices disabled to communicate with the internet if possible and it also shows - again - the lack of interest from the device makers to adress the security flaws. Wishing you all a productive week and stay healthy. - Peter

2 1