%% You should probably cite draft-ietf-suit-manifest-31 instead of this revision. @techreport{ietf-suit-manifest-28, number = {draft-ietf-suit-manifest-28}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-suit-manifest/28/}, author = {Brendan Moran and Hannes Tschofenig and Henk Birkholz and Koen Zandberg and Øyvind Rønningstad}, title = {{A Concise Binary Object Representation (CBOR)-based Serialization Format for the Software Updates for Internet of Things (SUIT) Manifest}}, pagetotal = 102, year = , month = , day = , abstract = {This specification describes the format of a manifest. A manifest is a bundle of metadata about code/data obtained by a recipient (chiefly the firmware for an IoT device), where to find the code/data, the devices to which it applies, and cryptographic information protecting the manifest. Software updates and Trusted Invocation both tend to use sequences of common operations, so the manifest encodes those sequences of operations, rather than declaring the metadata.}, }