[iot-wg] To be published: Architectural Considerations for IoT Device Security in the Home

JORDI PALET MARTINEZ via iot-wg <iot-wg at ripe.net> wrote:
    > I’m not sure if this should be considered in this document or other
    > future ones, or other foras.

    > Should IoT devices be allowed to send information to the cloud “always”
    > or the user must have the choice to disable that? I’ve seen many
    > devices, even CPEs, using OpenWRT or a derivative firmware, sending
    > stuff to the manufacturer, “hijacking DNS”, etc. This may be even a
    > regulatory issue.

No, this document is not really about that.
It's above our pay grade.

This document is about getting a handle on how any control would work,
rather than if, or under what regulation.

    > One last point. I think it will be very useful to have page numbers in
    > this (and every) document … also in other BCOP documents, we added an
    > annex with terminology.

point.

--
Michael Richardson <mcr+IETF at sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: </ripe/mail/archives/iot-wg/attachments/20210212/48c8a854/attachment.sig>