Skip to main content

A Concise Binary Object Representation (CBOR)-based Serialization Format for the Software Updates for Internet of Things (SUIT) Manifest

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
Authors Brendan Moran , Hannes Tschofenig , Henk Birkholz , Koen Zandberg
Last updated 2022-04-28 (Latest revision 2021-10-25)
Replaces draft-moran-suit-manifest
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd David Waltermire
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to David Waltermire <>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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 that 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.


Brendan Moran
Hannes Tschofenig
Henk Birkholz
Koen Zandberg

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)