February 2019 - iot-wg - mailman.ripe.net

For information: ETSI releases IoT security standard
by Marco Hogewoning 17 Oct '19

17 Oct '19

Dear colleagues, The European Telecommunications Standardisation Institute (ETSI), earlier this week released their initial standard for securing IoT devices. The document is titled ‘Technical specification - Cyber Security for Consumer Internet of Things’ (ETSI TS 103 645), and states that its objective is, “...to support all parties involved in the development and manufacturing of consumer IoT with guidance on securing their products.” While it remains a very high-level document, containing many recommendations our community probably takes for granted, it could be helpful in guiding newcomers towards a more secure implementation of their IoT services and devices. The recommendations include items like, for instance, using non-default passwords. Although this is not yet a European Standard (EN) level specification, it is likely that any European standard specification in this area would be developed based on guidance from this document. In this context, a specification like this might also be reflected in product conformity guidelines such as the Radio Equipment Directive, that I posted about last week. The specification is available at https://www.etsi.org/deliver/etsi_ts/103600_103699/103645/01.01.01_60/ts_10… Regards, Marco Hogewoning RIPE NCC

4 4

InnoITeam - a new Center of Excellence in IoT Science and Technology
by Artūras Serackis 01 Jul '19

01 Jul '19

Dear Colleagues, We are excited to introduce you a new initiative a Center of Excellence in IoT Science and Technology (InnoITeam). The CoE will leverage the knowledge, experience, and resources of three Lithuanian institutions – Kaunas University of Technology, Vilnius Gediminas Technical University and State Enterprise Centre of Registers of Lithuania - with the support of two advanced EU partners from Sweden – Linköping University and Interactive Institute Swedish ICT in Norrköping. During the first five years, the Consortium will focus on four R&D topics: 1. User interfacing and interaction design approaches for Smart Environments based on IoT. 2. Cybersecurity aspects of the Smart Environments based on IoT. 3. Data analysis and visualization approaches for data-intensive IoT environments. 4. Cognitive IoT technologies for Smart Home Environments. The InnoITeam project is funded by the European Union’s Horizon 2020 research and innovation programme and coordinated by the Kaunas University of Technology. The project has been already started in September (2017) and is finishing its first phase. During the second phase in a five-year period, the InnoITeam is planning to become a self-sustaining organization, integrating and supporting research excellence and innovation development in Lithuania, the Baltic Sea region, and Europe. Meet our team and recent news on our web page: https://www.innoiteam.com Follow us on social media: https://facebook.com/innoiteam https://www.linkedin.com/company/innoiteam/ https://twitter.com/innoiteam

8 9

appointing a co-chair
by Jim Reid 08 Apr '19

08 Apr '19

Ladies and gentlemen, boys and girls, start your engines! :-) Since the WG now has an appointment process in place, it's time to use it. Anyone interested in volunteering as a co-chair is encouraged to step forward. It would be helpful if potential candidates could post on the list what their vision is for the WG and what they would/wouldn't do if appointed. I would also urge volunteers to consult RIPE692: "RIPE Working Group Chair Job Description and Procedures" to get an appreciation for what this role entails. I'll also be happy to provide advice and guidance to anyone thinking about volunteering, either in private or on the list. The tentative schedule would be to finalise a list of potential candidates by early next year and run the selection process in March or theresabouts so the new co-chair can be in place in good time for RIPE78. Please speak up if you think this schedule is unreasonable or impractical. Although I have no say in who the WG chooses -- I just make the consensus determination -- I would very much like to see someone new in the role. It would be a pity if one of the usual suspects got the job. Not that I have any criticisms of them. A fresh face, new thinking and a break from the same old routine is both healthy and desirable IMO. However that will of course ultimately be a decision for the WG to make. Over to you...

5 5

Candidature for Co-Chair
by sandoche Balakrichenan 27 Mar '19

27 Mar '19

Dear all, I would like to put my application for the co-chair role. I believe I could fit into Jim's criteria, not being among the usual suspects :-) _*About my *_ I have been working at the French domain registry (Afnic) for the last 10 years. Since the beginning, I have been carrying out multiple IoT-related initiatives and projects internally and/or with partners. My linked in profile: https://www.linkedin.com/in/sandoche-balakrichenan-2a44645/ 50% of my job profile is oriented towards technology watch, and thus involved in activities at the IETF, GS1 (RFID, Barcode standardization), AIOTI (The Alliance for the Internet of Things Innovation), RIPE, CENTR (Council for European Top Level Domains) and LoRa-Alliance. My interest in IoT includes identification, name resolution, service discovery and using DNS infrastructure as PKI for the _*Some milestones in my IoT profile:*_ * I had participated for two years at the European Commission as an invited member of the IoT expert group. * Our IoT project WINGS (how DNS could be used for service discovery in the supply chain industry?) was awarded the CENTR R&D award for 2013 (https://www.inria.fr/en/centre/lille/news/anr-verso-wings-project-wins-cent…) * Principal contributor to the ONS standard (https://www.gs1.org/sites/default/files/docs/epc/ons_2_0_1-standard-2013013…) * Contributed to LoRa-alliance (lora-alliance.org) Backend interfaces specification on DNS usage for resolving LoRa devices in the Internet. _*What I could do in the Co-chair role?*_ * Will be able to participate in all RIPE physical sessions and other side meetings which a WG co-chair is supposed to attend. * Wil be able to allocate time to follow the policy proposal relevant to the WG; follow and respond to the mailing list discussion; ensure milestones and with the help of Jim, liaise with RIPE NCC. * Will be able to allocate time for administrative activities (like soliciting contents, preparing the agenda etc.) concerning the WG If you believe i can be of use, thanks for your support. Regards, Sandoche BALAKRICHENAN

3 2

appointing another co-chair
by Jim Reid 26 Feb '19

26 Feb '19

Here's what I posted back in November: Anyone interested in volunteering as a co-chair is encouraged to step forward. It would be helpful if potential candidates could post on the list what their vision is for the WG and what they would/wouldn't do if appointed. I would also urge volunteers to consult RIPE692: "RIPE Working Group Chair Job Description and Procedures" to get an appreciation for what this role entails. I'll also be happy to provide advice and guidance to anyone thinking about volunteering, either in private or on the list. The tentative schedule would be to finalise a list of potential candidates by early next year and run the selection process in March or theresabouts so the new co-chair can be in place in good time for RIPE78. Please speak up if you think this schedule is unreasonable or impractical. Although I have no say in who the WG chooses -- I just make the consensus determination -- I would very much like to see someone new in the role. It would be a pity if one of the usual suspects got the job. Not that I have any criticisms of them. A fresh face, new thinking and a break from the same old routine is both healthy and desirable IMO. However that will of course ultimately be a decision for the WG to make. I would also ask 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. This will also make it clearer for other members of the list to express their support for a candidate.

1 0

re-rebooting the co-chair appointment process
by Jim Reid 26 Feb '19

26 Feb '19

Colleagues, we're still missing a co-chair. The last attempt to find one didn't work out. Although a couple of names were mentioned, there were very few voices of support for any of them - certainly not enough to make a sound consensus decision. It's time for one more heave. I suggest a call for nominations/volunteers/stuckees which ends on April 5th. That gives us 6 weeks for potential co-chairs to be identified and hopefully someone to emerge as the new co-chair. If the results by then are still inconclusive, I'll talk to Hans-Petter about how best to invoke article 5 of our appointment process. Let's hope it doesn't come to that. Please limit your comments on this thread to the proposed time-line and how to solve the problem of lack of WG consensus if this happens this time. I'll post another article for would be co-chairs.

1 0

Proposed Updates to EU RED Directive to increase IoT security
by Marco Hogewoning 14 Feb '19

14 Feb '19

Dear Colleagues, As I mentioned in my presentation to the Working Group during RIPE 77, the European Commission is thinking about updating the Radio Equipment Directive with the aim of improving IoT security. As a quick refresher, the RED applies to all equipment that has a radio on board. The legislation has a few broadly-defined terms regarding security and safety, which can be filled in on a later date. Last year, a number of member states floated the idea of using this option to increase security for a number of IoT devices, mostly toys and 'smart wearables’, for e.g. smart watches and step-counters. The European Commission has now opened a four week ‘feedback’ period on what is called an ‘Inception Impact Assessment’. This means the process is at an early stage and not very specific, and they are seeking feedback from stakeholders on their thoughts so far. As expected, the proposal currently does indeed target toys and wearables. Of course, this could change or be expanded later. Here are the key questions in the Inception document: - The overall objective of this initiative is to ensure an adequate level of security for internet-connected radio equipment and wearable radio equipment at the moment of placing on the market. - The following policy options and their effects for potentially affected parties (e.g. manufacturers, consumers, National Authorities) will be analysed: - Option 0, baseline scenario: a situation in which manufacturers are not obliged to implement any specific measures as it is currently the case. - Option 1, a situation whereby the industry self-regulates to implement the existing legislation which protects personal data, the confidentiality of telecommunications, security and protection against fraud. - Option 2, adoption of a delegated act pursuant Article 3(3)(e). This will require that radio equipment incorporate safeguards to ensure that the personal data and privacy of the user and of the subscriber are protected, also as a tool to enhance the cybersecurity of these products, and this requirement will have to be demonstrated for the purposes of market access. - Option 3, adoption of a delegated act pursuant Article 3(3)(f). This will require that radio equipment incorporates certain features ensuring protection from fraud, also as a tool to enhance the cybersecurity of these products, and this requirement will have to be demonstrated for the purposes of market access. - Option 4, adoption of a delegated act pursuant both Articles 3(3)(e) and (f). In this case, both requirements in Options 2 and 3 will have to be demonstrated for the purposes of market access. More information about the process and the Inception Impact Assessment is available from https://ec.europa.eu/info/law/better-regulation/initiatives/ares-2018-64269… The deadline to submit feedback is Monday, 4 March 2019. This is the very early stage of the development. If a more formal proposal is drafted based on one of these policy options, there will be another 12-week consultation period. At the same time, please be aware that this process could result in a so-called ‘Delegated Act’, which does not require the formal approval of the European Parliament or Council and can come into effect very quickly. Regards, Marco Hogewoning Senior External Relations Officer RIPE NCC ------------------ Summary ------------------ RED security Inception Impact Assessment Feedback period: 4 weeks ending on 4 March 2019 Possibly followed by a 12 week consultation period

3 3