Last Call: <draft-ietf-suit-manifest-25.txt> (A Concise Binary Object Representation (CBOR)-based Serialization Format for the Software Updates for Internet of Things (SUIT) Manifest) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 07 February 2024 19:44 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-suit-manifest-25.txt> (A Concise Binary Object Representation (CBOR)-based Serialization Format for the Software Updates for Internet of Things (SUIT) Manifest) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
CC: David Waltermire <david.waltermire@nist.gov>, draft-ietf-suit-manifest@ietf.org, housley@vigilsec.com, rdd@cert.org, suit-chairs@ietf.org, suit@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <170733508508.56759.2461886140921682822@ietfa.amsl.com>
Date: Wed, 07 Feb 2024 11:44:45 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Gik6F96eeyrqnoMhsFdVXEX60xs>

The IESG has received a request from the Software Updates for Internet of
Things WG (suit) to consider the following document: - 'A Concise Binary
Object Representation (CBOR)-based Serialization
   Format for the Software Updates for Internet of Things (SUIT)
   Manifest'
  <draft-ietf-suit-manifest-25.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2024-02-21. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This specification describes the format of a manifest.  A manifest is
   a bundle of metadata about code/data obtained by a recipient (chiefly
   the firmware for an IoT device), where to find the code/data, the
   devices to which it applies, and cryptographic information protecting
   the manifest.  Software updates and Trusted Invocation both tend to
   use sequences of common operations, so the manifest encodes those
   sequences of operations, rather than declaring the metadata.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-suit-manifest/


The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/5921/
   https://datatracker.ietf.org/ipr/5892/
   https://datatracker.ietf.org/ipr/5075/
   https://datatracker.ietf.org/ipr/3799/
   https://datatracker.ietf.org/ipr/6008/
   https://datatracker.ietf.org/ipr/5881/



The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc9019: A Firmware Update Architecture for Internet of Things (Informational - Internet Engineering Task Force (IETF))
    rfc9124: A Manifest Information Model for Firmware Updates in Internet of Things (IoT) Devices (Informational - Internet Engineering Task Force (IETF))
    rfc9054: CBOR Object Signing and Encryption (COSE): Hash Algorithms (Informational - Internet Engineering Task Force (IETF))

Last Call: <draft-ietf-suit-manifest-25.txt> (A C… The IESG