[Suit] Re: I-D Action: draft-ietf-suit-report-20.txt

[Brendan Moran <[e-mail]>]

I have prepared an update to draft-ietf-suit-report to address the remaining review comments on draft-ietf-suit-report-19.

The changes are intended as clarifications rather than new protocol mechanisms. In summary, the update:

* Makes the COSE container text consistent by explicitly including COSE_Mac0 alongside COSE_Sign1, with COSE_Encrypt0 carried as an authenticated payload where confidentiality is needed.
* Adds guidance for report-generation failure cases:
** a recipient MUST NOT emit an unauthenticated report when policy requires authenticated reports;
​** ​if a report cannot be constructed or authenticated according to policy, the failure is reported through an implementation-specific local error/logging mechanism;
** any partial report that is emitted must satisfy the same authentication/integrity policy as other SUIT reports.
*Clarifies why suit-report-manifest-uri is present: SUIT_Record entries are only meaningful with the matching manifest, while system property claims can still be processed without the manifest because they carry SUIT_Component_Identifier.
*Clarifies that “Reporting Engine” is a conceptual function, not a required separate implementation component or mandated local API.
*Clarifies suit-record-manifest-id dependency/component-index semantics and updates the example.
*Aligns CDDL examples and standalone CDDL for $$SUIT_Parameters and repeated extension groups.

I do not believe these changes introduce a new protocol mechanism; they are intended to resolve review feedback and make the existing format and processing expectations clearer.

To the Chairs & Deb: If you believe that these changes materially affect WG consensus, please let me know.


Best,
Brendan

From: [e-mail] <[e-mail]>
Date: Tuesday, 26 May 2026 at 16:25
To: [e-mail] <[e-mail]>
Cc: [e-mail] <[e-mail]>
Subject: [Suit] I-D Action: draft-ietf-suit-report-20.txt

Internet-Draft draft-ietf-suit-report-20.txt is now available. It is a work
item of the Software Updates for Internet of Things (SUIT) WG of the IETF.

   Title:   Secure Reporting of SUIT Update Status
   Authors: Brendan Moran
            Henk Birkholz
   Name:    draft-ietf-suit-report-20.txt
   Pages:   31
   Dates:   2026-05-26

Abstract:

   The Software Update for the Internet of Things (SUIT) manifest
   provides a way for many different update and boot workflows to be
   described by a common format.  This document specifies a lightweight
   feedback mechanism that allows a developer in possession of a
   manifest to reconstruct the decisions made and actions performed by a
   manifest processor.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-suit-report/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-suit-report-20

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-suit-report-20

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
Suit mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.