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] "The Internet of Threats: Fighting FUD with MUD"
- Previous message (by thread): [iot-wg] "The Internet of Threats: Fighting FUD with MUD"
- Next message (by thread): [iot-wg] IoT traffic and implicit consent
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Oct 23 16:20:03 CEST 2018
> On 22 Oct 2018, at 22:29, Michael Richardson <mcr at sandelman.ca> wrote: > >> Indeed. However at least MUD files should (in principle anyway) give >> people an idea of what their latest IoT toy will do once it’s plugged >> in. Though just saying it phones home to google/Amazon/Facebook every >> so often isn’t much help if you don’t know what it's sending and >> receiving. Or why it’s doing that. > > I disagree.... please don't over-extend what this is designed to do! > > MUD files will not, even in principal, tell people what the device will do! > It simply say, "will phone home to XYZ on port Q" (for various ways of > expressing XYZ). Michael, I think we are in violent agreement. MUD files are a step in the right direction. They will tell people that their IoT things are phoning home and what sorts of traffic is being generated. This is to be strongly encouraged. It would be even better if we knew what data were carried in that IoT traffic (and why). Though that’s not something which MUD offers - at least not yet.
- Previous message (by thread): [iot-wg] "The Internet of Threats: Fighting FUD with MUD"
- Next message (by thread): [iot-wg] IoT traffic and implicit consent
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]