Hi Carsten, Orie, Thank you both, and Carsten for the RFC 6838 pointers: a profile parameter is indeed possible. We still think the encoding belongs in its own header. 259 says what the content is, for every instance of that type. The parameter says how this signer turned this value into the bytes it hashed, the same kind of fact as 258. A media type change covers only the type it amends, while every +cbor type has its own owner, and it changes the 259 value that existing verifiers match on. Where a type fixes its own serialization, 259 is enough and the parameter is omitted, so the two coexist.
Best, Anton On Fri, Nov 13, 2026 07:40 AM, Carsten Bormann <[email protected]> wrote: > On 2026 Nov 13, at 15:11, Orie <[email protected]> wrote: > > > > So which set of named constraints is application/cbor ? is it "any" ? > > No constraints (empty serialization constraint set), also known as CBOR. > > > 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? > > We could do new media types (per profile), or one new media type with a > parameter. > > > I don't know that I have ever seen a media type parameter get added > after the fact. > > RFC 6838: > > 4.3. Parameter Requirements > > Media types MAY elect to use one or more media type parameters[…] > the > names, values, and meanings of any parameters MUST be fully specified > when a media type is registered in the standards tree, and SHOULD be > specified as completely as possible when media types are registered > in the vendor or personal trees. > > and then… > > New parameters SHOULD NOT be defined as a way to introduce new > functionality in types registered in the standards tree, although new > parameters MAY be added to convey additional information that does > not otherwise change existing functionality. An example of this > would be a "revision" parameter to indicate a revision level of an > external specification such as JPEG. Similar behavior is encouraged > for media types registered in the vendor or personal trees, but is > not required. > > I think a profile (restricting certain aspects to a subset) would fit the > above narrowly. > > Reality (quick search, no warranty express or implied): > > 1. image/svg+xml > 2. application/json > 3. application/sdp > 4. application/dash+xml > > Grüße, Carsten > >
_______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
