Michael Jones <[email protected]> wrote: > Michael R., you wrote: >> 1) application/voucher-cms+json aka voucher+json+cms?
> I don't think these make sense since CMS is X.509 - not JSON. You
> could reasonably use application/voucher-cms or
> application/voucher+cms.
CMS signed JSON is in RFC8366. It's useful to people who have a CMS library
that has gone through FIPS, but not a JWS or COSE library. This was more
important in 2016 when the spec ws written.
>> 2) application/voucher+cose or? voucher+cbor+cose?
> application/voucher+cose would make sense. I don't think the +cbor
> adds anything useful here.
I agree, I don't think it adds anything.
>> 3) application/voucher-jwt+json aka voucher+json+jwt?
> Neither of the above make sense. JWTs are sequences of
> base64url-encoded characters separated by periods. They are not JSON.
Neither is image/svg+xml+gzip actually XML, until you decode the GZIP.
> application/voucher+jwt would make sense.
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
