<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-suit-manifest" target="https://datatracker.ietf.org/doc/html/draft-ietf-suit-manifest-34">
   <front>
      <title>A Concise Binary Object Representation (CBOR)-based Serialization Format for the Software Updates for Internet of Things (SUIT) Manifest</title>
      <author initials="B." surname="Moran" fullname="Brendan Moran">
         <organization>Arm Limited</organization>
      </author>
      <author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
         <organization>University of Applied Sciences Bonn-Rhein-Sieg</organization>
      </author>
      <author initials="H." surname="Birkholz" fullname="Henk Birkholz">
         <organization>Fraunhofer SIT</organization>
      </author>
      <author initials="K." surname="Zandberg" fullname="Koen Zandberg">
         <organization>Inria</organization>
      </author>
      <author initials="O." surname="Rønningstad" fullname="Øyvind Rønningstad">
         <organization>Nordic Semiconductor</organization>
      </author>
      <date month="May" day="28" year="2025" />
      <abstract>
	 <t>   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 Internet of Things (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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-suit-manifest-34" />
   
</reference>
