A Concise Binary Object Representation (CBOR)-based Serialization Format for the Software Updates for Internet of Things (SUIT) Manifest
draft-ietf-suit-manifest-16
| Document | Type | Expired Internet-Draft (suit WG) | |
|---|---|---|---|
| Authors | Brendan Moran , Hannes Tschofenig , Henk Birkholz , Koen Zandberg | ||
| Last updated | 2022-04-28 (Latest revision 2021-10-25) | ||
| Replaces | draft-moran-suit-manifest | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
bibtex
|
||
| 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 <david.waltermire@nist.gov> |
https://www.ietf.org/archive/id/draft-ietf-suit-manifest-16.txt
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 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.
Authors
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.)