[media-types] Re: Media type for SUIT_Report_Protected
"Murray S. Kucherawy" <[email protected]>
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <CAL0qLwaVEFkhdWkqveyYFPNN9k3Gagb56t1FeTxbUSjMCBfNfg@mail.gmail.com> |
On Tue, Jul 29, 2025 at 8:46 AM Brendan Moran <[email protected]> wrote: > As part of the SUIT working group, we have been developing a reporting > format for firmware updates. This reporting format is defined in: > https://datatracker.ietf.org/doc/draft-ietf-suit-report/ > > In this draft we have proposed a media type registration: > > application/suit-report+cose > > Type name: application > Subtype name: suit-report+cose > Required parameters: n/a > Where'd "Optional Parameters" go? > Encoding considerations: binary (CBOR) > Security considerations: Section 10 of > https://datatracker.ietf.org/doc/draft-ietf-suit-report/ > Interoperability considerations: n/a > Why is this N/A? > Published specification: > https://datatracker.ietf.org/doc/draft-ietf-suit-report/ > Applications that use this media type: SUIT Manifest Processor, SUIT > Manifest Distributor, SUIT Manifest Author, RATS Attesters, RATS > Verifiers > Fragment identifier considerations: The syntax and semantics of > fragment identifiers are as specified for "application/cose". > Person & email address to contact for further information: SUIT WG > mailing list ([email protected]) > Intended usage: COMMON > Restrictions on usage: none > Author/Change controller: IETF > Provisional registration: no > -MSK <https://www.norton.com> Virus-free.www.norton.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> _______________________________________________ media-types mailing list -- [email protected] To unsubscribe send an email to [email protected]