I’m not quite certain how it would work. Can you show a flow that will work for an IoT device (e.g., headless and no display)?
Eliot > On 9 Jul 2019, at 16:41, Michael Richardson <[email protected]> wrote: > > Signed PGP part > > Between editing drafts yesterday, I got to thinking about CAPPORT. > I have been working on what to do when an IoT device violates it's MUD > profile. There are a bunch of issues around this. > > Yesterday, it occured to me that when such a device is quarantined > (I really think it should be "quaranteed", but that's not a word) > that the capport controls and APIs should be available to the device to > learn what went on. > > This is not new, I think that this as been the approach of most enterprise > NEA systems upon encountering "infection". This has, I assume, involved > forced HTTP proxies to inform human. But, if we have APIs, we can inform > device as well. > > Is this on anyone's radar? > > -- > Michael Richardson <[email protected]>, Sandelman Software Works > -= IPv6 IoT consulting =- > > > > >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
