An Information Model for Firmware Updates in IoT Devices
draft-ietf-suit-information-model-05

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05

SUIT                                                            B. Moran
Internet-Draft                                             H. Tschofenig
Intended status: Standards Track                             Arm Limited
Expires: July 23, 2020                                       H. Birkholz
                                                          Fraunhofer SIT
                                                        January 20, 2020

        An Information Model for Firmware Updates in IoT Devices
                  draft-ietf-suit-information-model-05

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.  Ensuring that devices function and
   remain secure over their service life requires such an update
   mechanism to fix vulnerabilities, to update configuration settings,
   as well as adding new functionality

   One component of such a firmware update is a concise and machine-
   processable meta-data document, or manifest, that describes the
   firmware image(s) and offers appropriate protection.  This document
   describes 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 23, 2020.

Copyright Notice

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

Moran, et al.             Expires July 23, 2020                 [Page 1]
Internet-Draft    A Firmware Manifest Information Model     January 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.

   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 . . . . . . . . . . . . . . . . .   6
     2.1.  Requirements Notation . . . . . . . . . . . . . . . . . .   6
   3.  Manifest Information Elements . . . . . . . . . . . . . . . .   6
     3.1.  Manifest Element: Version ID of the manifest structure  .   6
     3.2.  Manifest Element: Monotonic Sequence Number . . . . . . .   6
     3.3.  Manifest Element: Vendor ID . . . . . . . . . . . . . . .   7
       3.3.1.  Example: Domain Name-based UUIDs  . . . . . . . . . .   7
     3.4.  Manifest Element: Class ID  . . . . . . . . . . . . . . .   7
       3.4.1.  Example 1: Different Classes  . . . . . . . . . . . .   8
       3.4.2.  Example 2: Upgrading Class ID . . . . . . . . . . . .   9
       3.4.3.  Example 3: Shared Functionality . . . . . . . . . . .   9
       3.4.4.  Example 4: White-labelling  . . . . . . . . . . . . .   9
     3.5.  Manifest Element: Precursor Image Digest Condition  . . .  10
     3.6.  Manifest Element: Required Image Version List . . . . . .  10
     3.7.  Manifest Element: Expiration Time . . . . . . . . . . . .  10
     3.8.  Manifest Element: Payload Format  . . . . . . . . . . . .  11
     3.9.  Manifest Element: Processing Steps  . . . . . . . . . . .  11
     3.10. Manifest Element: Storage Location  . . . . . . . . . . .  11
       3.10.1.  Example 1: Two Storage Locations . . . . . . . . . .  12