<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi, Jim!<div class=""><br class=""></div><div class="">Strongly agree!</div><div class=""><br class=""></div><div class=""><div class=""> <div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Sincerely,</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"><br class=""></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Vahan Hovsepyan</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">External Relations Officer</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Caucasus and Central Asia</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">RIPE NCC</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Tel. +374 94 258900</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">E-mail: <a href="mailto:vhovsepyan@ripe.net" class="">vhovsepyan@ripe.net</a></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><br class="Apple-interchange-newline"> </div> <br class=""><div><blockquote type="cite" class=""><div class="">On 25 Oct 2017, at 14:00, <a href="mailto:iot-discussion-request@ripe.net" class="">iot-discussion-request@ripe.net</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Send iot-discussion mailing list submissions to<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:iot-discussion@ripe.net" class="">iot-discussion@ripe.net</a><br class=""><br class="">To subscribe or unsubscribe via the World Wide Web, visit<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>https://lists.ripe.net/mailman/listinfo/iot-discussion<br class="">or, via email, send a message with subject or body 'help' to<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>iot-discussion-request@ripe.net<br class=""><br class="">You can reach the person managing the list at<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>iot-discussion-owner@ripe.net<br class=""><br class="">When replying, please edit your Subject line so it is more specific<br class="">than "Re: Contents of iot-discussion digest..."<br class=""><br class=""><br class="">Today's Topics:<br class=""><br class=""> 1. Outcome of the RIPE 75 Charter Discussion (Marco Hogewoning)<br class=""> 2. Charter for IoT WG (Jim Reid)<br class=""> 3. another step towards the IoT WG (Jim Reid)<br class=""><br class=""><br class="">----------------------------------------------------------------------<br class=""><br class="">Message: 1<br class="">Date: Tue, 24 Oct 2017 16:19:57 +0400<br class="">From: Marco Hogewoning <marcoh@ripe.net><br class="">To: iot-discussion@ripe.net<br class="">Subject: [iot-discussion] Outcome of the RIPE 75 Charter Discussion<br class="">Message-ID: <EEDA252E-65B9-4B5B-81D4-FBDC6C11A4F8@ripe.net><br class="">Content-Type: text/plain; charset=utf-8<br class=""><br class="">Dear colleagues,<br class=""><br class="">As we wrapped up the discussion, here is the text that the meeting agreed to present on Thursday:<br class=""><br class="">- To discuss challenges and opportunities of "IoT? for the RIPE community<br class="">- To serve as a focal point for the RIPE NCC regarding community input to their IoT activities, including liaisons with other organisations<br class="">- To invite IoT communities for a dialogue on matters of operational relevance, including security, the numbering system, and applicability of standards<br class="">- To develop positions of the RIPE community on IoT matters<br class=""><br class="">With the note that once the plenary agrees to start the Working Group, it can review its charter and think about adding text as per Jim?s suggestion.<br class=""><br class="">The session video archives are already online and available via https://ripe75.ripe.net/programme/meeting-plan/iot/<br class=""><br class="">And thanks to Jim Reid for volunteering to lead this effort in the closing plenary on Thursday and become the ?chair elect? to help start this Working Group once the plenary agrees.<br class=""><br class="">From my side, thanks for all the support during this process and of course the attendance and comments received during the session. RIPE NCC remains committed to support this effort and are happy to assist where we can.<br class=""><br class="">Looking forward to the discussion on Thursday.<br class=""><br class="">Regards,<br class=""><br class="">Marco Hogewoning<br class="">RIPE NCC<br class=""><br class=""><br class="">------------------------------<br class=""><br class="">Message: 2<br class="">Date: Wed, 25 Oct 2017 08:26:25 +0100<br class="">From: Jim Reid <jim@rfc1035.com><br class="">To: iot-discussion@ripe.net<br class="">Subject: [iot-discussion] Charter for IoT WG<br class="">Message-ID: <3B812FBB-410D-4023-923F-3BB381006E60@rfc1035.com><br class="">Content-Type: text/plain; charset=utf-8<br class=""><br class="">For those of you who weren't in Dubai and didn't follow the web cast, there was strong consensus in the room for the following text as the WG's charter:<br class=""><br class="">? To discuss challenges and opportunities of "IoT? for the RIPE community<br class=""><br class="">? To serve as a focal point for the RIPE NCC regarding community input to their IoT activities, including liaisons with other organisations<br class=""><br class="">? To invite IoT communities to for a dialogue on matters of operational relevance, including security, the numbering system, and applicability of standards<br class=""><br class="">? To develop positions of the RIPE community on IoT matters<br class=""><br class=""><br class="">If anyone has concerns or comments about the (hopefully final) charter, please speak up now.<br class=""><br class="">The charter text is going to go for approval at the closing plenary tomorrow, at which point the WG will be created.<br class=""><br class=""><br class=""><br class=""><br class="">------------------------------<br class=""><br class="">Message: 3<br class="">Date: Wed, 25 Oct 2017 08:48:43 +0100<br class="">From: Jim Reid <jim@rfc1035.com><br class="">To: iot-discussion@ripe.net<br class="">Subject: [iot-discussion] another step towards the IoT WG<br class="">Message-ID: <9C052755-709C-4565-96E7-D2C3C891403C@rfc1035.com><br class="">Content-Type: text/plain; charset=us-ascii<br class=""><br class="">I have volunteered to serve as an initial co-chair of the WG-to-be. There was strong consensus for this at the plenary session yesterday.<br class=""><br class="">Assuming tomorrow's plenary endorses that decision, the first thing to do is to get the WG to reach consensus on a co-chair selection process. Once that's in place, we'll use the process to appoint co-chairs. My preference would be to get the selection process decided before we discuss potential candidates and ask for volunteers. Best not entangle these things.<br class=""><br class="">A few people have expressed interest in becoming a co-chair and some of them thought I'd make the decision. I won't. The WG will decide that using whatever selection process we agree. There will be a public announcement in due course inviting people to volunteer/nominate candidates.<br class=""><br class="">We should also discuss the requirements and responsibilities for the IoT WG's co-chairs. That may need some clarification before we use the selection process once we have one. My personal opinion is co-chairs might need to engage with SDOs, industry fora and participate in IoT-related workshops like that ENISA/Europol thing last week. However this will be something for the WG to decide.<br class=""><br class=""><br class=""><br class=""><br class=""><br class="">------------------------------<br class=""><br class="">Subject: Digest Footer<br class=""><br class="">_______________________________________________<br class="">iot-discussion mailing list<br class="">iot-discussion@ripe.net<br class="">https://lists.ripe.net/mailman/listinfo/iot-discussion<br class=""><br class=""><br class="">------------------------------<br class=""><br class="">End of iot-discussion Digest, Vol 11, Issue 9<br class="">*********************************************<br class=""></div></div></blockquote></div><br class=""></div></body></html>