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

[Brendan Moran <[e-mail]>]

Hi Ken,

Is this text what you had in mind?

The suit-reference provides a digest and, when available, a reference URI
for a SUIT manifest. The digest is the digest of the manifest, exactly as
reported in SUIT_Authentication, element 0
({{Section 8.3 of I-D.ietf-suit-manifest}}). If the root manifest contains
a suit-reference-uri ({{Section 8.4.3 of I-D.ietf-suit-manifest}}), the
SUIT\_Report MUST include suit-report-manifest-uri, and its value MUST
exactly match that suit-reference-uri. If the root manifest does not contain
a suit-reference-uri, suit-report-manifest-uri MUST be omitted.

Best Regards,
Brendan

From: Ken Takayama <[e-mail]>
Date: Thursday, 18 June 2026 at 22:49
To: Akira Tsukamoto gmail <[e-mail]>
Cc: [e-mail] <[e-mail]>; [e-mail] <[e-mail]>
Subject: [Suit] Re: I-D Action: draft-ietf-suit-report-21.txt

Akira and SUIT Report authors,

Sure! I’m just reviewing the update today. Two points:

1. Clarify optionality in the document text (concern)
The CDDL now marks suit-report-manifest-uri as optional.
But the current sentence “The URI MUST exactly match the
suit-reference-uri …” can be read as requiring presence.
Making this conditional would avoid ambiguity, for example:
“If the manifest contains a suit-reference-uri, the SUIT Report MUST
include a matching suit-report-manifest-uri.”
or
“If a SUIT Report includes suit-report-manifest-uri, it MUST match the
value in suit-reference-uri.”
These two options imply different behaviors, and I’m not sure which
one reflects the intended design.
There may be other possibilities as well, so I would prefer to rely on
the authors’ judgment here.

2. Reorder elements in the CDDL (welcome)
>From a parser perspective it’s preferable if the digest is the first
element and the optional URI follows, so the first array element is
always SUIT_Digest.
If you reorder the CDDL, please update the document text to list the
elements in the same order as well.

Best regards,
Ken

2026年6月19日(金) 6:19 Akira Tsukamoto gmail <[e-mail]>:
>
> Hi Ken,
>
> Thanks for the SUIT-Interim today.
> Moving this to the mailing list,
>
> Brendan has published the suit-report-21, and could you review these
> changes in your comments on "suit-uri"?
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-suit-report-21
>
> Thanks,
> Akira
>
> ------------------------------
> On Fri, Jun 12, 2026 at 10:36 AM Ken Takayama
> <[e-mail]> wrote:
> Brendan,
>
> Sorry for my late reply.
>
> I believe that all of the ambiguities I previously pointed out have
> now been resolved, namely:
> - what the Reporting Engine is;
> - the behavior when generation of a SUIT Report fails, which depends
> on policy; and
> - what the uint values in suit-record-manifest-id and
> suit-record-component-index refer to.
>
> However, I would like to confirm one remaining point.
> It still looks to me as if suit-report-manifest-uri is mandatory in
> the data structure.
> If so, for SUIT Manifests that do not contain suit-reference-uri, such
> as Examples 0, 1, 3, 4, and 5 in draft-ietf-suit-manifest,
> I think this would result in a situation where “a report cannot be constructed.”
> >From my perspective, this still appears to be an unresolved issue.
>
>
> Best regards,
> Ken
>
>
> 2026年5月26日(火) 23:26 Brendan Moran <[e-mail]>:
> >
> > Hi Ken,
> >
> > I have updated suit-report to address some of your comments. The PR is here: https://github.com/suit-wg/suit-report/pull/70
> >
> > Please let me know if that resolves the issues you raised.
> >
> > Best Regards,
> > Brendan
>
> On Thu, Jun 18, 2026 at 10:42 PM <[e-mail]> wrote:
> >
> > Internet-Draft draft-ietf-suit-report-21.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-21.txt
> >    Pages:   31
> >    Dates:   2026-06-18
> >
> > 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-21
> >
> > A diff from the previous version is available at:
> > https://author-tools.ietf.org/iddiff?url2=draft-ietf-suit-report-21
> >
> > 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]
>
> _______________________________________________
> Suit mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

_______________________________________________
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.