Firmware Updates for Internet of Things Devices - An Information Model for Manifests
draft-ietf-suit-information-model-02
SUIT B. Moran
Internet-Draft H. Tschofenig
Intended status: Standards Track Arm Limited
Expires: July 22, 2019 H. Birkholz
Fraunhofer SIT
January 18, 2019
Firmware Updates for Internet of Things Devices - An Information Model
for Manifests
draft-ietf-suit-information-model-02
Abstract
Vulnerabilities with Internet of Things (IoT) devices have raised the
need for a solid and secure firmware update mechanism that is also
suitable for constrained devices. Incorporating such update
mechanism to fix vulnerabilities, to update configuration settings as
well as adding new functionality is recommended by security experts.
One component of such a firmware update is the meta-data, or
manifest, that describes the firmware image(s) and offers appropriate
protection. This document describes all the information that must be
present in the manifest.
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 July 22, 2019.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Moran, et al. Expires July 22, 2019 [Page 1]
Internet-Draft A Firmware Manifest Information Model January 2019
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.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 5
3. Manifest Information Elements . . . . . . . . . . . . . . . . 5
3.1. Manifest Element: version identifier of the manifest
structure . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Manifest Element: Monotonic Sequence Number . . . . . . . 6
3.3. Manifest Element: Vendor ID Condition . . . . . . . . . . 6
3.3.1. Example: Domain Name-based UUIDs . . . . . . . . . . 6
3.4. Manifest Element: Class ID Condition . . . . . . . . . . 6
3.4.1. Example 1: Different Classes . . . . . . . . . . . . 7
3.4.2. Example 2: Upgrading Class ID . . . . . . . . . . . . 7
3.4.3. Example 3: Shared Functionality . . . . . . . . . . . 8
3.5. Manifest Element: Precursor Image Digest Condition . . . 8
3.6. Manifest Element: Required Image Version List . . . . . . 8
3.7. Manifest Element: Best-Before timestamp condition . . . . 9
3.8. Manifest Element: Payload Format . . . . . . . . . . . . 9
3.9. Manifest Element: Processing Steps . . . . . . . . . . . 9
3.10. Manifest Element: Storage Location . . . . . . . . . . . 9
3.10.1. Example 1: Two Storage Locations . . . . . . . . . . 10
3.10.2. Example 2: File System . . . . . . . . . . . . . . . 10
3.10.3. Example 3: Flash Memory . . . . . . . . . . . . . . 10
Show full document text