Hi, https://datatracker.ietf.org/doc/draft-ietf-anima-jws-voucher/ is in WGLC, and https://datatracker.ietf.org/doc/draft-ietf-anima-brski-prm/ depends upon it.
In anima-jws-voucher, we defined: https://www.ietf.org/archive/id/draft-ietf-anima-jws-voucher-06.html#name-application-voucher-jwsjson Type name: application Subtype name: voucher-jws+json which is in alignment with https://www.rfc-editor.org/rfc/rfc8366.html#section-8.3 where we defined: Type name: application Subtype name: voucher-cms+json probably this was a mistake! (JSON in a CMS envelope) I think, based upon discussion about +cose and our other documents, that we should really be doing: application/voucher+jws While jwt is given as a structured suffix in the IANA registry, jws is not. I'm not entirely sure if this matters... we are dealing with JWS, not tokens... Please advise. While we have lots of running code (since 2018) for voucher-jws, it's a change we could probably make via Postel Principal. -- 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
