Internet of Things Working Group Agenda

Thursday, 23 May 11:00 - 12:30

1. Administrivia

2. ITU Study Group 20 Update (remote presentation) [5 min]

Patrik Fältström, Netnod

3. RIOT Summit Report [5 min]
Matthias Wählisch, Freie Universitaet Berlin
4. RIPE Atlas: Ethical, Security and Legal Aspects of Running an IoT Network [20 min]
Mirjam Kühne, RIPE NCC

RIPE Atlas is a global active measurement infrastructure, maintained by the RIPE NCC based on the voluntary contributions of thousands of probe hosts worldwide. In essence, those RIPE Atlas probes are IoT devices that people place in their homes. In this presentation, we will present the ethical, security and legal aspects that are put in place in order to support and protect this shared responsibility between the RIPE NCC as the provider or the platform and the users.
5. Building a Smart House and You Want to Do It Yourself? [20 min]
Jan Žorž

Jan is building a house and since he wanted to build a smart one, he went through the process of testing and experimenting with different IOT devices communicating over different wireless protocols, as well as through hardware and software choices of open-source home automation software. Alongside the process of connecting all the dots, privacy concerns also arise and it's time to have a proper discussion about these issues.
6. Spinning CPEs: Collaborative Work on CPE IoT Protection [20 min]
Jelte Jansen, SIDN Labs and Peter Steinhaüser, Embedd

In this joint presentation, Peter and Jelte discuss their work on home network protection, including related standardisation work, SPIN in OpenWRT, and an interactive SPIN demo.
7. A Residential IoT Un-Quarantine Playbook (remote presentation) [20 min]
Michael Richardson, Sandelman Software Works

The increased use of automated IoT security mechanisms such as the Manufacturer Usage Description means that devices will increasingly be "taken offline" for possible violations of stated security policy. Detection of possible violations is just a first step. There are a number of additional steps necessary to return the device to correct operation. For residential IoT devices, the only clear organisation that the resident has a relationship with is the Internet (access) Service Provider (ISP). The ISP helpdesk will inevitably take the call and needs to pass the call off to a manufacturer or another entity, providing as much information as possible in an automated way. This presentation is about the process (the playbook) to be followed, and attempts to identify which steps of the protocol can be automated with existing and/or upcoming protocols, and where there are gaps that could be automated.
8. AOB