Re: [Mud] how to increase trust in MUD URL

[Henk Birkholz <[e-mail]>]

Hi mud'ler,

On 22.01.20 02:03, Michael Richardson wrote:
> But, updating the URL in IDevID is difficult to do. Quite reasonably it might
> be impossible without a device recall.  The IDevID version is much easier to
> invest trust into.  And it clearly links back to the manufacturer.

This is one of the biggest issues that came to my mind ad-hoc. Is 
changing the URI really an option? I would assume this type of 
encapsulation is trustworthy, I think.

On 22.01.20 02:03, Michael Richardson wrote:
> If a vendor is going to put very specific information relating to TLS
> libraries into a MUD file, then it is going to be critical that any updates
> to the firmware (such as BUG FIXES) result in updates to the MUD TLS profile.

Hm. I always assumed that either a MUD file or the parameters to a MUD 
URI would take care of "versions" or "composition" of the requester (so 
the requester appends information about that in the URI). Is that not 
how other people think about it? The idea of a canonical composition of 
the segments in the URI did not fly IIRC (due to rfc7320 I assume).

Viele Grüße,

Henk