I have the following MUD things: 1) draft-richardson-opsawg-mud-acceptable-urls-00 There was also a bunch of discussion about how to embed/reference/link to MUD files in SUIT manifests last week. I believe that there is a bigger mechanism here to discuss. Some of this could occur in the SUIT WG instead.
2) Operational Considerations for use of DNS in IoT devices
draft-richardson-opsawg-mud-iot-dns-considerations-01
3) Manufacturer Usuage Description for quarantined access to firmware
draft-richardson-shg-mud-quarantined-access-00
(M.Ranga has joined as an author, new document
---
I presented A standard process to quarantine and restore IoT Devices
draft-richardson-shg-un-quarantine-02
at RIPE79 last October. The idea was to make this a RIPE BCOP, but I think
that we need a lot more discussion here.
In the process of discussion, some CAPPORT connections have been proposed,
which probably don't belong in this document.
Discussion of many of these things has occured on and off on the mud@ and the
iot-onboarding@ lists. I shall find some time to recap them to this list.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
