Re: [saag] SUIT will meet in the slot after SAAG

[Russ Housley <[e-mail]>]

SUIT

The SUIT Architecture (draft-ietf-suit-architecture) is with the RFC Editor.

SUIT Information Model (draft-ietf-suit-information-model).  During IESG Evaluation, three issues were raised that need highlighted.  First, UUID is used because it is fixed length, which makes decice handling very straightforward.  In addition, other fields provide human-readable text where that is appropriate.  Second, more details about delegation from one signer to another needs to be added to the document, but not the full details that are in the SUIT Manifest document.  Third, requirements for secure time source for experation of manifest need more explanation.
 
SUIT Manifest Format (draft-ietf-suit-manifest). The TEEP WG requested the ability to delete a component, which can lead to dependency problems. A garbage collection mechanism to remove unreferenced components will be provided instead.End up with broken system easily. Two approaches to encryption of firmware were discussed: one that uses a key-encryption key to distribute the content-encryption key, and another that uses ECDH Ephemeral-Static to establish the key-encryption key.  From the discussion is is fairly clear that algorithm profiles for SUIT Manifests will be needed.  To get the base protocol specification done, these profiles and examples will be put in other documents.

Other presentations were on the agenda, but the group ran out of time, so an virtual interim will be scheduled in a few weeks.