[OAUTH-WG] Re: [media-types] Re: Request for registering media types and structured suffixes defined by W3C VCWG candidate recommendations

[Michael Jones <[e-mail]>]

It’s my hope that the registrations of application/vc+sd-jwt and application/vp+sd-jwt will be able to be done in a way that works for both VC-JOSE-COSE and SD-JWT-VC.  As I see it, that should be an attainable goal and one that the interested parties should work together towards.

                                                                -- Mike

From: Brian Campbell <bcampbell=[e-mail]>
Sent: Thursday, June 20, 2024 1:19 PM
To: Orie Steele <[e-mail]>
Cc: [e-mail]; oauth <[e-mail]>
Subject: [OAUTH-WG] Re: [media-types] Re: Request for registering media types and structured suffixes defined by W3C VCWG candidate recommendations

Thanks for pointing out the potential dependencies and collisions on the horizon. As a co-author on a couple of the documents mentioned and a general media type novice, I have a couple of observations and questions.

The https://datatracker.ietf.org/doc/draft-ietf-oauth-selective-disclosure-jwt/ document does plan to request registration of a "+sd-jwt" structured syntax suffix. I believe (hope is perhaps a better word) that the draft is nearing WGLC and it could all happen this year.

The https://datatracker.ietf.org/doc/draft-ietf-oauth-sd-jwt-vc/ document, which builds on the aforementioned document, plans on requesting registration of an "application/vc+sd-jwt" media type. That draft is less mature overall and not expected to be "finished" anytime soon. However, the "application/vc+sd-jwt" media type is already being used in implementations as well as downstream specifications and profiles.

Would it be useful in avoidance of dependencies to request early or provisional registration of that structured syntax suffix and media type? Please forgive my ignorance of the process but is early or provisional registration even possible?


On Mon, Jun 10, 2024 at 10:58 AM Orie Steele <[e-mail]<mailto:[e-mail]>> wrote:
[ as an individual ]
+sd-jwt is requested to be registered in this document:

https://datatracker.ietf.org/doc/html/draft-ietf-oauth-selective-disclosure-jwt-08#name-structured-syntax-suffix-re

+cwt is requested to registered in this document:

https://datatracker.ietf.org/doc/html/draft-ietf-rats-eat-media-type-07#name-cwt-structured-syntax-suffi

Both drafts are still work in progress, but for the W3C Verifiable Credentials use case, only +sd-jwt might be relevant, since +cwt is for claimsets that are CBOR maps where the map keys come from https://www.iana.org/assignments/cwt/cwt.xhtml

Based on the comments I've seen here, I would expect to see requests for the following:

application/vc
application/vc+jwt
application/vc+cose
application/vc+sd-jwt (depends on the draft above)

application/vp
application/vp+jwt
application/vp+cose
application/vp+sd-jwt (depends on the draft above)

Perhaps it is worth asking now if application/vc+sd-jwt will be rejected, since it is currently already being requested here:

https://datatracker.ietf.org/doc/html/draft-ietf-oauth-sd-jwt-vc-03#name-application-vcsd-jwt

Including OAuth for awareness.

Regards,

OS


On Mon, Jun 10, 2024 at 10:33 AM Manu Sporny <[e-mail]<mailto:[e-mail]>> wrote:
On Mon, Jun 10, 2024 at 10:22 AM Alexey Melnikov
<[e-mail]<mailto:[e-mail]>> wrote:
> Yes, I can confirm that the registration is currently denied due to
> unclear rules about multiple structured suffixes, as well as lack of any
> conlusion on how to proceed on the mailing list.

Thank you, Alexey, much appreciated, that helps the VCWG move forward.

We'll update our specs and send in another set of registrations that
will fall more in line w/ the current accepted practices at IANA.

-- manu

--
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
https://www.digitalbazaar.com/

_______________________________________________
media-types mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>


--



ORIE STEELE
Chief Technology Officer
www.transmute.industries<http://www.transmute.industries/>

[https://ci3.googleusercontent.com/mail-sig/AIorK4xqtkj5psM1dDeDes_mjSsF3ylbEa5EMEQmnz3602cucAIhjLaHod-eVJq0E28BwrivrNSBMBc]<https://transmute.industries/>
_______________________________________________
OAuth mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>

CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited.  If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.