Hi Daniel, great work! Looking at [1] and [2] there`s obviously no consensus – which implies a breach of Sections 1.2, 5 and 9.2 of the IETF Directives on Internet Standards Process. An assumption is great but not sufficient as in any standardization body. According to IETF rules the consensus shall be ensured before announcement of new version.
The profiling you suggest is technically the worst solution as it leads directly to additional effort to ensure interoperability between fundamental standard and its profiles and extend complexity unnecessarily. Means the inclusion of DID in SD-JWT-VC shall be discussed with the relevant experts such as Markus Sabadello, Alen Horvat etc. Decision making based on actual consensus not assumed one. Formal appeal acc. Section 6.5 of IETF Directives on Internet Standards Process will follow in case the IETF directives will still be ignored. Best Steffen Von: Daniel Fett <[email protected]> Gesendet: Mittwoch, 13. November 2024 21:03 An: [email protected] Betreff: [OAUTH-WG] Re: I-D Action: draft-ietf-oauth-sd-jwt-vc-06.txt Caution: This email originated from outside of the organization. Despite an upstream security check of attachments and links by Microsoft Defender for Office, a residual risk always remains. Only open attachments and links from known and trusted senders. Hi all, we are happy to announce version -06 of SD-JWT VC. In this release, we're updating the media type from application/vc+sd-jwt to application/dc+sd-jwt (for background, see Brian's excellent summary at the IETF meeting last week [0]). This version also removes references to DIDs in the specification, while leaving the door open for those who want to define a profile of SD-JWT VC using DIDs. The previously provided text on DIDs was underspecified and therefore not helpful, and a more complete specification would exceed the scope of this document while interoperability issues would remain. We think that those ecosystems wanting to use DIDs are best served by defining a profile for doing so. We would like to point out that there are concerns about this step raised both in the respective issue [1] and in the pull request [2]. While it is our understanding from various discussions that there is a consensus for the removal of the references to DIDs in the group, this change had not been discussed here on the mailing list before. So we'd like to take this opportunity to do that now. As a minor point, this version adds the “Status” field for the well-known URI registration per IANA early review. -Daniel [0] https://www.youtube.com/watch?v=LvIBqlHkuXY [1] https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/250 [2] https://github.com/oauth-wg/oauth-sd-jwt-vc/pull/251 Am 13.11.24 um 21:45 schrieb [email protected]<mailto:[email protected]>: Internet-Draft draft-ietf-oauth-sd-jwt-vc-06.txt is now available. It is a work item of the Web Authorization Protocol (OAUTH) WG of the IETF. Title: SD-JWT-based Verifiable Credentials (SD-JWT VC) Authors: Oliver Terbu Daniel Fett Brian Campbell Name: draft-ietf-oauth-sd-jwt-vc-06.txt Pages: 53 Dates: 2024-11-13 Abstract: This specification describes data formats as well as validation and processing rules to express Verifiable Credentials with JSON payloads with and without selective disclosure based on the SD-JWT [I-D.ietf-oauth-selective-disclosure-jwt] format. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-oauth-sd-jwt-vc/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-06.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-oauth-sd-jwt-vc-06 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ OAuth mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________ OAuth mailing list -- [email protected] To unsubscribe send an email to [email protected]
