Tagged COSE payload

[Pique7]

Is it standard-compliant to tag a COSE payload? For eample:

COSE_Sign = [
     Headers,
     payload : #6.24(bytes),
     signatures : [+ COSE_Signature]
 ]

[cabo]

Section 4.1 defines the payload field as bstr / nil, which does not include tags.
Note that COSE has header parameter fields that might do what I think you want to achieve, e.g., please see RFC 9596. A "typ" parameter with value "60" (application/cbor) would have about the semantics of tag 24, but you could be more specific in the choice of the content format, which I would recommend.

[Pique7]

Thank you for the advice. I currently also try to implement a venturesome CBOR construct like this (pseudo code):

COSE_Sign1(
  COSE_Encrypt0(
    deflate_compressed: #6.40003(
      my_cbor: #6.24(bstr)
    )
  )
)

As far as I know by now, you can specify content type 16 for the nested COSE_Encrypt0, but I am still not sure how it would be possible to be more specific on the compressed data and its payload (a CBOR bstr). I have adopted tag 40003 for the structure of the compressed data.