A Firmware Update Architecture for Internet of Things Devices
draft-ietf-suit-architecture-00
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (suit WG)
|
|
Authors |
|
Brendan Moran
,
Milosch Meriac
,
Hannes Tschofenig
|
|
Last updated |
|
2018-06-03
|
|
Stream |
|
Internent Engineering Task Force (IETF)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
WG Document
(wg milestone:
Nov 2019 - Submit architecture ...
)
|
|
On Agenda |
|
suit at IETF-110
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
SUIT B. Moran
Internet-Draft Arm Limited
Intended status: Informational M. Meriac
Expires: December 5, 2018 Consultant
H. Tschofenig
Arm Limited
June 03, 2018
A Firmware Update Architecture for Internet of Things Devices
draft-ietf-suit-architecture-00
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.
This document lists requirements and describes an architecture for a
firmware update mechanism suitable for IoT devices. The architecture
is agnostic to the transport of the firmware images and associated
meta-data.
This version of the document assumes asymmetric cryptography and a
public key infrastructure. Future versions may also describe a
symmetric key approach for very constrained devices.
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 http://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 December 5, 2018.
Moran, et al. Expires December 5, 2018 [Page 1]
Internet-Draft IoT Firmware Update Architecture June 2018
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Agnostic to how firmware images are distributed . . . . . 5
3.2. Friendly to broadcast delivery . . . . . . . . . . . . . 5
3.3. Use state-of-the-art security mechanisms . . . . . . . . 5
3.4. Rollback attacks must be prevented . . . . . . . . . . . 6
3.5. High reliability . . . . . . . . . . . . . . . . . . . . 6
3.6. Operate with a small bootloader . . . . . . . . . . . . . 6
3.7. Small Parsers . . . . . . . . . . . . . . . . . . . . . . 7
3.8. Minimal impact on existing firmware formats . . . . . . . 7
3.9. Robust permissions . . . . . . . . . . . . . . . . . . . 7
3.10. Operating modes . . . . . . . . . . . . . . . . . . . . . 8
4. Claims . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 10
6. Manifest . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7. Example Flow . . . . . . . . . . . . . . . . . . . . . . . . 13
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
Show full document text