[Rats] Re: Hint Discussion in CSR Attestation Draft

[Michael Richardson <[e-mail]>]

Henk Birkholz <[e-mail]> wrote:
    > so a MUD file cannot point to feasible Verifiers?

It's not that you can't put a pointer like this into a MUD file.
The issue is that there is no context for CSR Attestation in which a MUD URL
will be retrieved.  Sure, the hint present in the CSR EvidenceStatement could
be a MUD URL, but that seems like a useless layer of indirection to me.

And it probably could make sense for some environments where MUD is already
used, such as with draft-itef-suit-mud!   I feel that we are lacking a few
pieces on the IETF "standard" MUD/SUIT/RATS ecosystem:

1) a standard SUIT Status Tracker
2) that also can distribute (multicast if practical) firmware updates to
   devices
3) that can collect RATS Evidence when it retrieves the SUIT Report
4) that can collect firmware from $vendor into a local repo, reducing the
   bandwidth, privacy and MUD impact of devices fetching their own firmware.

I hope the SUIT documents will finish the various review stages they are in,
and SUIT can consider rechartering to deal with these things.  I think that
RATS and SUIT were well chartered to interact with existing environments, to
embrace them, and now it is time to extend.


--
Michael Richardson <[e-mail]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide