- iot-wg - mailman.ripe.net

Call for Presentations [IoT WG session]
by sandoche Balakrichenan 12 Apr '22

12 Apr '22

Hi everyone! As you're probably already aware, RIPE 84 (https://ripe84.ripe.net/), we will be held from from May 16 to 20 in Berlin. It's an opportunity to meet you all after two years :-) The IoT WG session is scheduled on WEDNESDAY, 18th May, 9:00 to 10:00 CET If you have any presentation proposals, discussion topics, or something else that could be important and/or interesting for IoT enthusiasts and professionals in the RIPE community, please send a mail to <iot-wg-chairs@.ripe.net <http://ripe.net>>. We're looking forward to your ideas and proposals! :) Sandoche & Constanze --

1 0

Last call and final reminder for nominations to the 2022 Rob Blokzijl Award
by Carsten Schiefner 14 Mar '22

14 Mar '22

[Apologies for cross-posting to various RIPE lists] Dear IoT WG members - this is the last call and final reminder for nominations to the 2022 Rob Blokzijl Award that will be accepted until this Friday, 18th March, at 23:59 UTC. In seeking nominations for this prestigious award, which was created to celebrate Rob's contributions to the development of the Internet, the Award Committee (https://rob-blokzijl-foundation.org/2021/11/22/2022-award-committee/) is interested to receive nominations of those who have reflected Rob's approach in either a technical or operational capacity. Please give some consideration to nominating individuals - but also teams and groups of people! - in your own community and/or the wider industry in the RIPE region who, in your opinion, deserve to be recognised for their work to make the internet and/or internet community better. To specifically have this emphasised again after some according queries: nominations of teams and groups of people are very well possible and wished for as well in case their collective work would match the criteria of the call as laid out! The Award Committee is particularly interested to receive nominations of contributors who, in addition to their own contributions, have also supported and enabled others anywhere in the world. Also, the Award Committee would like to encourage those making nominations to consider not only the community members in the later stages of their careers or who are widely known but also those who may have contributed greatly in the springtime of their career or discreetly for the greater good or who may be considered to be part of an unrepresented group. And last but not least: those of you who previously have made a nomination other than Wilfried Woeber, the 2018 awardee, may want to consider resubmitting a nomination. The complete details of the call and the nomination process can be found at: https://rob-blokzijl-foundation.org/2021/11/25/call-for-nominations-2022/ Best wishes and kind regards Carsten (on behalf of the Award Committee)

1 0

what I'd want from DNS4EU
by Michael Richardson 01 Feb '22

01 Feb '22

I attended this "morning" (for me)'s discussion about DNS4EU. I don't know much about what the EC is put out in it's RFP as I don't live in the EU (..yet?) and aren't in a position to respond to it. Right now, people know about 8.8.8.8. They spray painted it on walls in Turkey a few years ago! Amateur network administrators, aka local teens, know that if someone is having problems with their device, that sticking 8.8.8.8 in sometimes helps. Many ISPs and many "pro-sumers" who configure their own home gateways will stick 8.8.8.8 in as a DNS server. I run my own recursive resolvers, but, on my desktop I have: nameserver 2607:f0b0:f::babe:f00d nameserver 209.87.249.18 nameserver 8.8.8.8 search sandelman.ca (The first two point to the same machine) Why? because sometimes shit happens, and that local VM is broken, and it's easier to use DNS to fix DNS. Yeah, I have breadcrumbs in my /etc/hosts too. So what I would like DNS4EU to do is to create a European hosted and operated alternative. It doesn't have to be run by a single entity. In fact, I think that this is a bad idea. But, it does have to have the same kind of "name" recognition as 8.8.8.8 (%) That might mean, literally, spray painting it on walls. Berlin people could hire 1UP crew maybe. It seems clear that this new resolver address will need to have multiple servers and and be anycasted. It could be run by a multitude of operators, with at least one per country. That solves the entire digital sovereignty issue, and the "local" denylist. a) This is where RIPE NCC starts to come in: find and allocate some memorable IPv4/24, and IPv6/48 for this. Let's call this R.R.R.R b) In order to run DoT, DoH, we need TLS certificates. If the system is anycast, and is run by a multitude of entities, then we need to be able to deploy certificates to a multitude of entities and each need to manage their own private keys. "dns.google" works because Google is a CA. (I didn't know that was the FQDN for it until I visited it just now) This is the second activity which RIPE NCC should be involved it: coordinating the certificates for the entities. How exactly to do this, technically, is an open question to me. There are many possible arrangements, including some new ones like RFC9060. c) The variety of entities running these servers need consistent and regular training. There is a further interesting thing to me, and that involves the IoT situations with DoT/DoH. There are three issues. 1) IoT devices that ignore the local resolver settings and try to use 8.8.8.8. This upsets many people (Vixie is loudest), because many of us have concerns about what the devices are doing. DoH makes it near impossible to observe. I have an IETF OPSAWG draft about DNS and MUD. There are privacy issues with the devices crossing national jurisdictions with their queries. I suspect GDPR ones, but I'm no lawyer. 2) Many would like to use DNS queries as canaries for malware on IoT devices. 3) Many would like to prevent IoT devices from being able to reach certain known malware sites. Recognize that when we allocate R.R.R.R, we get all of R.R.R.0/24 at least, and we could run a number of diffentiated services at R.R.R.I, etc. If R.R.R.I was promoted as a GDPR-safe place for IoT devices to send queries to, and if the canaries could be coordinated, then that would likely be a win for the security of the Internet. (Of course, making IoT devices pay attention to RDNSS and DHCP values would be my priority. But, return R.R.R.I to those IoT devices would make sense) (%) I know that 8.8.4.4 is also a google resolver, but I rarely use it. 1.1.1.1 is easier to remember. I can't remember the IPv6 for any of them offhand. Yet, I know sprint.net is http://[2600::] for instance. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | IoT architect [ ] mcr(a)sandelman.ca http://www.sandelman.ca/ | ruby on rails [ -- Michael Richardson <mcr+IETF(a)sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide

1 0

Happy New Year - 2022
by sandoche Balakrichenan 07 Jan '22

07 Jan '22

Dear all, Wish you all a Happy & Prosperous New year with good health and lots of success in your endeavors. We will have fruitful discussions in 2022 and importantly applying our work for the benefit of the Community. -- Sandoche BALAKRICHENAN As RIPE IoT WG Co-Chair

1 0

Draft RIPE 83 minutes
by sandoche Balakrichenan 10 Dec '21

10 Dec '21

Dear all, Here is the RIPE 83 draft minutes: https://www.ripe.net/participate/ripe/wg/active-wg/iot/minutes/draft-iot-wo… If there are any errors or omissions, please let us know on the list. -- Sandoche BALAKRICHENAN & Constanze Dietrich as RIPE IoT WG Co-Chairs

1 0

RIPE 83 IoT WG Agenda
by sandoche Balakrichenan 18 Nov '21

18 Nov '21

Dear all, As you all know, the IoT WG virtual session @RIPE 83 will be on Tuesday 23 November 14:30 - 15:30 (UTC+1) The agenda for the IoT WG session looks as follows: * Introduction (5 min) * Elsa Turcios Rodriguez – User compliance and remediation success after IoT malware notifications (30 min) * Marco Hogewoning – RIPE NCC IoT Update 2021 (20 min) * AOB (5 min) On Tuesday 23rd, we will also be online after 19:00 (UTC + 1) on the spacial chat lounge, for any further discussions. Thanks and kind regards Constanze& Sandoche.

1 0

ACM SIGCOMM HotNets'21 registration open
by Aaron Ding 14 Oct '21

14 Oct '21

ACM SIGCOMM HotNets'21 registration is open now, featuring an exciting programme: https://conferences.sigcomm.org/hotnets/2021/program.html Student registration is free, $5 for ACM members and $15 for non-members. Through the generosity of our sponsors we have scope to assist those who need financial aide to participate in HotNets'21. Please convey your case to the general chairs: hotnets21gcs(a)sigcomm.org Registration info: https://conferences.sigcomm.org/hotnets/2021/register.html Aaron

1 0

RIPE 83: Call for Presentations [IoT WG session]
by Constanze Dietrich 13 Oct '21

13 Oct '21

Hi everyone! As you're probably already aware, RIPE 83 is ahead of us from November 22 to 26 as another virtual meeting. This is the IoT WG's call for presentations! :) For the first time, the IoT WG session is scheduled on TUESDAY, November 23, 14:30 to 15:30 CET (13:30 - 14:30 UTC)! If you have any presentation proposals, discussion topics, or something else that could be important and/or interesting for IoT enthusiasts and professionals in the RIPE community, please send a mail to <iot-wg-chairs@. ripe.net>. We're looking forward to your ideas and proposals! :) Constanze & Sandoche

1 0

RIOT Summit 2021: Call for Participation
by Matthias Waehlisch 30 Aug '21

30 Aug '21

**What:** 6th RIOT Summit, the yearly get-together of the friendly Operating System for the Internet of Things, https://summit.riot-os.org/2021/ **Where:** virtually (online) **When:** September 9-10, 2021 **Registration:** Participation is free but registration is required via https://riot-summit2021.eventbrite.de/ **Keynote:** Henning Schulzrinne (Columbia University) will talk about "How do we program the Internet of Things at scale?" **Talks:** include topics about Network Security * Frank Hessel (TU Darmstadt), "ChirpOTLE: Using RIOT to Evaluate the Security of LoRaWAN" * Christian Amsüss, "Pieces to Picture: Security components of the CoRE ecosystem" * Jan Romann (University of Bremen), "Secure Network Access for IoT Devices: MUD & Co" System Security * Jürgen Fitschen (SSV Software Systems GmbH), "Secure Update of IoT Devices over Low Data Rate Wireless Networks" * Lena Boeckmann (HAW Hamburg), "Integration of a cryptographic API with configurable hardware and software backends in RIOT" * Joost Renes (NXP), "Post-Quantum Crypto: The Embedded Challenge" Debugging, Applications, and Networking * Richard Copeman (Lauterbach GmbH), "Efficient Debugging with RIOT Awareness in TRACE32" * Tobias Buchberger and Ines Kramer (Competence Centre for IT-Security, FH Campus Wien), "CoMatrix - How to overcome kernel panic, deal with buffer limitations and LOL at random" * Benjamin Valentin (ML!PA Consulting GmbH), "Wired sensor networks and IPv6 subnet auto-configuration" Training and Rapid Prototyping with RIOT * Ioannis Chatzigiannakis (Sapienza University of Rome), "Teaching IoT with RIOT" * Michael Richardson and Yoichi J. Nakaguro, "Building and Integrating Rust libraries for RIOT-OS,with Micropython support" Full program: https://summit.riot-os.org/#schedule thanks matthias -- Matthias Waehlisch . Freie Universitaet Berlin, Computer Science .. http://www.cs.fu-berlin.de/~waehl

1 0

[IoT2021] Call for Poster/Demos (Deadline August 23, 2021)
by Konrad Diwold 16 Aug '21

16 Aug '21

================================================================= Call for Posters and Demos (Deadline, Tuesday, August 23 August 31st, 2021, 23:59 AoE) 11th International Conference on the Internet of Things (IoT 2021) https://iot-conference.org St Gallen, Switzerland (and virtually). ACM (SIGCHI) In-Cooperation event ================================================================= The objective of the Posters and Demo sessions at IoT 2021 is to give researchers in the emerging research areas of IoT and their applications the opportunity to present early and fresh, in-progress results, to share experiences and strategies while facilitating the discussion between authors and conference attendees. We are especially interested in contributions of exciting demonstrations of novel approaches, designs, and implementations of IoT technology, both on an application as well as a hardware level. We would like to invite both researchers and practitioners from academia and industry to share and demonstrate their approaches. We explicitly welcome submissions from industry that outline and demonstrate new scientific opportunities and challenges for the application of IoT. Posters presenting early work and preliminary results are solicited. Demos can include but are not limited to, showcasing of research prototypes and proofs of concept, tool tutorials, or demonstrations of commercial or in-house applications. *Preparing Your Demo Submission* Researchers interested in submitting a demo should submit a 2 to 4 pages abstract (including references) formatted in the most recent ACM SIGCHI Extended Abstracts Format as PDF file. This extended abstract should include a figure of the system that shall be demonstrated during IoT 2021. Please mark the title of your contribution with the prefix “Demo:”. Information on the implementation of the demo session will be given after the review process. *Preparing Your Poster Submission* Researchers interested in submitting a poster should submit a 2 to 4 pages abstract (including references) formatted in the most recent ACM SIGCHI Extended Abstracts Format as PDF file. Please mark the title of your contribution with the prefix “Poster:”. Authors of accepted abstracts will be required to prepare a virtual poster for presentation at the conference in a standard format, details will be provided after the review process. *Submitting Your Poster and Demo Submission* Abstracts should be submitted via the EasyChair conference system ( https://easychair.org/conferences/?conf=iot20210), must be written in English, and contain original material that has not been published or is currently undergoing review elsewhere. Abstracts will be peer-reviewed by two experts of the scientific committee following a single-blind review process (i.e., the identity of the reviewer is anonymous, but the author’s name and affiliation are on the paper). Accepted abstracts will be listed on DBLP and published via the ACM Digital Library. Cases of plagiarism or multiple submissions will be subject to disciplinary action as per ACM rules and regulations, and no-shows at the conference will result in exclusion from the ACM Digital Library. Your submission should be close to camera-ready and thoroughly copy-edited due to the short selection cycle. *Important Dates* - Submission: August 23, 2021 (23:59 AoE) - Acceptance Notification: October 4, 2021 (23:59 AoE) - Camera-ready Version: October 18, 2021 (23:59 AoE) Track Chairs Konrad Diwold, Pro2Future GmbH & Graz University of Technology, e-mail: konrad.diwold(a)pro2future.at Pascal Weisenburger, University of St. Gallen, e-mail: pascal.weisenburger(a)unisg.ch

1 0