A Firmware Update Architecture for Internet of Things Devices
draft-moran-suit-architecture-03
| Document | Type | Replaced Internet-Draft (suit WG) | |
|---|---|---|---|
| Last updated | 2018-03-23 (latest revision 2018-03-05) | ||
| Replaces | draft-moran-fud-architecture | ||
| Replaced by | draft-ietf-suit-architecture, draft-ietf-suit-information-model | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-suit-architecture, draft-ietf-suit-information-model | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-moran-suit-architecture-03.txt
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.
Authors
Brendan Moran
(brendan.moran@arm.com)
Milosch Meriac
(milosch.meriac@arm.com)
Hannes Tschofenig
(Hannes.Tschofenig@gmx.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)