See the following PR related to registrations of media types that rely on multiple structured suffixes, for example:
application/foo+bar+cose would require `+bar+cose` , `+cose` application/foo+bar+jwt would require `+bar+jwt`, `+bar+jwt` application/foo+bar+sd-jwt would require `+bar+sd-jwt`, `+sd-jwt` Manu, please make sure I translated the text from the PR to examples meaningful to the JOSE, COSE and OAuth working groups. If you feel this message should be reviewed by other lists, for example: - https://openid.net/wg/digital-credentials-protocols/ - https://www.w3.org/community/wicg/ Please forward a link along to them. For context, the intention of the W3C VCWG appears to be to register a lot of media types relying on structured suffixes: For example: application/vc+ld+json - https://www.w3.org/TR/2024/CRD-vc-data-model-2.0-20240218/#iana-considerations application/vp+ld+json - https://www.w3.org/TR/2024/CRD-vc-data-model-2.0-20240218/#iana-considerations application/vc+ld+json+jwt - https://w3c.github.io/vc-jose-cose/#media-types application/vp+ld+json+jwt - https://w3c.github.io/vc-jose-cose/#media-types application/vc+ld+json+sd-jwt - https://w3c.github.io/vc-jose-cose/#media-types application/vp+ld+json+sd-jwt - https://w3c.github.io/vc-jose-cose/#media-types application/vc+ld+json+cose - https://w3c.github.io/vc-jose-cose/#media-types application/vp+ld+json+cose - https://w3c.github.io/vc-jose-cose/#media-types +jwt is already registered https://www.iana.org/assignments/media-type-structured-suffix/media-type-structured-suffix.xhtml ( https://www.rfc-editor.org/rfc/rfc8417.html#section-7.2 ) +ld+json is requested to be registered in https://w3c.github.io/json-ld-syntax/#structured-extension-ld-json (an W3C Editors draft) +sd-jwt is requested to be registered in https://datatracker.ietf.org/doc/html/draft-ietf-oauth-selective-disclosure-jwt-07#name-structured-syntax-suffix-re (not yet an RFC) +cose is requested to be registered in https://datatracker.ietf.org/doc/html/draft-ietf-anima-constrained-voucher#section-16.5 (not yet an RFC) My understanding of the proposed PR text would be that there is no need to register additional structured suffixes to support the intention of the W3C VCWG, because: All the suffixes mentioned above are either already registered (+jwt), or in the process of being registered (+ld+json, +sd-jwt, +cose). After all the suffixes have been registered, it will then be possible to request registrations of subtypes that rely on them, namely: application/vc+... application/vp+... We may also see additional structured syntax suffixes registered for other security formats in the future, for example: application/cesr might register +cesr - https://mailarchive.ietf.org/arch/msg/i-d-announce/FvL1rLC1SCyTBRnu92At9Wncd2Y/ <https://mailarchive.ietf.org/arch/msg/i-d-announce/FvL1rLC1SCyTBRnu92At9Wncd2Y/> - https://www.iana.org/assignments/provisional-standard-media-types/provisional-standard-media-types.xhtml#Samuel_M._Smith I can imagine perhaps `+mdoc` in the future, or perhaps mdoc might use `+cose` since AFAIK, mdocs are cose-sign1 based credentials. I'd like to see the suffixes draft make it to WGLC (with more reviews), and appreciate Manu sending this email out in order to gather feedback with sufficient time to address it before 119. Regards, OS ---------- Forwarded message --------- From: Manu Sporny <mspo...@digitalbazaar.com> Date: Mon, Feb 19, 2024 at 12:44 PM Subject: [media-types] Last tracker issue for mediaman-suffixes To: IETF Media Types <media-ty...@ietf.org> The only item of concern that was raised during the last IETF was the notion that one wouldn't have to register "intermediate" suffixes[1]. The PR above corrects that by implementing what I believe many of the people in the room (and on the tracker) were arguing for, including Alexi and Darrel: https://github.com/ietf-wg-mediaman/suffixes/pull/21 That is the last PR for the last tracker issue for the mediaman-suffixes draft. Speaking as an Editor, I think we're done here with all of the items that we can get consensus on (we'll see if others disagree). Once I have enough reviews on the PR above (end of week, probably), I'll cut a new version of the draft and send it out for review (next weekend, probably) before the next IETF. -- manu [1]https://github.com/ietf-wg-mediaman/suffixes/issues/20 -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. https://www.digitalbazaar.com/ _______________________________________________ media-types mailing list media-ty...@ietf.org https://www.ietf.org/mailman/listinfo/media-types -- ORIE STEELE Chief Technology Officer www.transmute.industries <https://transmute.industries> -- ORIE STEELE Chief Technology Officer www.transmute.industries <https://transmute.industries>
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
