RFC 9019: A Firmware Update Architecture for Internet of Things
In plain English — editorial summary, not part of the RFC
Vulnerabilities in Internet of Things (IoT) devices have raised the need for a reliable and secure firmware update mechanism suitable for devices with resource constraints. Incorporating such an update mechanism is a fundamental requirement for fixing vulnerabilities, but it also enables other important capabilities such as updating configuration settings and adding new functionality. In addition to the definition of terminology and an architecture, this document provides the motivation for the standardization of a manifest format as a transport-agnostic means for describing and protecting firmware updates.
Document record
- Document ID
- RFC9019
- Published
- April 2021
- Authors
- B. Moran; H. Tschofenig; D. Brown; M. Meriac
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7815Minimal Internet Key Exchange Version 2 (IKEv2) Initiator ImplementationCurrent
March 2016
- RFC 7548Management of Networks with Constrained Devices: Use CasesCurrent
May 2015
- RFC 7547Management of Networks with Constrained Devices: Problem Statement and RequirementsCurrent
May 2015
- RFC 9202Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE)Updated
August 2022
- RFC 9237An Authorization Information Format (AIF) for Authentication and Authorization for Constrained Environments (ACE)Current
August 2022
- RFC 8628OAuth 2.0 Device Authorization GrantCurrent
August 2019
- RFC 9430Extension of the Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE) to Transport Layer Security (TLS)Current
July 2023
- RFC 8449Record Size Limit Extension for TLSCurrent
August 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?