So which set of named constraints is application/cbor ? is it "any" ?
And wouldn't adding a parameter like ";sc=preferred+/deterministic" or
something similar cause a family of content formats and require an update
to the RFC for CBOR?
I don't know that I have ever seen a media type parameter get added after
the fact.


On Thu, Nov 12, 2026 at 11:52 PM Carsten Bormann <[email protected]> wrote:

> On 2026 Nov 13, at 02:48, Steven Mih <steven=
> [email protected]> wrote:
> >
> > -01, which we'll post once open again, defines a value for CBOR content
> only. What COSE still needs is the header itself: application/cbor in 259
> doesn't say whether a deterministic serialization was applied, so a Hash
> Envelope verifier re-encoding the value has to guess.
>
> The media type registry indeed sounds like a good way to define CBOR-based
> media types that come with serialization constraints.
>
> Grüße, Carsten
>
> _______________________________________________
> CBOR mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to