[media-types] Re: application/cmw* registration requests

Hi, media type experts,

Bumping this request to the top of your inbox in case you missed it :-)

The document has just been approved by the IESG.

Thank you in advance,

cheers, t

On Mon, 25 Aug 2025 at 12:01, Thomas Fossati <[email protected]> wrote:
>
> Hi, media type experts,
>
> This request is for the registration of the four "application/cmw*"
> media types as defined in Section 10.6 of draft-ietf-rats-msg-wrap-17
> [1].
>
> The details are included below.
>
> cheers, thanks!
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-rats-msg-wrap/17/
>
> ----------------------------------------------------------------------
> application/cmw+cbor
> ----------------------------------------------------------------------
>
>    Type name:  application
>    Subtype name:  cmw+cbor
>    Required parameters:  n/a
>    Optional parameters:  cmwc_t (Collection CMW type in string format.
>       OIDs must use the dotted-decimal notation.  The parameter value is
>       case-insensitive.  It must not be used for CMW that are not
>       Collections.)
>    Encoding considerations:  binary (CBOR)
>    Security considerations:  Section 9 of RFCthis
>    Interoperability considerations:  n/a
>    Published specification:  RFCthis
>    Applications that use this media type:  Attesters, Verifiers,
>       Endorsers and Reference-Value providers, Relying Parties that need
>       to transfer CMW payloads over HTTP(S), CoAP(S), and other
>       transports.
>    Fragment identifier considerations:  The syntax and semantics of
>       fragment identifiers are as specified for "application/cbor".  (No
>       fragment identification syntax is currently defined for
>       "application/cbor".)
>    Person & email address to contact for further information:  RATS WG
>       mailing list ([email protected])
>    Intended usage:  COMMON
>    Restrictions on usage:  none
>    Author/Change controller:  IETF
>    Provisional registration:  no
>
> ----------------------------------------------------------------------
> application/cmw+json
> ----------------------------------------------------------------------
>
>    Type name:  application
>    Subtype name:  cmw+json
>    Required parameters:  n/a
>    Optional parameters:  cmwc_t (Collection CMW type in string format.
>       OIDs must use the dotted-decimal notation.  The parameter value is
>       case-insensitive.  It must not be used for CMW that are not
>       Collections.)
>    Encoding considerations:  binary (JSON is UTF-8-encoded text)
>    Security considerations:  Section 9 of RFCthis
>    Interoperability considerations:  n/a
>    Published specification:  RFCthis
>    Applications that use this media type:  Attesters, Verifiers,
>       Endorsers and Reference-Value providers, Relying Parties that need
>       to transfer CMW payloads over HTTP(S), CoAP(S), and other
>       transports.
>    Fragment identifier considerations:  The syntax and semantics of
>       fragment identifiers are as specified for "application/json".  (No
>       fragment identification syntax is currently defined for
>       "application/json".)
>    Person & email address to contact for further information:  RATS WG
>       mailing list ([email protected])
>    Intended usage:  COMMON
>    Restrictions on usage:  none
>    Author/Change controller:  IETF
>    Provisional registration:  no
>
> ----------------------------------------------------------------------
> application/cmw+cose
> ----------------------------------------------------------------------
>
>    Type name:  application
>    Subtype name:  cmw+cose
>    Required parameters:  n/a
>    Optional parameters:  cmwc_t (Collection CMW type in string format.
>       OIDs must use the dotted-decimal notation.  The parameter value is
>       case-insensitive.  It must not be used for CMW that are not
>       Collections.)  Note that the cose-type parameter is explicitly not
>       supported, as it is understood to be "cose-sign1".
>    Encoding considerations:  binary (CBOR)
>    Security considerations:  Section 9 of RFCthis
>    Interoperability considerations:  n/a
>    Published specification:  RFCthis
>    Applications that use this media type:  Attesters, Verifiers,
>       Endorsers and Reference-Value providers, Relying Parties that need
>       to transfer CMW payloads over HTTP(S), CoAP(S), and other
>       transports.
>    Fragment identifier considerations:  n/a
>    Person & email address to contact for further information:  RATS WG
>       mailing list ([email protected])
>    Intended usage:  COMMON
>    Restrictions on usage:  none
>    Author/Change controller:  IETF
>    Provisional registration:  no
>
> ----------------------------------------------------------------------
> application/cmw+jws
> ----------------------------------------------------------------------
>
>    Type name:  application
>    Subtype name:  cmw+jws
>    Required parameters:  n/a
>    Optional parameters:  cmwc_t (Collection CMW type in string format.
>       OIDs must use the dotted-decimal notation.  The parameter value is
>       case-insensitive.  It must not be used for CMW that are not
>       Collections.)
>    Encoding considerations:  8bit; values are represented as a JSON
>       Object or as a series of base64url-encoded values each separated
>       from the next by a single period ('.') character.
>    Security considerations:  Section 9 of RFCthis
>    Interoperability considerations:  n/a
>    Published specification:  RFCthis
>    Applications that use this media type:  Attesters, Verifiers,
>       Endorsers and Reference-Value providers, Relying Parties that need
>       to transfer CMW payloads over HTTP(S), CoAP(S), and other
>       transports.
>    Fragment identifier considerations:  n/a
>    Person & email address to contact for further information:  RATS WG
>       mailing list ([email protected])
>    Intended usage:  COMMON
>    Restrictions on usage:  none
>    Author/Change controller:  IETF
>    Provisional registration:  no

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]