Skip to main content

A Firmware Update Architecture for Internet of Things Devices

Document Type Replaced Internet-Draft (suit WG)
Expired & archived
Authors Brendan Moran , Milosch Meriac , Hannes Tschofenig
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
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-suit-architecture, draft-ietf-suit-information-model
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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.


Brendan Moran
Milosch Meriac
Hannes Tschofenig

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)