This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/iot-wg@ripe.net/
[iot-wg] Bad actors
- Previous message (by thread): [iot-wg] Bad actors
- Next message (by thread): [iot-wg] Bad actors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Wed Oct 10 14:12:42 CEST 2018
> On 10 Oct 2018, at 13:02, Peter Steinhäuser <ps at embedd.com> wrote: > > I don’t think it’s RIPE’s and this working group’s purpose to get into the name & shame game. In my opinion we should define technical solutions that can be applied to address the security issues introduced by insecure devices. This is a wonderful idea Peter! Consider yourself volunteered! :-) Would you like to help develop this suggestion, for instance by proposing how the WG could define these solutions? Maybe you could put together an outline for a BCP or something like that. It would be great if the WG could produce a RIPE document on this topic.
- Previous message (by thread): [iot-wg] Bad actors
- Next message (by thread): [iot-wg] Bad actors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]