[Suit] Rerendered PDF available: RFC 9019 on A Firmware Update Architecture for Internet of Things

rfc-editor@rfc-editor.org Mon, 19 December 2022 21:52 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: suit@ietfa.amsl.com
Delivered-To: suit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8063BC14CF14; Mon, 19 Dec 2022 13:52:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.648
X-Spam-Level:
X-Spam-Status: No, score=-6.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S5rJEtCUXl1H; Mon, 19 Dec 2022 13:52:20 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCF33C15258B; Mon, 19 Dec 2022 13:51:57 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 7F227C8AFD; Mon, 19 Dec 2022 13:51:57 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, suit@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20221219215157.7F227C8AFD@rfcpa.amsl.com>
Date: Mon, 19 Dec 2022 13:51:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/Lz7GYAIZ90gyn3kdr-n26ATf7sk>
Subject: [Suit] Rerendered PDF available: RFC 9019 on A Firmware Update Architecture for Internet of Things
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Software Updates for Internet of Things <suit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/suit>, <mailto:suit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/suit/>
List-Post: <mailto:suit@ietf.org>
List-Help: <mailto:suit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/suit>, <mailto:suit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2022 21:52:24 -0000

This RFC has a rerendered PDF file: https://www.rfc-editor.org/rfc/rfc9019.pdf

More information is here: https://www.rfc-editor.org/rpc/wiki/doku.php?id=rerendering

        
        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
        Pages:      24
        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