RFC 9124: A Manifest Information Model for Firmware Updates in Internet of Things (IoT) Devices
In plain English — editorial summary, not part of the RFC
Vulnerabilities with Internet of Things (IoT) devices have raised the need for a reliable and secure firmware update mechanism that is also suitable for constrained devices. Ensuring that devices function and remain secure over their service lifetime requires such an update mechanism to fix vulnerabilities, update configuration settings, and add new functionality. One component of such a firmware update is a concise and machine-processable metadata 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.
Document record
- Document ID
- RFC9124
- Published
- January 2022
- Authors
- B. Moran; H. Tschofenig; H. Birkholz
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 40
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8628OAuth 2.0 Device Authorization GrantCurrent
August 2019
- RFC 7641Observing Resources in the Constrained Application Protocol (CoAP)Updated
September 2015
- RFC 9126OAuth 2.0 Pushed Authorization RequestsCurrent
September 2021
- RFC 9132Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationCurrent
September 2021
- RFC 9133Controlling Filtering Rules Using Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal ChannelCurrent
September 2021
- RFC 9115An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated CertificatesCurrent
September 2021
- RFC 9140Nimble Out-of-Band Authentication for EAP (EAP-NOOB)Updated
December 2021
- RFC 9142Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)Current
January 2022
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?