<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">First of all I want to thank Jim for his great work for this working group and his years commitment as a working group chair!<br class=""><br class="">For the designation of a new working group co-chair I put my hat (again) into the ring.<br class=""><br class="">I'm seriously concerned about the impact malicious IoT devices will have on the internet's infrastructure. My goal in the working group is defining best practices and standards about how can be best dealt with IoT devices pro-actively to keep the attacks that are already onging and will come to happen under control. Besides that I want to work on providing players from the IoT industry with better practices and - if possible - technical solutions while working with regulators to create better standards that help providing security and privacy.<br class=""><br class="">Coming from a home gateway/personal router/CPE background (DD-WRT / OpenWRT) such devices are for me potential gatekeepers that can play an important role in securing millions home small networks. Also ISP's should be brought on board, it's in their sole interest as well. To have an effect we need to try to gain a maximum traction in the industry.<br class=""><br class="">There are already activities (SPIN / IETF home gateway WG, etc.) in this field. As a working group chair I would focus working on connecting the ongoing activities to form technical standards and reference implementations for easy adoption by the industry. I would also work on advocating those to industry players (i.e. via Broadband Forum & prpl Foundation) to get broader support for these activities as well. In my role as project manager for the open source projects in the prpl Foundation I also work on selecting security related technologies for adoption / funding by the prpl Foundation and it's members.<br class=""><br class="">Being a RIPE member since years and becoming more and more familiar with the works of standardization organizations I am eager to learn more about the proceedings and how to better support the RIPE-community and other standardization organizations.<br class=""><br class="">It would be my pleasure to work closer with all of you for the better of the internet.<div class=""><br class=""></div><div class="">Sincerly,</div><div class="">Peter<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 20.04.2020 um 18:44 schrieb Jim Reid <<a href="mailto:jim@rfc1035.com" class="">jim@rfc1035.com</a>>:</div><br class="Apple-interchange-newline"><div class=""><div class="">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.<br class=""><br class="">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.<br class=""><br class="">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.<br class=""><br class="">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).<br class=""><br class="">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.<br class="">_______________________________________________<br class="">iot-wg mailing list<br class=""><a href="mailto:iot-wg@ripe.net" class="">iot-wg@ripe.net</a><br class="">https://lists.ripe.net/mailman/listinfo/iot-wg</div></div></blockquote></div><div class=""><div id="sig" style="border-top: dotted 1px #999999; padding-top: 10px; padding-botton: 10px; margin: 11px 0; font-family: 'Lucida Grande', Verdana, Arial, Sans-Serif; font-size: 11px;" class=""> <img src="https://file.as201155.net/f/5572ae1c73f64c0caea4/?dl=1" width="180" height="38" align="left" style="margin-right: 20px; padding-top: 2px;" class=""> <div style="color: #999999;" class=""> <strong style="color: #333333;" class="">Peter Steinhäuser, CEO</strong><br class=""> embeDD GmbH · Alter Postplatz 2 · 6370 Stans · Switzerland<br class=""> Phone: +41 (41) 784 95 85 · Fax: +41 (41) 784 95 64 </div> <div style="clear: both;" class=""></div> </div> </div> <br class=""></div></body></html>