A Firmware Update Architecture for Internet of Things
RFC 9019
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2023-01-13
|
Sandy Ginoza | 2022/12/19: RPC rerendered the PDF of RFC 9019 using xml2rfc 3.15.3 and WeasyPrint 56.1 (see https://mailarchive.ietf.org/arch/msg/ietf-announce/PJyGNHu2cvEbQrgBA9-Q6OMhRoI/) |
|
2022-12-20
|
(System) | Received changes through RFC Editor sync (changed pages to 24) |
|
2021-04-30
|
(System) | Received changes through RFC Editor sync (created alias RFC 9019, changed abstract to 'Vulnerabilities in Internet of Things (IoT) devices have raised the need … Received changes through RFC Editor sync (created alias RFC 9019, changed abstract to '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.', changed pages to 25, changed standardization level to Informational, changed state to RFC, added RFC published event at 2021-04-30, changed IESG state to RFC Published) |
|
2021-04-30
|
(System) | RFC published |