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

Document Type Active Internet-Draft (suit WG)
Authors Brendan Moran  , Hannes Tschofenig  , Henk Birkholz  , Koen Zandberg 
Last updated 2020-11-02
Replaces draft-moran-suit-manifest
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd David Waltermire
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to David Waltermire <david.waltermire@nist.gov>
SUIT                                                            B. Moran
Internet-Draft                                             H. Tschofenig
Intended status: Standards Track                             Arm Limited
Expires: May 6, 2021                                         H. Birkholz
                                                          Fraunhofer SIT
                                                             K. Zandberg
                                                                   Inria
                                                       November 02, 2020

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

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 6, 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Moran, et al.              Expires May 6, 2021                  [Page 1]
Internet-Draft          CBOR-based SUIT Manifest           November 2020

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   6
   3.  How to use this Document  . . . . . . . . . . . . . . . . . .   8
   4.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  IoT Firmware Update Constraints . . . . . . . . . . . . .   9
     4.2.  SUIT Workflow Model . . . . . . . . . . . . . . . . . . .  10
   5.  Metadata Structure Overview . . . . . . . . . . . . . . . . .  11
     5.1.  Envelope  . . . . . . . . . . . . . . . . . . . . . . . .  12
     5.2.  Delegation Chains . . . . . . . . . . . . . . . . . . . .  13
     5.3.  Authentication Block  . . . . . . . . . . . . . . . . . .  13
     5.4.  Manifest  . . . . . . . . . . . . . . . . . . . . . . . .  13
       5.4.1.  Critical Metadata . . . . . . . . . . . . . . . . . .  14
       5.4.2.  Common  . . . . . . . . . . . . . . . . . . . . . . .  14
       5.4.3.  Command Sequences . . . . . . . . . . . . . . . . . .  14
       5.4.4.  Integrity Check Values  . . . . . . . . . . . . . . .  15
       5.4.5.  Human-Readable Text . . . . . . . . . . . . . . . . .  15
     5.5.  Severable Elements  . . . . . . . . . . . . . . . . . . .  15
     5.6.  Integrated Dependencies and Payloads  . . . . . . . . . .  16
   6.  Manifest Processor Behavior . . . . . . . . . . . . . . . . .  16
     6.1.  Manifest Processor Setup  . . . . . . . . . . . . . . . .  16
     6.2.  Required Checks . . . . . . . . . . . . . . . . . . . . .  17
       6.2.1.  Minimizing Signature Verifications  . . . . . . . . .  19
     6.3.  Interpreter Fundamental Properties  . . . . . . . . . . .  19
     6.4.  Abstract Machine Description  . . . . . . . . . . . . . .  20
     6.5.  Special Cases of Component Index and Dependency Index . .  22
     6.6.  Serialized Processing Interpreter . . . . . . . . . . . .  24
     6.7.  Parallel Processing Interpreter . . . . . . . . . . . . .  24
     6.8.  Processing Dependencies . . . . . . . . . . . . . . . . .  25
     6.9.  Multiple Manifest Processors  . . . . . . . . . . . . . .  25
   7.  Creating Manifests  . . . . . . . . . . . . . . . . . . . . .  27
Show full document text