May 2022 - iot-wg - mailman.ripe.net

the vague IoT/RIPE-NCC training question
by Michael Richardson 06 Jul '22

06 Jul '22

At RIPE84, recorded at https://ripe84.ripe.net/archives/video/782/ Jad El Cham asks about training from the RIPE NCC on "IoT". I watched this today from the archives. I wasn't able to be at the IOT-WG meeting in person (yes, you saw me there on Monday), because I was at the IoT Security Foundation's ManySecured WG meetings in London. Perhaps that makes me more qualified to answer the question? First, some nitpicks about this presentation. I couldn't hear Jad El Cham's name very well, and the lack of slides meant I had to watch the video three times to understand his question. https://ripe84.ripe.net/programme/meeting-plan/iot-wg/ has his name correctly, but: https://ripe84.ripe.net/archives/#wednesday does *NOT* If there were three slides with the questions and thoughts on them, then I could far better respond to the question. (Still not sure if the clapping for Marco leaving RIPE was ... "thanks for all the work", or "thank god you escaped with your sanity...) Second, while I share some of Jim's concern about scope creep, in fact there are many things that the RIPE NCC is uniquely positioned to help with that would benefit the community, and which probably *does* need a subsidy to get done correctly. Profit motives being forever next-quarter, 90% of the IoT security problems (as explained in the previous presentation, the slides at: https://ripe84.ripe.net/presentations/87-HVIKT-IoT-encounters-ripe.pdf include his missing slides...) are the result of next quarter thinking combined with very poor operational controls. If we are going to get a handle on the security issues with networks of devices (routers are the Internet of Internet things) then we need more data and more sharing of experiences. Back in RIPE79, (Rotterdam), I tried to start discussion about how ISPs can collaborate better on dealing with security issues, particularly DDoS caused by distributed malware. So, what would I like to see: 1) increase connection with RIPE NCC with organizations like iotsecurityfoundation.org. IoTSF is among the few places I've found which are not about hype or marketing, who seem to have real connections to both places/people technical and people/places regulatory. Like the IETF, though, we need more participation of operators.... not just the airy-fairy senior security architects from various ISPs, but actual people in the trenches. There are dozens of interesting bits of research being done via RIPE Atlas, telling more IoT types about the results would be a good thing. That could be in the form of some RIPE (NCC?) person talking about research, or perhaps for RIPE NCC sponsoring the researcher to present their stuff at a few conferences, such as the IoTSF conference in October, but also IETF meetings, RSA(*), Industrial Internet Consortium, The Thing Conference, ... btw: I did two training courses in 2020 for IoTSF on default passwords and software updates. *Manufacturers* are *really* hard to reach. Educating *operators* about what to *ask for*, and which regulation the supplier is not-complliant with when they fail, would also be very good. 2) RIPE NCC involvement with specifications like: https://datatracker.ietf.org/wg/mile/about/ ROLIE RFC 8322 good intro:https://www.redhat.com/en/blog/red-hat-adopts-rolie-protocol-automate… GOLIE https://github.com/rolieup/golie For instance, how many ISPs how how to set this up? I have no personal experience. Would I come to a day-long workshop (Saturday before or after RIPE?)... YES. This is training content that RIPE NCC could develop, and could provide in multiple venues for free or for low cost. This is much akin to MANRS, RPKI training, and I think there has been IX training occur as well. ROLIE is not loved by everyone, btw, and there are some alternatives which my slides from 79 went into, but actually I'm not, alas, qualified at this time to say much, because I know little myself. 3) RIPE (NCC) involvement with regulators on the topic of *privacy* and *liability* around vulnerability disclosures. Some operators, for instance, have told me that in order to avoid violating the privacy of their customers when it comes to detecting malware infestations on *their* networks, set up honeypots of (somewhat?) vulnerable devices and wait for them to get p0wned. That's an interesting training course on its own. 4) a RIPE reference secure CPE device...? I could probably go on for days here with things that could be done. Many medium-sized operators have decided they don't like what's available to them, and have went out to specify/build their own devices. Most bigger operators have been doing this for more than a decade, but my observation is that the bigger the operator, the less secure their default device is. (For instance, we know how many and how poorly some of these devices support IPv6) Is there an opportunity to collect wisdom together? Maybe some kind of symposium of operators and openwrt developers could happen. OpenWRT has had conferences, although often not that well advertised in advance. pprlFoundation sometimes has conferences I think. The WBAlliance does stuff, but alas, 90% of what I see is total marketing. 5) I could come with a fifth, but his email is already too long. :-) -- Michael Richardson <mcr+IETF(a)sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide

4 5

IoT conference in Delft - call for workshops
by Aaron Ding 19 May '22

19 May '22

Hi all, a kind reminder for the workshop proposals at 12th International Conference on IoT https://iot-conference.org/iot2022/call-for-workshops/ Proposals can be submitted to workshops-iot2022-IDE(a)tudelft.nl<mailto:workshops-iot2022-IDE@tudelft.nl> Important Dates * Workshop proposal submission deadline: May 25th, 2022 * Notification of workshop acceptance: Rolling, typically within three weeks but no later than June 30 * Workshop papers Submission deadlines: Camera ready date no later than October 17, 2022 * Workshop dates: TBD within November 7-10, 2022 Workshop Program Chairs: Aaron Ding & Kimberly Garcia Aaron -- Associate Professor, TU Delft Associate Editor for ACM Transactions on IoT <https://homepage.tudelft.nl/8e79t/>https://homepage.tudelft.nl/8e79t/

1 0

LoRa Alliance's LoRaWAN World Expo conference
by Jim Reid 19 May '22

19 May '22

In case anyone's interested in this event... > Begin forwarded message: > > From: Olivier Beaujard <obeaujard(a)semtech.com> > Subject: [T20ALL] LoRa Alliance's LoRaWAN World Expo conference in Paris > Date: 19 May 2022 at 09:04:00 BST > To: "t22sg20all(a)lists.itu.int" <t22sg20all(a)lists.itu.int> > Cc: "tsbsg20(a)itu.int" <tsbsg20(a)itu.int> > Reply-To: Olivier Beaujard <obeaujard(a)semtech.com> > > The LoRa Alliance is organizing a two ways conference in Paris on July 6-7: the LoRaWAN World Expo. > > There will be an impressive line-up of ~50 speakers from our entire Global Ecosystem who will come and present about the Power of LoRaWAN in the IoT: Miscrosoft, AWS, Eutelsat, Echostar, Cisco, Tata,… and many others. > > You can see the latest version of the agenda: https://bit.ly/38d6rgk > and the latest list of speakers here: https://bit.ly/3kUaEs4 > > You can register for this important IoT event via this link: > https://cvent.me/EzK049 > > and you are welcome to use the 10% discount code: LWE-SAVE10 (valid through May 31). > > Let me know if you do have any question. > > > > With best regards, > > Olivier Beaujard > Senior Director, LoRa Ecosystem > Semtech > LoRa Alliance Board Member & > Chairman of the Regulatory Work Group > +33 667 027 641 > obeaujard(a)semtech.com >

1 0

Re: [iot-wg] iot-wg Digest, Vol 59, Issue 4
by Phil Stanhope 17 May '22

17 May '22

I just wanted to add my support for Peter. It was a pleasure to work with Peter and other members of the working group on the IoT Architectural Considerations paper we released in April 2021. Peter helped keep us organized and focused during the drafting and review process. -phil On Sun, May 15, 2022 at 6:00 AM <iot-wg-request(a)ripe.net> wrote: > Send iot-wg mailing list submissions to > iot-wg(a)ripe.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ripe.net/mailman/listinfo/iot-wg > or, via email, send a message with subject or body 'help' to > iot-wg-request(a)ripe.net > > You can reach the person managing the list at > iot-wg-owner(a)ripe.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of iot-wg digest..." > > > Today's Topics: > > 1. [Peter Steinhaeuser] for co-chair (Peter Steinh?user) > 2. Re: [Peter Steinhaeuser] for co-chair (fwd) Michael > Richardson: Re: [Peter Steinhaeuser] for co-chair (Michael > Richardson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 14 May 2022 17:17:26 +0200 > From: Peter Steinh?user <ps(a)embedd.com> > To: IoT WG RIPE <iot-wg(a)ripe.net> > Subject: [iot-wg] [Peter Steinhaeuser] for co-chair > Message-ID: <6A271EB2-9384-477F-9237-632AA7FC4F8A(a)embedd.com> > Content-Type: text/plain; charset="us-ascii" > > Dear collegues, > > I put my hat (again) into the ring and ask you to support me as a candiate > for co-chairing this WG. > > I think that this WG is still trying to find it's place in the RIPE > community, the overall acitivity level has beend a bit low. Of course the > years of the pandemic and the lack of opportunities to meet in person were > not helpful. Nevertheless it seems that IoT is still something that is > often considered to live in the consumer space, and also many carriers > currently seem to have other priorities. > > With the expanding support of IP for IoT connectivity - i.e. the Thread > and Matter protcol - I think this WG can work more closely with the other > RIPE WGs and should working on linkinf with other RIPE WGs and > standardisation and industry entities to better understand what this RIPE > WG can contribute. > > There are already activities (IETF home gateway WG, Telcom Infra Project) > in this field and also carriers bit by bit seems to pay more attention to > IoT. Industrial IoT is also getting traction and new technologies like LiFi > are emerging. Such should also come this WG's attention and there's are > strong tendency to move toward IP (in my understanding). > > As a WG 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 & Telcom Infrastructure Project > - TIP) to get broader support for these activities as well. In my role as > project manager for prplOS in the prpl Foundation I also propose > technologies for adoption & funding by the prpl Foundation and it's > members, as well as in the TIP project where we contribute technology and > solutions to the Open Coverged Wireless WG (and recently started working on > IoT integration as well). > > I would appreaciate your support for my standing for co-chair for this WG > and supporting it's activities. I still think that this WG can make > meaningful contributions - we had a good start with the BCOP document and > it was a pleasure for me to work with the participating WG members. > > Sincerly, > Peter Steinhaeuser >

1 0

Re: [iot-wg] iot-wg Digest, Vol 59, Issue 6
by Phil Stanhope 17 May '22

17 May '22

I just wanted to add my support for Peter. It was a pleasure to work with Peter and other members of the working group on the IoT Architectural Considerations paper we released in April 2021. Peter helped keep us organized and focused during the drafting and review process. -phil On Tue, May 17, 2022 at 6:00 AM <iot-wg-request(a)ripe.net> wrote: > Send iot-wg mailing list submissions to > iot-wg(a)ripe.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ripe.net/mailman/listinfo/iot-wg > or, via email, send a message with subject or body 'help' to > iot-wg-request(a)ripe.net > > You can reach the person managing the list at > iot-wg-owner(a)ripe.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of iot-wg digest..." > > > Today's Topics: > > 1. Re: [Peter Steinhaeuser] for co-chair (T?ma Gavrichenkov) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 16 May 2022 20:01:19 +0200 > From: T?ma Gavrichenkov <ximaera(a)gmail.com> > To: Peter Steinh?user <ps(a)embedd.com> > Cc: IoT WG RIPE <iot-wg(a)ripe.net> > Subject: Re: [iot-wg] [Peter Steinhaeuser] for co-chair > Message-ID: > < > CALZ3u+aEXc5nLWGNcazAJAk15Zy6iDchj4c1YeTEMmNm6b+jJQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Peace, > > I, too, support Peter for the IoT WG Chair position. > > -- > T?ma > > On Sat, May 14, 2022, 5:17 PM Peter Steinh?user <ps(a)embedd.com> wrote: > > > Dear collegues, > > > > I put my hat (again) into the ring and ask you to support me as a > candiate > > for co-chairing this WG. > > > > I think that this WG is still trying to find it's place in the RIPE > > community, the overall acitivity level has beend a bit low. Of course the > > years of the pandemic and the lack of opportunities to meet in person > were > > not helpful. Nevertheless it seems that IoT is still something that is > > often considered to live in the consumer space, and also many carriers > > currently seem to have other priorities. > > > > With the expanding support of IP for IoT connectivity - i.e. the Thread > > and Matter protcol - I think this WG can work more closely with the other > > RIPE WGs and should working on linkinf with other RIPE WGs and > > standardisation and industry entities to better understand what this RIPE > > WG can contribute. > > > > There are already activities (IETF home gateway WG, Telcom Infra Project) > > in this field and also carriers bit by bit seems to pay more attention to > > IoT. Industrial IoT is also getting traction and new technologies like > LiFi > > are emerging. Such should also come this WG's attention and there's are > > strong tendency to move toward IP (in my understanding). > > > > As a WG 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 & Telcom Infrastructure > Project > > - TIP) to get broader support for these activities as well. In my role as > > project manager for prplOS in the prpl Foundation I also propose > > technologies for adoption & funding by the prpl Foundation and it's > > members, as well as in the TIP project where we contribute technology and > > solutions to the Open Coverged Wireless WG (and recently started working > on > > IoT integration as well). > > > > I would appreaciate your support for my standing for co-chair for this WG > > and supporting it's activities. I still think that this WG can make > > meaningful contributions - we had a good start with the BCOP document and > > it was a pleasure for me to work with the participating WG members. > > > > Sincerly, > > Peter Steinhaeuser_______________________________________________ > > iot-wg mailing list > > iot-wg(a)ripe.net > > https://lists.ripe.net/mailman/listinfo/iot-wg > > > > To unsubscribe from this mailing list, get a password reminder, or change > > your subscription options, please visit: > > https://lists.ripe.net/mailman/listinfo/iot-wg > > >

1 0

it's co-chair selection time!
by Jim Reid 16 May '22

16 May '22

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. 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. 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. 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). 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.

11 19

Re: [iot-wg] [Peter Steinhaeuser] for co-chair (fwd) Michael Richardson: Re: [Peter Steinhaeuser] for co-chair
by Michael Richardson 14 May '22

14 May '22

Peter Steinh=C3=A4user <ps(a)embedd.com> wrote: > I put my hat (again) into the ring and ask you to support me as a > candiate for co-chairing this WG. I am very supportive of Peter doing this! > I think that this WG is still trying to find it's place in the RIPE > community, the overall acitivity level has beend a bit low. Of course > the years of the pandemic and the lack of opportunities to meet in > person were not helpful. Nevertheless it seems that IoT is still > something that is often considered to live in the consumer space, and > also many carriers currently seem to have other priorities. I thik that these are astute observations. I really enjoyed the RIPE79 (Rotterdam) IoT hackathon. I think that there are interesting operational things that RIPE IoT WG could have deeper converations about. There will be a grandchild-of-HOMENET effo= rt at the IETF that might get called SNAC. It would be interesting to me to do some kind of *interop* testing of IoT systems and ISP systems. > As a WG 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= & > Telcom Infrastructure Project - TIP) to get broader support for these > activities as well. =20=20=20=20 > In my role as project manager for prplOS in the > prpl Foundation I also propose technologies for adoption & funding by > the prpl Foundation and it's members, as well as in the TIP project > where we contribute technology and solutions to the Open Coverged > Wireless WG (and recently started working on IoT integration as well). This kind of promotion of new open source systems and open-stand.org (standards) is really important to me as well. -- Michael Richardson <mcr+IETF(a)sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-

1 0

RIPE 84 IoT WG Agenda
by sandoche Balakrichenan 13 May '22

13 May '22

Dear all, As you all know, the IoT WG session @RIPE 84 will be on Wednesday 18th May9:00 - 10:00 (UTC+2). The agenda looks as follows: * Introduction & House Keeping (5 mins) * Leandro Lanzieri (Hamburg University of Applied Sciences) – "Secure and Authorized Client-to-Client Communication for LwM2M" - (15 mins) * Tommy Haga (Helse Vest IKT) - "IoT encounters in Health Care Networks" (25 mins) * Jad El Cham – "RIPE NCC IoT Update 2022" (10 min) * Co-Chair announcement & AOB (5 mins) Thanks and kind regards, Constanze& Sandoche.

1 0

Call for volunteers or nominations for RIPE IoT Working Group co-chair
by sandoche Balakrichenan 13 May '22

13 May '22

Dear Colleagues As Constanze's term as IoT WG co-chair is about to end with RIPE 84, this is a call for nominations or volunteers to co-chair the RIPE IoT working group. *********************************************************************** Please DO NOT reply to this message if you wish to propose a volunteer. *********************************************************************** I would ask for each candidate to start a new thread with, e.g., "[name] for co-chair", and for members to utter their support by replying to the respective thread. Provided there are no reasoned objections from the WG, I'd like to set *May 16th* as a deadline for showing support on the mailing list, so that we can announce the decision on *18th May* during the IoT WG sesssion at RIPE 84. More information about WG co-chair responsibilities (https://www.ripe.net/publications/docs/ripe-692). If you'd like further information, don't hesitate to contact me or Constanze. Have a nice day! Sandoche

4 8