[rfc-dist] RFC 9019 on A Firmware Update Architecture for Internet of Things
rfc-editor@rfc-editor.org Sat, 01 May 2021 05:16 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6ECD3A352C for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 30 Apr 2021 22:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s5nRMomvR5Ff for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 30 Apr 2021 22:16:31 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F2BD3A352D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 30 Apr 2021 22:16:31 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 66AD8F407CC; Fri, 30 Apr 2021 22:16:13 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 13524F407C7; Fri, 30 Apr 2021 22:16:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20210501051613.13524F407C7@rfc-editor.org>
Date: Fri, 30 Apr 2021 22:16:13 -0700
Subject: [rfc-dist] RFC 9019 on A Firmware Update Architecture for Internet of Things
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, suit@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9019
Title: A Firmware Update Architecture for
Internet of Things
Author: B. Moran,
H. Tschofenig,
D. Brown,
M. Meriac
Status: Informational
Stream: IETF
Date: April 2021
Mailbox: brendan.moran@arm.com,
hannes.tschofenig@arm.com,
david.brown@linaro.org,
milosch@meriac.com
Pages: 25
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-suit-architecture-16.txt
URL: https://www.rfc-editor.org/info/rfc9019
DOI: 10.17487/RFC9019
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.
This document is a product of the Software Updates for Internet of Things Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org