Subject: [Suit] Separate manifest for the status tracker

From: Rønningstad, Øyvind <[email-masked]>
Date: Mon, 29 Nov 2021 13:12:07 +0000

There has been some talk about status trackers decoding manifests. How about creating separate manifests especially for the status tracker (servers) and firmware servers? This would also potentially solve the problem of signed recipient lists (the entire list can be signed in the status tracker manifest). We could potentially define directives especially for these purposes, such as directive-push ("opposite" of fetch), directive-notify (notify a device of a new update), directive-publish (make a payload available at a URI). This would for example allow creating a manifest which instructs the status tracker (or firmware server) to
1.       Fetch all the relevant payloads.
2.       Push subsets of the payloads to different devices on the network. If directive-push takes a list of payloads, it would allow the status tracker to construct a manifest with these payloads as integrated payloads.
This would save bandwidth compared to having to download a separate package (envelope) for each device.

Is this something that has been considered or discussed?
Thoughts?

Øyvind